Repository navigation
Release 0.2.0 - #10
Merged
Merged
Conversation
- Version 0.2.0: moved elements are matched by text instead of being reported as changed (#8), and releases go out through trusted publishing (#9). - RELEASING.md: set up the trusted publisher with `npm trust` from the command line (the website form never saved for wrapguard), check it with `npm trust list`, and note the 0.0.0-stage placeholder for new packages.
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.
Bumps the version to 0.2.0, the first release through the new workflow (#9).
What's in 0.2.0
--verboseand never fails the check. The JSON output andDiffResultgain amovedlist, which is why this is a minor version.Also
RELEASING.mdnow sets up the trusted publisher withnpm truston the command line (the website form never saved for wrapguard; the CLI did, andnpm trust listconfirmsbirazzzz/wrapguard,release.yml,stage publish).After merging
Publish a GitHub release tagged
v0.2.0onmain. The Release workflow tests, stages 0.2.0 on npm and movesv0; then approve it under Staged Packages on npmjs.com.