Bump go-containerregistry to v0.22.0 and modernc.org/sqlite to v1.57.0 - #3
Merged
Merged
Conversation
Minor bump of the registry-polling library and patch bump of the SQLite driver behind the journal. go mod tidy also promotes golang.org/x/sync to a direct requirement, correcting a stale indirect marker: cmd/snowdeployd imports errgroup.
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.
Dependency currency only — no code changes. Nothing live moves: the host runs a released binary pinned by a snowsys bundle; these bumps ride the next release.
Bumps
internal/registry,internal/revision, viapkg/name+pkg/v1/remote)Transitives pulled along by go-containerregistry:
docker/cliv29.6.2 → v29.7.2 (indirect),klauspost/compressv1.19.1 → v1.19.2 (indirect).go mod tidyalso promotedgolang.org/x/syncfrom indirect to direct —cmd/snowdeploydimportserrgroup, so the indirect marker was stale.go-containerregistry v0.22.0 highlights relevant to this repo
remote; a transient failure while setting up the puller is now retried instead of surfacing immediately, which should make polling against a briefly flaky registry quieter.pkg/nameparsing loosened slightly; no manifest we accept gets stricter.mutate/tarballoptions, and their Cloud Build tooling — none exercised here.modernc.org/sqlite v1.57.0 is the driver's routine upstream refresh; the journal package's behavior is covered by its own tests below.
Verification
All run at go-containerregistry v0.22.0 / sqlite v1.57.0 in a clean worktree off
origin/main:go build ./...— cleango vet ./...— cleango test -race ./...— all packages ok, includinginternal/registryandinternal/journalgolangci-lint run(v2.12.2, matching CI) — 0 issues