Repository navigation
versions: refresh, each entry to its newest in a commit, proposed once as a pull request - #114
Merged
Merged
Conversation
…e as a pull request Two of the nine repositories with a versions.yaml move their pins on a schedule, and each wrote the same shell for it: bump, commit, name a branch for what it holds, ask whether it was proposed, push, open the pull request, close the one it supersedes - spin-ami's refresh:move and refresh:propose, spin-machine's refresh:kernel and refresh:apk. The other seven move nothing until somebody looks. versions refresh <name>... is that, once, in Go with its tests: each entry bumped in a commit of its own, those with it in the same commit, an entry that cannot be moved said and the rest moved anyway. With -propose the commits are pushed as refresh/<label>-<the file's sum> and opened as one pull request whose body is what moved and what each note says to check; a set is proposed once, so one a person closed is not asked again, and a new set closes the open one of its label it supersedes. A repository's refresh is then a one-line task and a short workflow. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
aledbf
force-pushed
the
versions-refresh
branch
from
November 18, 2026 19:30
5ae66af to
5bd20ff
Compare
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.
Two of the nine repositories with a versions.yaml move their pins on a
schedule, and each wrote the same shell for it: bump, commit, name a branch
for what it holds, ask whether it was proposed, push, open the pull request,
close the one it supersedes - spin-ami's refresh:move and refresh:propose,
spin-machine's refresh:kernel and refresh:apk. The other seven move nothing
until somebody looks.
versions refresh ... is that, once, in Go with its tests: each entry
bumped in a commit of its own, those with it in the same commit, an entry
that cannot be moved said and the rest moved anyway. With -propose the
commits are pushed as refresh/-<the file's sum> and opened as one pull
request whose body is what moved and what each note says to check; a set is
proposed once, so one a person closed is not asked again, and a new set
closes the open one of its label it supersedes. A repository's refresh is
then a one-line task and a short workflow.
Tried on a clone of spin-ami without -propose: simple-icons moved to 16.38.0 in its own commit, task and kernel current; without a token, GitHub's 403 for two entries was listed and failed the run, the third still checked.
🤖 Generated with Claude Code