Publish npm packages with provenance #1615
Conversation
| - run: npm ci | ||
| - run: npm publish | ||
| - run: npm run build --if-present | ||
| - run: npm version ${TAG_NAME} --git-tag-version=false |
There was a problem hiding this comment.
Does this mean we can create releases without having to push a version bump to main?
Will we lose the tags and version in our package file by doing this? Sounds nice being able to release without the extra push but also I like having tags and the right version in the JSON 😅
There was a problem hiding this comment.
Does this mean we can create releases without having to push a version bump to main?
Yes.
Will we lose the tags and version in our package file by doing this? Sounds nice being able to release without the extra push but also I like having tags and the right version in the JSON 😅
Also yes. Typically I set package.json version to 0.0.0-development so it's clear that the version is generated.
There was a problem hiding this comment.
No worries I think that makes sense. @koddsson can you update the package version so that is clear?
* Publish npm packages with provenance * Set version to 0.0.0 because we dynamically generate it now
This will allow us to have a cool badge on npm.
Example:
