Skip to content

fix(deps): bump golang.org/x/net to v0.60.0 - #298

Merged
lokewate merged 1 commit into
mainfrom
fix/x-net-v0.60.0
Oct 11, 2026
Merged

lokewate merged 1 commit into
mainfrom
fix/x-net-v0.60.0

Conversation

@lokewate

Copy link
Copy Markdown
Contributor

Summary

Bumps golang.org/x/net from v0.58.0 to v0.60.0. govulncheck reports five HTTP/2 advisories in v0.58.0 (GO-2026-6603, GO-2026-6610, GO-2026-6611, GO-2026-6612, GO-2026-6617), all fixed in v0.60.0, which fails the Vulnerability Scan job on main and every branch.

Type of Change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation update
  • Refactoring (no functional changes)
  • Performance improvement
  • Other (please describe):

Changes Made

  • go.mod / go.sum: golang.org/x/net v0.58.0 → v0.60.0 (indirect). go mod tidy also moves golang.org/x/text v0.41.0 → v0.42.0.
  • No other module pins the vulnerable version.

Testing

  • I have tested this change locally
  • I have added tests that prove my fix is effective or that my feature works
  • I have tested edge cases
  • All existing tests pass

Checklist

  • My code follows the project's style guidelines
  • I have performed a self-review of my code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have checked that there are no merge conflicts

Related Issues

N/A

Screenshots/Demo

N/A

Additional Notes

Locally, govulncheck no longer reports golang.org/x/net. It still lists standard-library advisories for the local Go toolchain, which the CI scan's Go does not hit; CI's Vulnerability Scan is the check that matters here. #297 needs this to pass its scan.

🤖 Generated with Claude Code

govulncheck reports five HTTP/2 advisories in golang.org/x/net v0.58.0
(GO-2026-6603, GO-2026-6610, GO-2026-6611, GO-2026-6612, GO-2026-6617),
all fixed in v0.60.0, which fails the Vulnerability Scan job on every
branch. x/net is indirect; go mod tidy also moves golang.org/x/text to
v0.42.0.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Oct 11, 2026 •

Copy link
Copy Markdown

Important

  • 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration
  • Configuration used: defaults
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 7de071a1-e50d-42b4-862a-ccf9295fb9bd

  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@lokewate
lokewate requested a review from Aravinda-HWK October 11, 2026 15:30
@lokewate
lokewate marked this pull request as ready for review October 11, 2026 15:30
@lokewate
lokewate added this pull request to stack #299 October 11, 2026 15:43
@lokewate
lokewate merged commit b449460 into main Oct 11, 2026
46 of 47 checks passed
@lokewate
lokewate deleted the fix/x-net-v0.60.0 branch October 11, 2026 16:10
lokewate added a commit to OpenNSW/nsw-srilanka that referenced this pull request Oct 11, 2026
Pins core at b449460 (main after OpenNSW/core#298), whose
golang.org/x/net v0.60.0 fixes the five HTTP/2 advisories (GO-2026-6603,
-6610, -6611, -6612, -6617) the Go Vulnerability Check reports in
v0.58.0. go mod tidy also moves golang.org/x/text to v0.42.0.

The bump also brings core's other root-module changes since 474396a:

- #288: a BATCH_SPLIT node's partitions see only the variables its
  input_mapping names, and its output_mapping collects their values.
- #285: CORS Validate errors name settings by their yaml keys; the
  config tests expect the new messages.

BREAKING CHANGE: workflow artifacts with a BATCH_SPLIT must declare the
split's input_mapping (the TNSW NPQS workflows do, since
one-trade-artifacts#142).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
chathura-de-silva pushed a commit to chathura-de-silva/NSW-SriLanka that referenced this pull request Oct 12, 2026
Pins core at b449460 (main after OpenNSW/core#298), whose
golang.org/x/net v0.60.0 fixes the five HTTP/2 advisories (GO-2026-6603,
-6610, -6611, -6612, -6617) the Go Vulnerability Check reports in
v0.58.0. go mod tidy also moves golang.org/x/text to v0.42.0.

The bump also brings core's other root-module changes since 474396a:

- OpenNSW#288: a BATCH_SPLIT node's partitions see only the variables its
  input_mapping names, and its output_mapping collects their values.
- OpenNSW#285: CORS Validate errors name settings by their yaml keys; the
  config tests expect the new messages.

BREAKING CHANGE: workflow artifacts with a BATCH_SPLIT must declare the
split's input_mapping (the TNSW NPQS workflows do, since
one-trade-artifacts#142).

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
WebCooper pushed a commit to WebCooper/nsw-srilanka that referenced this pull request Oct 13, 2026
Pins core at b449460 (main after OpenNSW/core#298), whose
golang.org/x/net v0.60.0 fixes the five HTTP/2 advisories (GO-2026-6603,
-6610, -6611, -6612, -6617) the Go Vulnerability Check reports in
v0.58.0. go mod tidy also moves golang.org/x/text to v0.42.0.

The bump also brings core's other root-module changes since 474396a:

- OpenNSW#288: a BATCH_SPLIT node's partitions see only the variables its
  input_mapping names, and its output_mapping collects their values.
- OpenNSW#285: CORS Validate errors name settings by their yaml keys; the
  config tests expect the new messages.

BREAKING CHANGE: workflow artifacts with a BATCH_SPLIT must declare the
split's input_mapping (the TNSW NPQS workflows do, since
one-trade-artifacts#142).

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants