Skip to content

go-tools: refresh:kernel is versions refresh; go-tools without the cooldown - #267

Merged
aledbf merged 2 commits into
mainfrom
rollout/go-tools
Nov 18, 2026
Merged

aledbf merged 2 commits into
mainfrom
rollout/go-tools

Conversation

@aledbf

@aledbf aledbf commented Nov 18, 2026

Copy link
Copy Markdown
Member

Rolls out go-tools v0.20261118.5's versions refresh here.

  • dependabot: go-tools without the cooldown. go-tools is ours, and its releases are now tagged v0.<date>.<n>, so Dependabot's gomod update can move it the week a release is made. go.mod's go-tools is left as it is: Dependabot moving it is the check that this works.
  • taskfile: refresh:kernel is versions refresh. The task's shell (bump, branch, ls-remote, push, gh pr create, close superseded) becomes versions refresh -propose -label kernel kernel. The pull request's body is now built from the entries' notes, so what the task's body said - kernel.yml builds it; before merging, boot it with task kernel:build boot:ssh-first - is in versions.yaml's kernel note. refresh.yml's step now passes the app's token as GITHUB_TOKEN as well as GH_TOKEN: versions refresh takes GITHUB_TOKEN first, and the workflow sets it to the run's own token at the top, which has contents: read and would start no checks on the pull request. GH_TOKEN stays for the push, which goes through gh auth setup-git. refresh:apk is unchanged.

The branch name changes from refresh/kernel-<version> to refresh/kernel-<first 12 hex of versions.yaml's sha256>. "Proposed already" is now decided by the file's sum, and still covers closed pull requests. An open pull request with the old naming is closed as superseded by the next refresh that proposes something, because the match is on the refresh/kernel- prefix. A version proposed and closed under the old naming could be proposed once more under the new one.

Checked: go tool task lint and go tool task test pass. In a throwaway clone of this branch, go run github.com/spin-stack/go-tools/cmd/versions@v0.20261118.5 refresh kernel (without -propose) printed "Every entry is at its newest.", because the kernel is at 7.3.5, and changed nothing. versions refresh kernel run through go tool task gave the same result, so the command is on the task's PATH. The first real -propose run is refresh.yml's next scheduled one.

🤖 Generated with Claude Code

aledbf and others added 2 commits November 18, 2026 16:51
go-tools is ours, and a release of it is made to be taken: waiting a week
for it to settle guards against nothing. Its releases are tagged
v0.<date>.<n> now, so Dependabot can see them.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
go-tools' versions refresh does what the task's shell did - bump, commit,
push a branch, open the pull request, close the one it supersedes - and is
the same command in every repository that proposes a refresh. The branch
is named for versions.yaml's sum (refresh/kernel-<sum>) rather than the
version, so a set proposed once, closed or not, is still not asked again.

The pull request's body is built from the entries' notes, so what the task
said to do before merging - boot it, task kernel:build boot:ssh-first - is
in the kernel's note now. refresh.yml hands the app's token as GITHUB_TOKEN
too: refresh takes it before GH_TOKEN, and the workflow sets it to the
run's own, which can neither open the pull request nor start its checks.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@aledbf
aledbf merged commit 20e1a73 into main Nov 18, 2026
7 checks passed
@aledbf
aledbf deleted the rollout/go-tools branch November 18, 2026 19:54
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