Skip to content

ci: propose the node image's newest digest every Monday - #81

Merged
aledbf merged 1 commit into
mainfrom
rollout/go-tools
Nov 18, 2026
Merged

aledbf merged 1 commit into
mainfrom
rollout/go-tools

Conversation

@aledbf

@aledbf aledbf commented Nov 18, 2026

Copy link
Copy Markdown
Member

Every Monday, refresh.yml runs go tool task refresh, which is go-tools' versions refresh -propose node (v0.20261118.5). It moves the node image 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's parity job runs that gate (parity:contract runs TestTSOracleGoldensMatchTheReference against versions 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 and RELEASE_APP_KEY, as spin-machine's refresh.yml does. The run commits as github-actions[bot] through the step's env, because a runner has no git identity.

The gomod block in .github/dependabot.yml has no cooldown, so it needs no go-tools exclusion and is unchanged.

Checked

  • go tool task lint passes (taskgate: every workflow step is a task), and so does go tool task test:race, including TestWorkflowsDeclarePermissions.
  • actionlint v1.7.12 reports nothing for refresh.yml.
  • I ran versions refresh node without -propose in a throwaway clone. It committed versions: node 24-bookworm-slim, with the digest moving to sha256:dc26ae92…c54. So the first scheduled run will propose a new node digest, and parity:contract will check it.

🤖 Generated with Claude Code

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>
@aledbf
aledbf merged commit f3807c4 into main Nov 18, 2026
13 checks passed
@aledbf
aledbf deleted the rollout/go-tools branch November 18, 2026 20:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant