Repository navigation
chore(deps): merge main and clear all 19 Dependabot alerts (x/crypto 0.57.0, grpc 1.83.2) - #13
Merged
Conversation
Bumps the go_modules group with 1 update in the / directory: [golang.org/x/crypto](https://github.com/golang/crypto). Updates `golang.org/x/crypto` from 0.40.0 to 0.45.0 - [Commits](golang/crypto@v0.40.0...v0.45.0) --- updated-dependencies: - dependency-name: golang.org/x/crypto dependency-version: 0.45.0 dependency-type: indirect dependency-group: go_modules ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
This branch had gone stale: it proposes golang.org/x/crypto 0.40.0 -> 0.45.0, but main has been on 0.49.0 for nine commits, so the bump would have moved backwards. The go.mod/go.sum conflict is therefore resolved by taking main wholesale — the branch side had nothing left worth keeping — and the real upgrades are applied on top rather than reconciled hunk by hunk between two outdated version sets. golang.org/x/crypto 0.49.0 -> 0.57.0 13 alerts, 7 critical google.golang.org/grpc 1.80.0 -> 1.83.2 4 alerts golang.org/x/net 0.52.0 -> 0.59.0 1 alert github.com/moby/go-archive 0.2.0 -> 0.3.3 1 alert x/crypto landed on 0.57.0 rather than the 0.56.0 this fleet usually pins: asking for both x/net@latest and x/crypto@v0.56.0 in one `go get` fails outright — x/net 0.59.0 requires x/crypto 0.57.0 — and a `go get` that cannot satisfy every argument upgrades nothing at all. Letting x/net pull its own floor lands higher than the pin would have. Worth noting against theplant/qor5-ai-demo, patched the same day: there moby/go-archive had to be pinned *down* to 0.1.0, because docker 28.5.2's deprecated pkg/archive shim needs the older API. Same package, opposite directions — the constraint comes from each module graph, not from the package. Verified: go build, go vet and go mod tidy -diff all pass, go test with CI's own flags (-p=1 -count=1 -failfast) passes, and govulncheck reports no vulnerabilities. All 19 alerts checked against their own vulnerable_version_range; none still inside. The go directive already reads 1.26.0 and is untouched — CI takes its Go version from go.mod via go-version-file. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
shenzhaoyan
changed the title
shenzhaoyan
approved these changes
Sep 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps the go_modules group with 1 update in the / directory: golang.org/x/crypto.
Updates
golang.org/x/cryptofrom 0.40.0 to 0.45.0Commits
4e0068cgo.mod: update golang.org/x dependenciese79546essh: curb GSSAPI DoS risk by limiting number of specified OIDsf91f7a7ssh/agent: prevent panic on malformed constraint2df4153acme/autocert: let automatic renewal work with short lifetime certsbcf6a84acme: pass context to requestb4f2b62ssh: fix error message on unsupported cipher79ec3a5ssh: allow to bind to a hostname in remote forwarding122a78fgo.mod: update golang.org/x dependenciesc0531f9all: eliminate vet diagnostics0997000all: fix some commentsDependabot 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 mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@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 conditionsYou can disable automated security fix PRs for this repo from the Security Alerts page.