ci: make the release a reconciler, not a trigger - #8
Merged
Conversation
Mirrors ai-forms#17, where this was not theoretical: that repo's merge to main started no publish run, because auto-merge merges with GITHUB_TOKEN and a push with that token starts no workflow. The identical change fired here only because I merged this repo's PR by hand with a user token. threadkit has no auto-merge today, which is exactly why the schedule belongs here now — rather than being added after auto-merge arrives and a release quietly goes missing. The question the workflow asks — "is package.json's version on the registry?" — is idempotent, so asking it hourly costs one `npm view` when there is nothing to do and repairs a missed release when there is. Co-Authored-By: Claude Opus 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
1 participant
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.
Mirrors ai-forms#17, where this was not theoretical: that repo's merge to main started no publish run, because auto-merge merges with
GITHUB_TOKENand a push with that token starts no workflow. The identical change fired here only because I merged this repo's PR by hand with a user token.threadkit has no auto-merge today — which is exactly why the schedule belongs here now, rather than being added after auto-merge arrives and a release quietly goes missing.
The question the workflow asks — is
package.json's version on the registry? — is idempotent, so asking it hourly costs onenpm viewwhen there's nothing to do, and repairs a missed release when there is.🤖 Generated with Claude Code