Add workflow support for trusted publishing #300
Merged
Conversation
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
Buqeta
previously approved these changes
Dec 18, 2025
jetakasabaqi
previously approved these changes
Dec 18, 2025
promeris
reviewed
Dec 18, 2025
ZgjimHaziri
dismissed stale reviews from jetakasabaqi and Buqeta
via
066ad7e
|
Buqeta
approved these changes
Dec 18, 2025
promeris
approved these changes
Dec 18, 2025
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
The missing requirements of trusted publishing using OpenID in our workflow:
Added explicit npm version installation in the publish workflow. And added the repository metadata in package.json.
Note: I already ran the publishing manually, will just update the workflows now to fit the solution.
Relevant links
https://docs.npmjs.com/trusted-publishers
Checklist