Skip to content

Release 0.2.0 - #10

Merged
birazzzz merged 1 commit into
mainfrom
release/v0.2.0
Oct 21, 2026
Merged

birazzzz merged 1 commit into
mainfrom
release/v0.2.0

Conversation

@birazzzz

Copy link
Copy Markdown
Collaborator

Bumps the version to 0.2.0, the first release through the new workflow (#9).

What's in 0.2.0

Also

RELEASING.md now sets up the trusted publisher with npm trust on the command line (the website form never saved for wrapguard; the CLI did, and npm trust list confirms birazzzz/wrapguard, release.yml, stage publish).

After merging

Publish a GitHub release tagged v0.2.0 on main. The Release workflow tests, stages 0.2.0 on npm and moves v0; then approve it under Staged Packages on npmjs.com.

- 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.
@birazzzz
birazzzz merged commit ca5fcf7 into main Oct 21, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant