Repository navigation
chore(deps): update Go toolchain and modules - #29
Merged
Merged
Conversation
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
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.
Update the CLI and acceptance-test dependency graph to current stable releases and regenerate the module checksums with Go's resolver.
Godog now resolves Gherkin v42 and Messages v34. Its UUID dependency changes to google/uuid. The remaining upstream test dependencies were also refreshed, including go-uuid 1.0.4 and testify 1.12.1.
Breaking changes: builds now require Go 1.27.2 or later, reflected in the README. The executable acceptance suite passes against Godog's newer major schema dependencies; no application source changes were necessary.
October 13 validation passed locally with Go 1.27.2:
go test ./... -count=1,go vet ./...,gofmtcheck,go mod verify,go build ./cmd/huddlz, andgovulncheck(no vulnerabilities found). Existing checkout v7.0.1 and setup-go v7.0.0 CI actions are already current.Remaining upstream graph entry: Objx 0.5.3 now has a newer stable 0.8.0 release. During the prior update,
go get github.com/stretchr/objx@latestsucceeded, but canonicalgo mod tidyremoved that unused override; the module is not needed by this project's packages. Testify's upstream graph still declares 0.5.3. All other resolved module paths are current.CI run 38452121879 passed on commit
8b9e3c06b9626366d80b62ea9debc72c4ab4764c: Linux, macOS and Windows formatting, vet and acceptance tests all succeeded. Tag-triggered publication was not run.October 19 recheck
The canonical Go resolver (
go get -u -t ./..., thengo mod tidy) reproducedgo.modandgo.sumbyte-for-byte. Go 1.27.2, all twelve declared module paths, and the pinned checkout/setup-go actions remain current stable versions. No additional module bump is required this week.Dependency validation run 39250918059 passed module verification, formatting, vet, all tests, the CLI build, and govulncheck 1.9.0 with no vulnerabilities. These checks ran on GitHub's Linux runner; Go was not installed in the local cloud workspace. The temporary resolver workflow was removed after collecting and verifying its canonical output.
The embedded canonical timezone-name list remains at 2026c. IANA 2026e is newer, but the backend validates names against its runtime-loaded
Tzdata.canonical_zone_list(); the deployed database version could not be established from this repository. Regenerating immediately would add four accepted names without evidence the deployed backend accepts them. This is data-contract compatibility, not a Go module blocker.Final-head CI run 39251228326 passed Linux, macOS, and Windows formatting, vet, and tests on
4f4eaf3b07e23f1961ab94829e911a191a6cd7b0. The PR remains mergeable and non-draft.