build(publish): set up npm publishing (OIDC provenance, tag-gated)#12
Merged
Conversation
…prx-47qm Makes the kit installable beyond bounded-systems — `npm i @bounded-systems/conformance-kit` — so it's reusable everywhere, not just git-vendored. Setting up the pipeline does NOT publish: the release only fires on a `v*` tag push (merging to main never does). - package.json: add `files` allowlist (gates/generators/integrity/emitters/lib + README/LICENSE/provenance — excludes test/fixtures), wildcard `exports` for deep imports (e.g. `@bounded-systems/conformance-kit/gates/conformance-report.mjs`), and `publishConfig` (public + provenance). Version 0.1.0 (vendored-only stub) → 0.2.0. - .github/workflows/publish.yml: on a `v*` tag, npm ci → npm test → `npm publish --provenance` via Trusted Publishing (OIDC, id-token:write — no stored NPM_TOKEN), mirroring lone's tag-gated publish. npm pack --dry-run: 35 files, 70.4 kB. Tests 17/0. NOTE — registry-side, owner only: configure the package's npm Trusted Publisher (repo + publish.yml) on npmjs.com (a brand-new name may need one manual `npm publish` to claim it first, then OIDC for subsequent tags). lone stays the JSR-published STANDARD; npm is the right home for this CLI/vendoring toolkit. 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.
The "use it everywhere" unlock (prx-47qm): makes the kit installable beyond bounded-systems —
npm i @bounded-systems/conformance-kit— so consumers can install it, not just git-vendor it.What
filesallowlist (gates / generators / integrity / emitters / lib + README/LICENSE/provenance — excludes test+fixtures), wildcardexportsfor deep imports (e.g.@bounded-systems/conformance-kit/gates/conformance-report.mjs),publishConfig(public + provenance). Version 0.1.0 → 0.2.0 (0.1.0 was the vendored-only stub).v*tag → npm ci → npm test →npm publish --provenancevia Trusted Publishing (OIDC) —id-token: write, no storedNPM_TOKEN.Verification
npm pack --dry-run→ 35 files, 70.4 kB, v0.2.0 (the right allowlist).npm test→ 17/0.Registry-side (owner only — gates the actual release)
@bounded-systems/conformance-kiton npmjs.com (this repo +publish.yml). A brand-new package name may need one manualnpm publishto claim it first, then OIDC handles subsequent tags.git tag v0.2.0 && git push origin v0.2.0triggers the release. I won't push that tag without your explicit go.Architecture note
lone stays the JSR-published standard (pure Deno/Zod model). npm is the right home for this CLI/vendoring toolkit (bins + npm deps) — JSR doesn't fit a Node CLI package. That's the honest npm-vs-JSR split, rather than forcing the kit onto JSR.
🤖 Generated with Claude Code