Repository navigation
Create the GitHub release from the changelog when a version is tagged - #524
Merged
Merged
Conversation
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.
After a pushed version tag is staged on npm, a second job creates the GitHub release with that version's section of
doc/release-notes/changelog.mdas its notes, so the release notes no longer need to be written by hand. Links to the docs are made absolute, as the changelog links them relative to the docs site.Prereleases are marked as such, and only versions on the
latestdist-tag become the latest release. The job fails if the changelog has no section for the version. It runs in its own job, so only it can write to the repository, and the npm job keeps read-only access.