Repository navigation
build: pin core at the released tag v0.19.8, and tidy go.sum - #1205
Merged
Merged
Conversation
cli#1201's final head moved core to v0.19.8-0.20261027203111-6eadd92dd156, a commit on a squash-orphaned branch (7 ahead / 1 behind both core main and the tag): `go mod download` for a release pinning it breaks the day that ref goes. The tag v0.19.8 (a06da5fc) exists and carries the same API this CLI consumes — dockerrun.ContainerServiceIdentity and the release acquisition — and the adoption guard's tests pass against it. go.sum was not tidy at the head: stale sums for the old core pseudo-versions, moby/buildkit v0.32.2, logrus and x/time. `go mod tidy` drops them. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This was referenced Oct 27, 2026
# Conflicts: # go.sum
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.
What
go.mod: corev0.19.8-0.20261027203111-6eadd92dd156→v0.19.8(the released tag,a06da5fc). The pseudo-version named a commit on a squash-orphaned branch — 7 ahead / 1 behind both core main and the tag — so a release pinning it would breakgo mod downloadthe day that ref disappears. The tag carries the same API this CLI consumes (dockerrun.ContainerServiceIdentity, release acquisition).go.sum:go mod tidy— drops the stale sums the the first-Init port guard excuses every container this service's agent kept #1201 re-check named (both old core pseudo-versions,moby/buildkit v0.32.2, logrus,x/time).Evidence
go build ./...,go vet ./pkg/orchestration/ ./cmd/run/, and the adoption guard's tests (Adopt|FirstInit|PublishesAddress) pass against the tag. Nox-access-tokeningo.sum.Why before v0.1.220
The release cut from main would otherwise pin the orphaned commit. Publish was stopped before #1203 merged for exactly this; v0.1.220 is cut once this and #1206 are on main.
🤖 Generated with Claude Code
After #1209 merged (main
8056b9da)Main now pins core at the tag
v0.19.8itself (the e9cf stack carried that), so this PR collapses to itsgo mod tidy: 8 stalego.sumlines for four orphaned core pseudo-versions (6eadd92d,b14f7188,3d31544a,bc4e15ca) dropped;go.modidentical to main. Brought current by merging main (no force-push).go test ./pkg/engine/ ./pkg/orchestration/green against the tag — the authenticated-v2 reader test that was red before #1209 now passes.