ci(release): enable npm, crates.io, and pypi publishing for v0.1.0#9
Merged
Conversation
Activate the previously stubbed publish steps in the three non-Go release trains, matching the configured credentials: crates.io via CARGO_REGISTRY_TOKEN, npm via NPM_TOKEN with provenance, and PyPI via Trusted Publishing (OIDC). The npm publish runs `napi pre-publish --skip-gh-release` to ship the per-platform packages, then `npm publish --ignore-scripts` for the main package; --ignore-scripts stops the prepublishOnly hook from re-running pre-publish with its default --gh-release in a token-less job. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Give @c3-oss/codexcw a README so it renders on npmjs.com instead of a blank page, and include it in the published `files`. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Move every workflow off GitHub-hosted runners onto Blacksmith (2vcpu Linux, 6vcpu macOS, 2vcpu Windows), mirroring the c3-oss/mcp-plane convention: matrix jobs keep `matrix.os` as the display/cache-key label and add a `matrix.runs-on` Blacksmith label. The quality job passes GITHUB_TOKEN to lychee to avoid anonymous GitHub rate limits. Co-Authored-By: Claude Opus 4.8 (1M context) <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
1 participant
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.
Enables the first release of the three registry artifacts by activating the
previously stubbed publish steps in the non-Go release trains.
Changes
release-crate.yml— publishcodexcwto crates.io withCARGO_REGISTRY_TOKEN(kept the--dry-runverify step ahead of it).release-npm.yml— publish@c3-oss/codexcw+ the 7 per-platformpackages with npm provenance (
NPM_TOKEN). Usesnapi pre-publish --skip-gh-releasethennpm publish --ignore-scripts; the--ignore-scriptsstops theprepublishOnlyhook from re-running pre-publishwith its default
--gh-releasein a token-less job.release-pypi.yml— publishcodexcwvia PyPI Trusted Publishing (OIDC),no token.
bindings/node/README.md— added so the npm package renders a pageinstead of a blank one; included in the package
files.Release procedure (after merge)
Cut the train tags sequentially against the merged commit on
master, watchingeach publish before the next:
rust-v0.1.0→py-v0.1.0→node-v0.1.0.Versions are already
0.1.0across all manifests; no version bump needed.🤖 Generated with Claude Code