Setup NPM trusted publishing#57
Merged
Merged
Conversation
![atlassian[bot]](https://avatars.githubusercontent.com/in/14320?s=60&v=4){kind=small}
|
|
||
| - run: yarn publish | ||
| - name: Publish to npm | ||
| run: npm publish --provenance |
There was a problem hiding this comment.
⚠️ Maintainability - DevOps
Since @get-dx/backstage-plugin is a scoped package, npm defaults to restricted access — add --access public to avoid a publish failure: npm publish --provenance --access public.
Details
📖 Explanation: Since this is a scoped package (@get-dx/backstage-plugin), npm defaults to restricted (private) access. Without --access public, the publish will fail unless the package was explicitly configured as public on npm already.
emmahoggan
approved these changes
Jun 22, 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.
This changes our
publishworkflow configuration so we can use NPM trusted publishing. I've already made the config changes on the NPM side, so once this merges, the publish should happen.Rovo Dev code review: Rovo Dev is reviewing this pull request…
Refresh the page in a few minutes to see the results.