chore(phrase-js): use trusted npm publishing #SCD-552#1051
Merged
BlumMichael merged 1 commit intomainfrom Feb 13, 2026
Merged
Conversation
BlumMichael
changed the title
BlumMichael
changed the title
forelabs
approved these changes
Feb 13, 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
2 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.
Fixes the phrase-js release workflow to work with trusted npm publishing and restores tag-based publishing.
phrase-js releases are triggered by push on tags, but the workflow used github.event.release.tag_name for the release tag. That field is not present on push events, which can break release creation and block npm publishing.
Also updated to node LTS version 22, because it is a requirement for OIDC to work:
https://docs.npmjs.com/trusted-publishers
Ticket:
https://phrase.atlassian.net/browse/SCD-552