chore(ci): Automate releases with release-please and add the npm badge - #2
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.
What
release-please.yml: on every push tomain, maintain a Release PR (version bump + CHANGELOG from conventional commits); merging it tags, creates the GitHub Release, publishes to npm, and attaches the tarball — all in one run.release-please-config.json+.release-please-manifest.json(bootstrapped at 0.2.3).docs/runbooks/release.md: new versioning rules — no manualpackage.jsonbumps, no manual tags,fix:/feat:trigger releases.Why
Tags were being pushed by hand. Publishing must live in the release-please run because tags created with
GITHUB_TOKENnever triggerrelease.yml(kept only as an emergency fallback).Requires (org admin)
Org Settings → Actions → General → Allow GitHub Actions to create and approve pull requests — without it release-please cannot open the Release PR.