Conversation
…11.8 (#330) Supersedes #281, #282, #283 and #284. Closing those four in favour of this one. They had been open since 2026-08-17, and two of them would have landed a repository that was already behind on the day it merged: #281 proposes `golang.org/x/crypto` v0.55.0 when v0.56.0 is out, and #284 pins the nine examples to `authcore` v1.11.7 when v1.11.8 shipped this morning. Re-landing the same four bumps at the versions that are actually current costs one branch and avoids merging a correction that needs correcting. ### What moves Root, still five direct dependencies: | Module | From | To | |---|---|---| | `golang.org/x/crypto` | v0.54.0 | v0.56.0 | | `golang.org/x/net` | v0.57.0 | v0.58.0 | | `golang.org/x/text` | v0.40.0 | v0.41.0 | Examples: `authcore` v1.11.6 to v1.11.8 in all nine, and `gofiber/fiber/v3` v3.4.0 to v3.5.0 in the fiber example, which carries `fasthttp`, `klauspost/compress` and `mattn/go-isatty` with it. `gin` was already on v1.12.0, the current release. ### What I measured | Check | Result | |---|---| | `govulncheck ./...` | exit 0, **No vulnerabilities found** | | `go test -race ./...` | 9/9 packages pass | | Nine examples, `go build && go vet` | 9/9 pass, one package each | | `go` directive, all 11 module files | untouched at 1.26.6 | One latent entry remains, in a module I require but do not call: the standing `GO-2026-5932` advisory that `x/crypto/openpgp` is unmaintained and unsafe by design, `Fixed in: N/A`, applying to every version of the module since 0. Nothing here imports `openpgp`. ### Three files this deliberately does not add `go mod tidy` under `GOWORK=off` wrote a `go.sum` into the apikey, basic and username examples, which have never carried one. Those three depend on nothing but `authcore`, and the workspace resolves it from the checkout, so there is no hash to record. I deleted them and confirmed all three still build and vet. Committing them would add three files that every future bump has to keep in step, which is the coupling the workspace removed. ### Release This changes a dependency floor, which the releases standard counts as something a consumer receives, so it wants a tag rather than sitting on `develop`. It is not urgent the way #328 was: `govulncheck` was already clean at v1.11.8, so nothing here closes an open advisory. Signed-off-by: Jaro-c <75870284+Jaro-c@users.noreply.github.com>
Jaro-c
added
type:deps
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.
Release
v1.11.9, one commit: #330.Why this earns a tag rather than waiting
The root
requireblock movedgolang.org/x/cryptofrom v0.54.0 to v0.56.0,golang.org/x/netfrom v0.57.0 to v0.58.0 andgolang.org/x/textfrom v0.40.0 to v0.41.0. Under minimal version selection a consumer's build resolves to the maximum of every requirement in the graph, so raising ours raises theirs. The releases standard names dependency floors as something a consumer receives, which is exactly what this is, andmainsitting behinddevelopmeans the change does not exist for anyone.It is not urgent the way v1.11.8 was.
govulncheckwas already clean at v1.11.8 and stays clean here, so nothing in this release closes an open advisory.The examples half of #330 (
authcorev1.11.6 to v1.11.8 in all nine,gofiber/fiber/v3v3.4.0 to v3.5.0) reaches no consumer at all: the examples are standalone modules precisely so gin and fiber never enter anyone's dependency graph. It rides along because it was in the same branch, not because it earns anything.What this supersedes
#281, #282, #283 and #284, the four Dependabot pull requests open since 2026-08-17, are closed. Two of them had gone stale: #281 proposed
x/cryptov0.55.0, overtaken by v0.56.0, and #284 pinned the examples toauthcorev1.11.7, replaced by v1.11.8 this morning. #282 and #283 were still current and were folded in rather than merged separately.Verification
govulncheck ./...go test -race ./...go build && go vetgodirective, all 11 module filesThe one latent entry is the standing
GO-2026-5932advisory thatx/crypto/openpgpis unmaintained and unsafe by design,Fixed in: N/Asince version 0 of the module. Nothing here importsopenpgp.