Repository navigation
Release workflow (npm Trusted Publishing) and CI - #1
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Adds:
ci.yml: typecheck + e2e tests on every PR and push to main.release.yml: on tagvX.Y.Z(must equal package.json version), test andnpm publishwith Trusted Publishing (OIDC, provenance, no stored token), same setup as coderbuzz/codex.repository/homepagein package.json (Trusted Publishing requiresrepository.urlto match this repo).Before the first tag: npm cannot attach a Trusted Publisher to a package that does not exist yet, so 0.1.0 is published once by hand, then npmjs.com > @coderbuzz/dsh > Settings > Trusted Publisher = GitHub Actions, coderbuzz / dsh / release.yml, with "Allow npm publish".
🤖 Generated with Claude Code