Skip to content

DFBUGS-8414: [release-4.20] Bump go (stdlib) from 1.24.5 to 1.24.12#4022

Open
df-build-team wants to merge 1 commit into
release-4.20from
fix-release-4.20-8cd106cf
Open

DFBUGS-8414: [release-4.20] Bump go (stdlib) from 1.24.5 to 1.24.12#4022
df-build-team wants to merge 1 commit into
release-4.20from
fix-release-4.20-8cd106cf

Conversation

@df-build-team

Copy link
Copy Markdown

Changes

  • go (stdlib): 1.24.51.24.12 (in services/provider/api/go.mod)
  • go (stdlib): 1.24.51.24.12 (in api/go.mod)
  • go (stdlib): 1.24.51.24.12 (in go.mod)
  • go (stdlib): 1.24.51.24.12 (in metrics/go.mod)

@df-build-team df-build-team added automated Pull requests that are created via an automation dependencies Pull requests that updates a dependency file labels Jul 9, 2026
@df-build-team df-build-team requested a review from a team July 9, 2026 07:27
@openshift-ci-robot openshift-ci-robot added jira/severity-important jira/valid-reference Indicates that this PR references a valid jira ticket of any type jira/invalid-bug Indicates that the referenced jira bug is invalid for the branch this PR is targeting labels Jul 9, 2026
@openshift-ci-robot

openshift-ci-robot commented Jul 9, 2026

Copy link
Copy Markdown

@df-build-team: This pull request references [Jira Issue DFBUGS-8414](https://redhat.atlassian.net/browse/DFBUGS-8414), which is invalid:

  • expected the vulnerability to target the "odf-4.20.15" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

Details

In response to this:

Changes

  • go (stdlib): 1.24.51.24.12 (in services/provider/api/go.mod)
  • go (stdlib): 1.24.51.24.12 (in api/go.mod)
  • go (stdlib): 1.24.51.24.12 (in go.mod)
  • go (stdlib): 1.24.51.24.12 (in metrics/go.mod)

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci

openshift-ci Bot commented Jul 9, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: df-build-team
Once this PR has been reviewed and has the lgtm label, please assign malayparida2000 for approval. For more information see the Code Review Process.

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

Details 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

@malayparida2000

Copy link
Copy Markdown
Contributor

@nik-redhat Unliker PRs for other branches it's not changing this actual version just the toolchain is being updated

@Nikhil-Ladha

Copy link
Copy Markdown
Member

@nik-redhat Unliker PRs for other branches it's not changing this actual version just the toolchain is being updated

Yeah, that's expected because the go.mod file has a toolchain definition so it will only update the toolchain directive.

@df-build-team df-build-team force-pushed the fix-release-4.20-8cd106cf branch 2 times, most recently from 7d349f9 to 25515ff Compare July 14, 2026 02:24
Updated the following modules:
- go (stdlib): 1.24.5 -> 1.24.12 (api/go.mod)
- go (stdlib): 1.24.5 -> 1.24.12 (go.mod)
- go (stdlib): 1.24.5 -> 1.24.12 (metrics/go.mod)
- go (stdlib): 1.24.5 -> 1.24.12 (services/provider/api/go.mod)

Signed-off-by: DF Build Team <df-build-team@redhat.com>
@df-build-team df-build-team force-pushed the fix-release-4.20-8cd106cf branch from 25515ff to 7736257 Compare July 14, 2026 08:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

automated Pull requests that are created via an automation dependencies Pull requests that updates a dependency file jira/invalid-bug Indicates that the referenced jira bug is invalid for the branch this PR is targeting jira/severity-important jira/valid-reference Indicates that this PR references a valid jira ticket of any type

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants