Skip to content

chore: Update from ubi9/go-toolset:1.22.7-1733160835 to ubi9/go-toolset:9.5-1737480393 #1373

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
wants to merge 5 commits into from
Closed

chore: Update from ubi9/go-toolset:1.22.7-1733160835 to ubi9/go-toolset:9.5-1737480393 #1373

wants to merge 5 commits into from

Conversation

che-incubator-bot
Copy link
Collaborator

Signed-off-by: Nick Boldt nboldt@redhat.com

@nickboldt
chore: Update from ubi9/go-toolset:1.22.7-1733160835 to ubi9/go-tools…
19d0539 
…et:9.5-1737480393

Signed-off-by: Nick Boldt <nboldt@redhat.com>
@openshift-ci OpenShift CI
Copy link

openshift-ci bot commented Jan 25, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: che-incubator-bot
Once this PR has been reviewed and has the lgtm label, please assign dkwon17 for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

github-advanced-security[bot]
github-advanced-security bot found potential problems Jan 25, 2025
View reviewed changes
build/Dockerfile
@@ -14,7 +14,7 @@
#

# https://access.redhat.com/containers/?tab=tags#/registry.access.redhat.com/ubi9/go-toolset
FROM registry.access.redhat.com/ubi9/go-toolset:1.22.7-1733160835 as builder
FROM registry.access.redhat.com/ubi9/go-toolset:9.5-1737480393 as builder

Check warning

Code scanning / Scorecard

Pinned-Dependencies Medium

score is 2: containerImage not pinned by hash
Remediation tip: pin your Docker image by updating registry.access.redhat.com/ubi9/go-toolset:9.5-1737480393 to registry.access.redhat.com/ubi9/go-toolset:9.5-1737480393@sha256:b0627f14a2179df19f449623328cd4f6db9b6e0c369e9a91dae811c1cd9402cb
Click Remediation section below for further remediation help
build/Dockerfile
@@ -34,7 +34,7 @@
RUN make compile-webhook-server

# https://access.redhat.com/containers/?tab=tags#/registry.access.redhat.com/ubi9-minimal
FROM registry.access.redhat.com/ubi9-minimal:9.5-1731593028
FROM registry.access.redhat.com/ubi9-minimal:9.5-1736404155

Check warning

Code scanning / Scorecard

Pinned-Dependencies Medium

score is 2: containerImage not pinned by hash
Remediation tip: pin your Docker image by updating registry.access.redhat.com/ubi9-minimal to registry.access.redhat.com/ubi9-minimal@sha256:b87097994ed62fbf1de70bc75debe8dacf3ea6e00dd577d74503ef66452c59d6
Click Remediation section below for further remediation help
project-clone/Dockerfile
@@ -15,7 +15,7 @@

# Build the manager binary
# https://access.redhat.com/containers/?tab=tags#/registry.access.redhat.com/ubi9/go-toolset
FROM registry.access.redhat.com/ubi9/go-toolset:1.22.7-1733160835 as builder
FROM registry.access.redhat.com/ubi9/go-toolset:9.5-1737480393 as builder

Check warning

Code scanning / Scorecard

Pinned-Dependencies Medium

score is 2: containerImage not pinned by hash
Remediation tip: pin your Docker image by updating registry.access.redhat.com/ubi9/go-toolset:9.5-1737480393 to registry.access.redhat.com/ubi9/go-toolset:9.5-1737480393@sha256:b0627f14a2179df19f449623328cd4f6db9b6e0c369e9a91dae811c1cd9402cb
Click Remediation section below for further remediation help
project-clone/Dockerfile
@@ -37,7 +37,7 @@
project-clone/main.go

# https://access.redhat.com/containers/?tab=tags#/registry.access.redhat.com/ubi9-minimal
FROM registry.access.redhat.com/ubi9-minimal:9.5-1731593028
FROM registry.access.redhat.com/ubi9-minimal:9.5-1736404155

Check warning

Code scanning / Scorecard

Pinned-Dependencies Medium

score is 2: containerImage not pinned by hash
Remediation tip: pin your Docker image by updating registry.access.redhat.com/ubi9-minimal to registry.access.redhat.com/ubi9-minimal@sha256:b87097994ed62fbf1de70bc75debe8dacf3ea6e00dd577d74503ef66452c59d6
Click Remediation section below for further remediation help
@openshift-merge-robot
Copy link

PR needs rebase.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@dkwon17
Copy link
Collaborator

dkwon17 commented Feb 24, 2025

Replaced by #1385

@dkwon17 dkwon17 closed this Feb 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@dkwon17 dkwon17 Awaiting requested review from dkwon17 dkwon17 is a code owner

@ibuziuk ibuziuk Awaiting requested review from ibuziuk ibuziuk is a code owner

Assignees
No one assigned
Labels
needs-rebase
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
4 participants
@che-incubator-bot @openshift-merge-robot @dkwon17 @nickboldt