build(deps): bump the root dependencies and point the examples at v1.11.8 - #330
Merged
Merged
Conversation
…11.8 Supersedes #281, #282, #283 and #284, which had gone stale sitting open since 2026-08-17. Two of them would have landed a repository that was already behind on the day it merged. #281 proposed `golang.org/x/crypto` v0.55.0 and v0.56.0 is out; #284 pinned the nine examples to `authcore` v1.11.7 and 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. Root, five direct dependencies as before: - `golang.org/x/crypto` v0.54.0 to v0.56.0 - `golang.org/x/net` v0.57.0 to v0.58.0 - `golang.org/x/text` v0.40.0 to 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 have added three files that every future bump has to keep in step, which is the coupling the workspace removed. Signed-off-by: Jaro-c <75870284+Jaro-c@users.noreply.github.com>
Jaro-c
added
type:deps
This was referenced Sep 7, 2026
Merged
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.
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/cryptov0.55.0 when v0.56.0 is out, and #284 pins the nine examples toauthcorev1.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:
golang.org/x/cryptogolang.org/x/netgolang.org/x/textExamples:
authcorev1.11.6 to v1.11.8 in all nine, andgofiber/fiber/v3v3.4.0 to v3.5.0 in the fiber example, which carriesfasthttp,klauspost/compressandmattn/go-isattywith it.ginwas already on v1.12.0, the current release.What I measured
govulncheck ./...go test -race ./...go build && go vetgodirective, all 11 module filesOne latent entry remains, in a module I require but do not call: the standing
GO-2026-5932advisory thatx/crypto/openpgpis unmaintained and unsafe by design,Fixed in: N/A, applying to every version of the module since 0. Nothing here importsopenpgp.Three files this deliberately does not add
go mod tidyunderGOWORK=offwrote ago.suminto the apikey, basic and username examples, which have never carried one. Those three depend on nothing butauthcore, 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:govulncheckwas already clean at v1.11.8, so nothing here closes an open advisory.