ci+docs: auto-create GitHub Releases from CHANGELOG + README npm link - #20
Merged
Conversation
- publish.yml: on each v* tag, extract that version's CHANGELOG section and create a GitHub Release (pre-release for -alpha/-beta/-rc), so tags never ship without notes again. Needs contents: write. - CHANGELOG: lead the 2.0.0-beta.2 entry with the @grapesjs/react-parity restructure headline. - README: add an explicit npm package link and install via @beta (the newest build ships under the beta dist-tag).
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
Follow-up housekeeping after the
v2.0.0-beta.2release.publish.yml— release notes baked into the processOn every
v*tag push, a new Create GitHub Release step extracts that version's section fromCHANGELOG.md(Keep a Changelog format) and creates the GitHub Release — marked pre-release for-alpha/-beta/-rc, falling back to GitHub's auto-generated notes if no CHANGELOG section exists. No more bare, noteless tags. Addscontents: write(needed forgh release create); the npm publish step is unchanged.CHANGELOG.mdLead the
2.0.0-beta.2entry with a headline framing the@grapesjs/react-parity restructure.README.md@beta— the newest build ships under thebetadist-tag, so a plainnpm installcurrently resolves to an older beta.Note
The two existing tags already have GitHub Releases (created retroactively from these same CHANGELOG sections).