Fail CI when the latest release loses skill-demo.pdf - #20
Merged
Merged
Conversation
The README links to releases/latest/download/skill-demo.pdf, which only resolves while the release GitHub calls "latest" carries an asset under exactly that filename. v1.1.0 shipped with no assets, became latest, and the link 404'd for the 54 minutes until v1.1.1 replaced it. The rule was already written down and it still broke, so make it a check rather than a thing to remember. Runs on release events, weekly, and on demand. It polls first, because `gh release create` uploads assets after the release row exists, then verifies the public URL returns 200 and that the body really is a PDF. 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.
What
A new workflow,
.github/workflows/release-assets.yml, that fails when the release GitHub calls latest does not carryskill-demo.pdf.Why
README.mdlinks toreleases/latest/download/skill-demo.pdf. That URL resolves only while the latest release has an asset under exactly that filename.v1.1.0shipped at 15:41 with no assets attached, became latest, and the README link 404'd untilv1.1.1went out at 16:35 with the asset. Nobody reported it. The rule was already written down whenv1.0.0was tagged and it still broke, which is the argument for a check instead of a reminder.How it works
releaseevents (published,edited,released,deleted), weekly on a cron, and onworkflow_dispatch.gh release createuploads assets after the release row exists, so thepublishedevent can arrive ahead of the file.%PDF-. A 200 alone is not enough, since an error page is also a 200.permissions: contents: read, matchingci.yml.Verification
The exact shell in both steps was run against the live repo:
Nothing in
ci.ymlis touched, so the three required check names are unchanged.🤖 Generated with Claude Code