Repository navigation
chore: release 0.1.0 - #5
Merged
Merged
Conversation
- Version 0.1.0 (rc.2 passed the full production run on both install routes). - verify-release.sh: bypass npm's metadata cache (--prefer-online) so a check run right after a publish does not fail on a stale registry listing. - configure-repo-security.sh: the release environment allows self-review, matching the decision taken on the live repository; re-running the script no longer flips it back.
YoanPtr
approved these changes
Oct 2, 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.
Release PR for
v0.1.0.0.1.0inpackage.jsonandnpm-shrinkwrap.json.v0.1.0-rc.2passed the full production run on both install routes (binary and npm, macOS arm64): sign-in,whoami,tools list, a read-only call in all five formats, server-side logout/revocation, and no token in the captured output. Provenance and attestations verify.scripts/verify-release.shnow bypasses npm's metadata cache (--prefer-online); a check run right after a publish failed on a stale registry listing.scripts/configure-repo-security.shsetsprevent_self_review: falseon thereleaseenvironment, matching the live setting, so re-running it no longer reverts it.After merge: tag
v0.1.0on the merge commit; the release workflow builds, attests, creates the GitHub release, publishes to npm (latest, with provenance) after environment approval, and opens the Homebrew tap PR.🤖 Generated with Claude Code