build(deps): bump the golangx group with 5 updates#456
build(deps): bump the golangx group with 5 updates#456dependabot[bot] wants to merge 1 commit intomainfrom
Conversation
WalkthroughThe PR updates five indirect Go module requirements in Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes 🚥 Pre-merge checks | ✅ 3 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing touches🧪 Generate unit tests (beta)
No actionable comments were generated in the recent review. 🎉 Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Fix all issues with AI agents
In `@go.mod`:
- Around line 82-86: Replace the invalid golang.org/x/term v0.40.0 entry with
the existing v0.39.0 and address golang.org/x/text v0.34.0's breaking changes:
either pin golang.org/x/text to the previous compatible version (e.g., v0.33.0)
or keep v0.34.0 but run full text/IDNA/domain normalization tests and update any
callers that rely on old IDNA/Unicode behavior; after editing the module lines
for golang.org/x/term and golang.org/x/text run go get to fetch the chosen
versions, run go mod tidy, and execute the test suite to verify no regressions.
| golang.org/x/net v0.50.0 // indirect | ||
| golang.org/x/oauth2 v0.35.0 // indirect | ||
| golang.org/x/sys v0.41.0 // indirect | ||
| golang.org/x/term v0.40.0 // indirect | ||
| golang.org/x/text v0.34.0 // indirect |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
# Check if go.mod exists and read lines 82-86
wc -l go.mod
sed -n '75,95p' go.modRepository: package-operator/boxcutter
Length of output: 1078
🌐 Web query:
golang.org/x/net v0.50.0 security vulnerabilities release notes
💡 Result:
golang.org/x/net v0.50.0 (published/tagged Feb 9, 2026)
There are no dedicated “release notes” for golang.org/x/net v0.50.0; the v0.50.0 tag points at a commit whose message is essentially “go.mod: update golang.org/x dependencies” (i.e., a dependency-rollup style release). [1]
Go package index pages show v0.50.0 as published on Feb 9, 2026. [2]
Security vulnerabilities status (relevant advisories)
As of this release, the most recent Go vulnerability reports affecting golang.org/x/net were:
- CVE-2025-58190 / GO-2026-4441:
golang.org/x/net/htmlhtml.Parseinfinite loop DoS. Affected: before v0.45.0 (so v0.50.0 is not affected). [3] - CVE-2025-47911 / GO-2026-4440:
golang.org/x/net/htmlquadratic complexity DoS. Affected: before v0.45.0 (so v0.50.0 is not affected). [4] - CVE-2025-22870 / GO-2025-3503: proxy bypass via IPv6 zone IDs. Fixed in v0.36.0 (so v0.50.0 is not affected). [5]
Where to see “what changed” for v0.50.0
Use the repository’s tag (v0.50.0) and compare it to the previous tag (v0.49.0) in the upstream repo history; the tag metadata is here. [1]
Sources: [1] [2] [3] [4] [5]
🌐 Web query:
golang.org/x/oauth2 v0.35.0 security vulnerabilities
💡 Result:
No security vulnerabilities are currently listed as affecting golang.org/x/oauth2 v0.35.0 in the Go/OSV advisory data.
The known vulnerability for this module is:
- CVE-2025-22868 / GO-2025-3488 / GHSA-6v2p-p543-phr9: malformed token can cause unexpected memory consumption (DoS) during parsing in
golang.org/x/oauth2/jws. It affects all versions < v0.27.0 and is fixed in v0.27.0—so v0.35.0 is not affected. [1] [2]
Reference for the version you asked about:
golang.org/x/oauth2v0.35.0 is published Jan 12, 2026 on pkg.go.dev. [3]
Sources: OSV advisory (GO-2025-3488) [1], GitHub Advisory (GHSA-6v2p-p543-phr9) [2], pkg.go.dev module page [3].
🌐 Web query:
golang.org/x/sys v0.41.0 security vulnerabilities
💡 Result:
As of February 12, 2026, the Go Vulnerability Database lists one vulnerability affecting golang.org/x/sys:
- GO-2022-0493 / CVE-2022-29526 –
golang.org/x/sys/unix.Faccessatcould incorrectly report a file as accessible when called with non-zero flags. It affectsgolang.org/x/sys/unixversions beforev0.0.0-20220412211240-33da011f77ad.golang.org/x/sys v0.41.0is newer than that and is not affected. [1]
golang.org/x/sys v0.41.0 is published on Feb 8, 2026. [2]
Conclusion: there are no known Go Vulnerability Database issues that apply to golang.org/x/sys v0.41.0 (the one known issue is fixed long before this release). [1][2]
Sources
- Go Vulnerability Database entry for GO-2022-0493 (CVE-2022-29526) [1]
golang.org/x/sysmodule page showingv0.41.0(published Feb 8, 2026) [2]
🌐 Web query:
golang.org/x/term v0.40.0 security vulnerabilities
💡 Result:
As of February 12, 2026, there is no golang.org/x/term release v0.40.0 on pkg.go.dev (the latest tagged version shown there is v0.39.0, published Jan 9, 2026). [1]
Also, the Go Vulnerability Database (the source used by govulncheck and browsable on pkg.go.dev/vuln) does not list any vulnerability reports for golang.org/x/term (i.e., no GO-IDs/CVEs/GHSAs mapped to that module). [2][3]
How to verify in your own project (recommended):
go install golang.org/x/vuln/cmd/govulncheck@latest
govulncheck ./...govulncheck queries the Go Vulnerability Database at vuln.go.dev by default. [3]
Sources:
[1] pkg.go.dev module page for golang.org/x/term (shows latest version) (pkg.go.dev)
[2] Go Vulnerability Database search UI (pkg.go.dev/vuln) (pkg.go.dev)
[3] govulncheck documentation (default DB behavior) (pkg.go.dev)
Citations:
- 1: https://pkg.go.dev/golang.org/x/term?utm_source=openai
- 2: https://pkg.go.dev/vuln/?utm_source=openai
- 3: https://pkg.go.dev/golang.org/x/vuln/cmd/govulncheck?utm_source=openai
🌐 Web query:
golang.org/x/text v0.34.0 security vulnerabilities breaking changes
💡 Result:
golang.org/x/text v0.34.0 (tagged Feb 9, 2026): breaking/behavior changes
Between v0.33.0 → v0.34.0, the repo includes a batch of changes (8 commits / 103 files) that are potentially behavior-breaking even though the tag itself is just a go.mod/go.sum refresh. Key items called out in the compare log include: update to Unicode 17, IDNA algorithm updates, and deleting old Unicode tables / old Go-version compatibility code. [1]
Concretely, expect possible breakage in these areas:
- Unicode data-dependent behavior changes (e.g., normalization, properties, case/width behavior, collation-related outputs) due to the Unicode 17 table regen. [1]
- IDNA behavior changes (domain name processing) due to “update for post‑Unicode 10 idna changes” and related cleanups. This can change what inputs are considered valid / how they map. [1]
- Build/compatibility break if you rely on older Go versions: the repo is explicitly removing code/tables for older Go versions and notes “go.mod … requires Go 1.24”. [1]
The v0.34.0 tag commit itself is “go.mod: update golang.org/x dependencies” (e.g., bumps golang.org/x/tools and golang.org/x/mod). [2]
Security vulnerabilities relevant to v0.34.0
From the Go vulnerability database (authoritative for Go module vulns), the main historical vulns in golang.org/x/text/language are:
- GO-2022-1059 (CVE-2022-32149): DoS via crafted
Accept-Languageheader parsed byParseAcceptLanguage. Affected: before v0.3.8 (fixed in v0.3.8). v0.34.0 is not affected. [3] - GO-2021-0113 (CVE-2021-38561): malformed language tag can trigger panic (OOB read) in parsing. Affected: before v0.3.7 (fixed in v0.3.7). v0.34.0 is not affected. [4]
If you want, tell me what version you’re upgrading from (and which subpackages you use: language, unicode/norm, secure/precis, width, etc.) and I’ll narrow this to the changes most likely to impact your code/tests.
Sources: [1] [2] [3] [4]
golang.org/x/term v0.40.0 does not exist; the latest available version is v0.39.0.
This must be corrected in go.mod. Additionally, golang.org/x/text v0.34.0 contains breaking changes—Unicode 17 table updates and IDNA algorithm changes—that affect domain name validation and text normalization behavior. These require testing to ensure no unexpected changes in your text/language processing. The other modules (golang.org/x/net v0.50.0, golang.org/x/oauth2 v0.35.0, golang.org/x/sys v0.41.0) have no known vulnerabilities affecting these versions.
🤖 Prompt for AI Agents
In `@go.mod` around lines 82 - 86, Replace the invalid golang.org/x/term v0.40.0
entry with the existing v0.39.0 and address golang.org/x/text v0.34.0's breaking
changes: either pin golang.org/x/text to the previous compatible version (e.g.,
v0.33.0) or keep v0.34.0 but run full text/IDNA/domain normalization tests and
update any callers that rely on old IDNA/Unicode behavior; after editing the
module lines for golang.org/x/term and golang.org/x/text run go get to fetch the
chosen versions, run go mod tidy, and execute the test suite to verify no
regressions.
Bumps the golangx group with 5 updates: | Package | From | To | | --- | --- | --- | | [golang.org/x/net](https://github.com/golang/net) | `0.49.0` | `0.50.0` | | [golang.org/x/oauth2](https://github.com/golang/oauth2) | `0.34.0` | `0.35.0` | | [golang.org/x/sys](https://github.com/golang/sys) | `0.40.0` | `0.41.0` | | [golang.org/x/term](https://github.com/golang/term) | `0.39.0` | `0.40.0` | | [golang.org/x/text](https://github.com/golang/text) | `0.33.0` | `0.34.0` | Updates `golang.org/x/net` from 0.49.0 to 0.50.0 - [Commits](golang/net@v0.49.0...v0.50.0) Updates `golang.org/x/oauth2` from 0.34.0 to 0.35.0 - [Commits](golang/oauth2@v0.34.0...v0.35.0) Updates `golang.org/x/sys` from 0.40.0 to 0.41.0 - [Commits](golang/sys@v0.40.0...v0.41.0) Updates `golang.org/x/term` from 0.39.0 to 0.40.0 - [Commits](golang/term@v0.39.0...v0.40.0) Updates `golang.org/x/text` from 0.33.0 to 0.34.0 - [Release notes](https://github.com/golang/text/releases) - [Commits](golang/text@v0.33.0...v0.34.0) --- updated-dependencies: - dependency-name: golang.org/x/net dependency-version: 0.50.0 dependency-type: indirect update-type: version-update:semver-minor dependency-group: golangx - dependency-name: golang.org/x/oauth2 dependency-version: 0.35.0 dependency-type: indirect update-type: version-update:semver-minor dependency-group: golangx - dependency-name: golang.org/x/sys dependency-version: 0.41.0 dependency-type: indirect update-type: version-update:semver-minor dependency-group: golangx - dependency-name: golang.org/x/term dependency-version: 0.40.0 dependency-type: indirect update-type: version-update:semver-minor dependency-group: golangx - dependency-name: golang.org/x/text dependency-version: 0.34.0 dependency-type: indirect update-type: version-update:semver-minor dependency-group: golangx ... Signed-off-by: dependabot[bot] <support@github.com>
4acb43d to
d6e0d7a
Compare
Bumps the golangx group with 5 updates:
0.49.00.50.00.34.00.35.00.40.00.41.00.39.00.40.00.33.00.34.0Updates
golang.org/x/netfrom 0.49.0 to 0.50.0Commits
ebddb99go.mod: update golang.org/x dependencies4a490d4internal/http3: add Expect: 100-continue support to ClientConn73fe701internal/http3: add Expect: 100-continue support to Serveraf0c9dfhtml: add NodeType.String() methode02fb33internal/http3: make responseWriter.Flush write headers if not done yetda558ffinternal/http3: ensure bodyReader cannot be read after being closedd7c76fainternal/http3: make responseWriter behave closer to other http.ResponseWriter64b3af9http2: prevent transport deadlock due to WINDOW_UPDATE that exceeds limit1973e8dinternal/http3: add Server support for handling HEAD requests57ea86dicmp, internal/socket, ipv4, ipv6: use binary.NativeEndianUpdates
golang.org/x/oauth2from 0.34.0 to 0.35.0Commits
89ff2e1google: add safer credentials JSON loading options.Updates
golang.org/x/sysfrom 0.40.0 to 0.41.0Commits
fc646e4cpu: use IsProcessorFeaturePresent to calculate ARM64 on windowsf11c7bbwindows: add IsProcessorFeaturePresent and processor feature constsd25a7aaunix: add IoctlSetString on all platforms6fb913bunix: return early on error in RecvmsgUpdates
golang.org/x/termfrom 0.39.0 to 0.40.0Commits
3aff304go.mod: update golang.org/x dependenciesUpdates
golang.org/x/textfrom 0.33.0 to 0.34.0Commits
817fba9go.mod: update golang.org/x dependencies3264de9all: clean up old Go hacks74af298all: fix tags in remaining Unicode tables117e03ball: delete old Unicode tables9463ea4all: update to Unicode 177278b25internal/export/idna: update for post-Unicode 10 idna changesf964ad8internal/export/idna: delete old code678d34eunicode/norm: preserve QC Maybe bit in packed forminfoDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditions