Repository navigation
release: v<YYYYMMDD>.<NN> by release.yml after CI, and go tool task runs the latest go-tools - #101
Merged
Merged
Conversation
…atest Releases are named as spin-stack names releases (internal/release, as spin's releaseversion): v<YYYYMMDD>.<NN>, the day in UTC and its number. release.yml makes one of main each time CI passes on it - the commit that passed - builds, attests, and publishes last, with a checksums.txt; a commit released already is that release, not a second one. cmd/task takes go-tools from the latest release, held to the sha256 its checksums give, asking which is the latest at most every ten minutes and going on with the last one offline (internal/toolcache's Latest). No versions.yaml pins go-tools, so the gate asks only for task. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…that nothing refused Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Follow-up to #100, after a decision (2026-11-09):
versions.yaml.Releases (
release.yml)workflow_runwhen CI succeeds on a push to main. It checks out the commit that passed, not whatever main is by then.v<YYYYMMDD>.<NN>, as spin'shack/releaseversion: the UTC day and the day's sequence number, two digits (internal/release,internal/release/cmd/releasename).vYYYYMMDD.NNisn't three-number semver, sogo getnever takes these tags for module versions.attest-build-provenance) and publishes last. The release creates the tag, so a failed publish leaves no tag without files.checksums.txt.releasejob leavesci.yml. One release at a time (concurrency: release).go tool task(cmd/task)versions.yaml, pinned by sha256 per platform, as before.toolcache.Latest)./releases/latestredirect, which counts against no API quota.checksums.txtand unpacks it once.cmd/taskingo.modit only requirestask. Thego-toolsentry and its tie togo.modgo away.What this gives up
With no pin, a go-tools release reaches every repository's next run without a PR in each. It's protected by the gate that passed on main and the attestation, not by a sha in each repository.
checksums.txtguards against a corrupt download, not a malicious release.Checked
task lint,task testandtask sitepass.go run ./cmd/mutate -base origin/main -max 600: 0 survived.release:nameandrelease:buildran locally: the next name today, and the checksums of the four archives.bin-20261109.212154, from #100, stays as an old release. The firstv...is cut when this merges, and becomes thelatest.🤖 Generated with Claude Code