ci: create a GitHub Release automatically on tag push#124
Merged
Conversation
The release workflow only published to PGXN; the GitHub Release steps were commented out and used actions/create-release + actions/upload-release-asset, which GitHub archived in 2021, plus an empty latest-changes.md for the body. Replace them with the maintained softprops/action-gh-release@v2, which creates the release for the pushed tag, uploads the pgxn-bundle archive as an asset, and auto-generates release notes. Grant the job contents:write so the token can create the release. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Both pages.yml and jekyll-gh-pages.yml were copies of the GitHub Pages
starter template configured with `source: ./docs`, but the repository has
no `docs/` directory and no Jekyll config. As a result the "Deploy Jekyll"
workflow failed on every push to main (the github-pages build aborts with
"No such file or directory - .../docs"), and pages.yml targeted a `master`
branch that does not exist, so it never ran.
Building from the repository root is not an option either: the github-pages
gem refuses it ("Destination directory cannot be or contain the Source
directory") because the `_site` output lives inside the source root.
Neither workflow has ever produced a site, so remove both to stop the
perennial failed deploy. GitHub Pages can be reintroduced later with a real
docs source if desired.
Co-Authored-By: Claude Opus 4.8 (1M context) <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.
Summary
The release workflow (
.github/workflows/release.yml) only published to PGXN — the GitHub Release steps were commented out and usedactions/create-release+actions/upload-release-asset, both archived by GitHub in 2021, withbody_pathpointing at an emptylatest-changes.md.Replace them with the maintained
softprops/action-gh-release@v2, which:v*tag automatically (alongside the PGXN publish),pgxn-bundlearchive as a release asset,Adds
permissions: contents: writeso the workflow token can create the release. Step order is preserved (bundle → PGXN publish → GitHub Release), so the irreversible PGXN step runs first.Test Plan
v3.1.11— the Release workflow should publish to PGXN and create thev3.1.11GitHub Release with the bundle asset.🤖 Generated with Claude Code