Repository navigation
ci: propose the node image's newest digest every Monday - #81
Merged
Merged
Conversation
The ts-oracle's goldens are only as true as the Node they were made with, and its digest otherwise moves when someone runs versions check. go-tools' versions refresh -propose opens one pull request with what moved and the entry's note; parity:contract's oracle gate is the check of it. Only node is refreshed: golangci-lint is go-tools' version, distroless and go-licenses are checked by a release, which a pull request does not run, and task's note names no check of a move. The pull request is opened with the run's own token, so CI does not start on it by itself: this repository's workflows use no GitHub App. 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.
Every Monday,
refresh.ymlrunsgo tool task refresh, which is go-tools'versions refresh -propose node(v0.20261118.5). It moves thenodeimage to its newest digest in one commit and opens one pull request. The PR body has a table of what moved and the entry's note. The run does nothing when the pin is current. A set of versions is proposed only once: if a person closed it, it is not opened again.Entries chosen and why
node: its note says a bump that changes an answer fails the oracle gate, and CI'sparityjob runs that gate (parity:contractrunsTestTSOracleGoldensMatchTheReferenceagainstversions ref node).Left out
golangci-lint: go-tools' version, so it is a person's to move along with go-tools.distroless,go-licenses: their notes say a release checks them (task release --snapshot,release:smoke,release:notices), and a pull request runs none of these.task: its note names no check of a move.Its pull request starts no CI. No workflow in this repository uses the spin-stack-release GitHub App, so the PR is opened with the run's own
GITHUB_TOKEN, and GitHub starts no workflow for that. CI runs on it once a person pushes to it, or closes and reopens it. To have CI start by itself, give this repository the release app andRELEASE_APP_KEY, as spin-machine'srefresh.ymldoes. The run commits asgithub-actions[bot]through the step's env, because a runner has no git identity.The gomod block in
.github/dependabot.ymlhas no cooldown, so it needs no go-tools exclusion and is unchanged.Checked
go tool task lintpasses (taskgate: every workflow step is a task), and so doesgo tool task test:race, includingTestWorkflowsDeclarePermissions.refresh.yml.versions refresh nodewithout -propose in a throwaway clone. It committedversions: node 24-bookworm-slim, with the digest moving tosha256:dc26ae92…c54. So the first scheduled run will propose a new node digest, andparity:contractwill check it.🤖 Generated with Claude Code