Skip to content

versions: refresh, each entry to its newest in a commit, proposed once as a pull request - #114

Merged
aledbf merged 1 commit into
mainfrom
versions-refresh
Nov 18, 2026
Merged

aledbf merged 1 commit into
mainfrom
versions-refresh

Conversation

@aledbf

@aledbf aledbf commented Nov 18, 2026

Copy link
Copy Markdown
Member

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

…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
aledbf merged commit ead1d13 into main Nov 18, 2026
3 checks passed
@aledbf
aledbf deleted the versions-refresh branch November 18, 2026 19:37
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