Let the source feed update itself when a release is published - #28
Merged
Merged
Conversation
The workflow has only ever worked from a manual run. On a release event `actions/checkout` takes the tag, so the job built `docs/apps.json`, committed it, and then could not push it: "fatal: You are not currently on a branch". Publishing 0.3.7 hit exactly that, leaving the feed pointing at 0.3.6 with the release already out. It now checks out the default branch, which is where the commit belongs — the feed is rebuilt from the GitHub API, never from the tree — and pushes there explicitly. 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.
Found while publishing 0.3.7.
update-sourcehas only ever worked from a manual run. On areleaseeventactions/checkouttakes the tag, so the job builtdocs/apps.json, committed it, and then could not push:That is run 35521862717 on the 0.3.7 release — the feed stayed on 0.3.6 with the release already published. It predates #10's merge into a release flow; the
apps.jsoncommits onmainso far came from manual dispatches, which check out a branch and so push fine.The job never needs the tagged tree — it rebuilds the feed from the GitHub API — so it now checks out the default branch, where the commit belongs, and pushes there explicitly.
Verified after merge by re-running the workflow against the published 0.3.7 release.
🤖 Generated with Claude Code