ci: publish package using npm trusted publisher with OIDC#1319
Merged
pedro-martins-brisa merged 5 commits intomainfrom Jan 22, 2026
Merged
Conversation
jairo-chaves-brisa
approved these changes
Jan 15, 2026
nathan-moura-brisa
approved these changes
Jan 15, 2026
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.
Description
This pull request updates the release workflow to clearly separate the build and publish steps using different Node versions.
The project build remains on Node 12.22.1 to preserve compatibility with legacy dependencies, while the npm publish step is migrated to Node 20, which is required to properly support modern npm features such as OIDC authentication and provenance (--provenance).
This change improves the security and reliability of the release process without impacting the existing build behavior.
Compliance
References