ci: automate releases with release-please and npm provenance - #1143
Open
BethGriggs wants to merge 2 commits into
Open
BethGriggs wants to merge 2 commits into
BethGriggs wants to merge 2 commits into
Conversation
Adds a release-please workflow that opens and maintains a release PR on every push to main. When the release PR is merged, the package is published to npm automatically using GitHub OIDC trusted publishing. Configuration is added so 'lookup:' commits trigger patch releases. RELEASES.md is updated accordingly. Signed-off-by: Beth Griggs <bethanyngriggs@gmail.com>
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #1143 +/- ##
=======================================
Coverage 96.20% 96.20%
=======================================
Files 29 29
Lines 2213 2213
=======================================
Hits 2129 2129
Misses 84 84 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
targos
reviewed
Sep 25, 2026
targos
approved these changes
Sep 25, 2026
targos
left a comment
targos
left a comment
Member
There was a problem hiding this comment.
I created the OIDC connection on npmjs.com
Co-authored-by: Michaël Zasso <targos@protonmail.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
3 participants
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.
Adds a release-please workflow that opens and maintains a release PR on every push to main. When the release PR is merged, the package is published to npm automatically using GitHub OIDC trusted publishing.
Configuration is added so 'lookup:' commits trigger patch releases.
RELEASES.md is updated accordingly.
I noticed I didn't have access to publish a release. Rather than asking for the access, this PR introduces automated releases for CITGM using release-please and npm trusted publishing via GitHub OIDC. I figured it made sense to align this with the automation used in
nodejs/node-core-utils.Note this does introduce slightly different/stricter commit message formatting. However, I did add a customisation so that
lookup:prefixed commits will also be treated as patches and trigger release PRs/PR updates..release-please-manifest.jsonis required because of this customisation.Note: someone with access will need to configure the Trusted Publishing in npm before the first release PR is merged:
nodejs/citgmrelease-please.ymlChecklist
npm testpasseshere