ci: automate versioning and changelog with release-please - #31
Open
Amayyas wants to merge 1 commit into
Open
Conversation
- release-please-config.json + .release-please-manifest.json: node release type, keeps package.json and manifest.json versions in sync (extra-files jsonpath), plain v<version> tags. - release-please.yml: maintains the release PR (version bump + CHANGELOG), and on merge builds + attaches the Chrome/Firefox zips to the created Release (done in-workflow since GITHUB_TOKEN releases don't trigger other workflows). - Remove release.yml: the tag-triggered release flow is now superseded by release-please (single mechanism). - README: Releases section updated to the release-please flow. Builds on the Conventional-Commit PR titles (#16) and the release zips (#12).
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
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
Automated versioning + changelog (theme #5 of the CI roadmap). Builds on the Conventional-Commit PR titles (#16) and the release zips (#12).
release-please.yml+release-please-config.json+.release-please-manifest.json) — asfeat:/fix:changes land onmain, release-please keeps a release PR up to date that bumps the version and updatesCHANGELOG.md. Merging it tags the version, creates the GitHub Release with changelog notes, then this same workflow builds and attaches the Chrome/Firefox zips.release-type: nodebumpspackage.json(+ lockfile); anextra-filesjsonpath entry bumpsmanifest.jsontoo, so the two never drift (ourcheck:versionCI keeps enforcing it).release.yml(the tag-triggered flow from CI: per-browser release zips on tagged releases #12/ci: release zips per browser on tagged releases #29) is removed; release-please now drives releases end to end. Thenpm run packagescript and the zip naming are unchanged.Why the build/upload lives inside the release-please workflow
A GitHub Release created with the default
GITHUB_TOKENdoes not trigger other workflows (loop-prevention). So instead of a separateon: releaseworkflow, the zip build + upload runs in the same job, gated onsteps.release.outputs.release_created == 'true'.Permissions & supply chain
contents: write+pull-requests: writeon this workflow only.googleapis/release-please-actionpinned to16a9c90…(v4.4.0), consistent with the SHA-pinning policy from ci: add security & supply-chain hardening #17.First run after merge
release-please will open a release PR (e.g.
chore(main): release 0.x.y) based on the commits since0.1.0. Review/merge it when you actually want to cut a version — nothing is released until you do.ci:/chore:commits don't bump the version;feat:→ minor,fix:→ patch.Verification (local)
npm run lint,format:check,knip,typecheck— all pass.