Skip to content

DFBUGS-8403: [release-4.16] Bump go (stdlib) from 1.21.9 to 1.21.13 - #650

Merged
openshift-ci[bot] merged 1 commit into
release-4.16from
release-4.16-fix-8cd106cf
Sep 15, 2026
Merged

DFBUGS-8403: [release-4.16] Bump go (stdlib) from 1.21.9 to 1.21.13#650
openshift-ci[bot] merged 1 commit into
release-4.16from
release-4.16-fix-8cd106cf

Conversation

@Nikhil-Ladha

@Nikhil-Ladha Nikhil-Ladha commented Jul 7, 2026

Copy link
Copy Markdown
Member

Changes

  • go (stdlib): 1.21.9 → 1.21.13 (in go.mod)

Nikhil Ladha
godeps: bump go (stdlib) from 1.21.9 to 1.21.13
bf9e218 
Updated the following modules:
- go (stdlib): 1.21.9 -> 1.21.13 (go.mod)

Signed-off-by: Nikhil Ladha <nikhil.ladha@example.com>
@Nikhil-Ladha Nikhil-Ladha added automated Pull requests that are created via an automation dependencies Pull requests that updates a dependency file labels Jul 7, 2026
@openshift-ci-robot openshift-ci-robot added jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. 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 7, 2026
@openshift-ci-robot

openshift-ci-robot commented Jul 7, 2026 •
edited by openshift-ci Bot
Loading

Copy link
Copy Markdown

@Nikhil-Ladha: This pull request references [Jira Issue DFBUGS-8403](https://redhat.atlassian.net/browse/DFBUGS-8403), which is invalid:

  • expected the vulnerability to target the "odf-4.16.31" 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.21.9 → 1.21.13 (in 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.

@github-actions

github-actions Bot commented Sep 10, 2026

Copy link
Copy Markdown

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed in two weeks if no further activity occurs. Thank you for your contributions.

@github-actions github-actions Bot added the stale label Sep 10, 2026
@leelavg leelavg closed this Sep 11, 2026
@openshift-ci-robot

openshift-ci-robot commented Sep 11, 2026 •
edited by openshift-ci Bot
Loading

Copy link
Copy Markdown

@Nikhil-Ladha: This pull request references [Jira Issue DFBUGS-8403](https://redhat.atlassian.net/browse/DFBUGS-8403). The bug has been updated to no longer refer to the pull request using the external bug tracker. All external bug links have been closed. The bug has been moved to the NEW state.

Details

In response to this:

Changes

  • go (stdlib): 1.21.9 → 1.21.13 (in 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.

@Nikhil-Ladha

Nikhil-Ladha commented Sep 15, 2026

Copy link
Copy Markdown
Member Author

@leelavg any reason for closing the PR?
We were waiting for the QE approval on the bug, hence the PR was pending merge.

@leelavg leelavg reopened this Sep 15, 2026
@openshift-ci-robot

openshift-ci-robot commented Sep 15, 2026 •
edited by openshift-ci Bot
Loading

Copy link
Copy Markdown

@Nikhil-Ladha: This pull request references [Jira Issue DFBUGS-8403](https://redhat.atlassian.net/browse/DFBUGS-8403), which is invalid:

  • expected the vulnerability to target the "odf-4.16.31" 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.21.9 → 1.21.13 (in 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.

@leelavg

leelavg commented Sep 15, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

I was cleaning up some leftovers since we have GH action updating golang but that's doing upto 4.18, reopened. why do we need qe approval for patch version bump?

@Nikhil-Ladha

Nikhil-Ladha commented Sep 15, 2026

Copy link
Copy Markdown
Member Author

I was cleaning up some leftovers since we have GH action updating golang but that's doing upto 4.18, reopened. why do we need qe approval for patch version bump?

Good question, ideally we shouldn't.
The bug is targetted for next z-version, so we should get it merged in that timeline.

@leelavg

leelavg commented Sep 15, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Don't want to have more trackers & timelines, merging it as that issue wasn't serving any purpose if the d/s builder is already at .13, isn't it?

@openshift-ci openshift-ci Bot added the lgtm label Sep 15, 2026
@openshift-ci

openshift-ci Bot commented Sep 15, 2026

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: leelavg, Nikhil-Ladha

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

The pull request process is described 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

@leelavg leelavg added jira/valid-bug Indicates that the referenced jira bug is valid for the branch this PR is targeting and removed jira/invalid-bug Indicates that the referenced jira bug is invalid for the branch this PR is targeting labels Sep 15, 2026
@openshift-ci
openshift-ci Bot merged commit 453a74d into release-4.16 Sep 15, 2026
22 checks passed
@openshift-ci-robot

openshift-ci-robot commented Sep 15, 2026 •
edited by openshift-ci Bot
Loading

Copy link
Copy Markdown

@Nikhil-Ladha: [Jira Issue DFBUGS-8403](https://redhat.atlassian.net/browse/DFBUGS-8403): All pull requests linked via external trackers have merged:

[Jira Issue DFBUGS-8403](https://redhat.atlassian.net/browse/DFBUGS-8403) has been moved to the MODIFIED state.

Details

In response to this:

Changes

  • go (stdlib): 1.21.9 → 1.21.13 (in 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.

@Nikhil-Ladha
Nikhil-Ladha deleted the release-4.16-fix-8cd106cf branch September 15, 2026 06:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@leelavg leelavg leelavg approved these changes

Assignees

@leelavg leelavg

Labels

approved automated Pull requests that are created via an automation dependencies Pull requests that updates a dependency file jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-bug Indicates that the referenced jira bug is valid for the branch this PR is targeting jira/valid-reference Indicates that this PR references a valid jira ticket of any type lgtm size/XS

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@Nikhil-Ladha @openshift-ci-robot @leelavg