Release new artifacts - #37
Conversation
|
=== branch-name === Running benchmark: branch-name-eval ✓ [1/3] Feature Branch Naming 🧪 Waza Eval ResultsStatus: ✅ Passed | Score: 1.00 | Duration: 224ms
Task Results
Benchmark: branch-name-eval | Skill: git/branch-name | Model: claude-sonnet-4-20250514 === commit-message === Running benchmark: commit-message-eval ✓ [1/3] Basic Bug Fix Commit 🧪 Waza Eval ResultsStatus: ✅ Passed | Score: 1.00 | Duration: 226ms
Task Results
Benchmark: commit-message-eval | Skill: git/commit-message | Model: claude-sonnet-4-20250514 === pr-title-description === Running benchmark: pr-title-description-eval ✓ [1/3] Basic Feature PR 🧪 Waza Eval ResultsStatus: ✅ Passed | Score: 1.00 | Duration: 241ms
Task Results
Benchmark: pr-title-description-eval | Skill: git/pr-title-description | Model: claude-sonnet-4-20250514 ═══════════════════════════════════════════════ Skill Status Pass Rate Avg Score |
6809313 to
262e196
Compare
|
=== branch-name === Running benchmark: branch-name-eval ✓ [1/3] Feature Branch Naming 🧪 Waza Eval ResultsStatus: ✅ Passed | Score: 1.00 | Duration: 239ms
Task Results
Benchmark: branch-name-eval | Skill: git/branch-name | Model: claude-sonnet-4-20250514 === commit-message === Running benchmark: commit-message-eval ✓ [1/3] Basic Bug Fix Commit 🧪 Waza Eval ResultsStatus: ✅ Passed | Score: 1.00 | Duration: 245ms
Task Results
Benchmark: commit-message-eval | Skill: git/commit-message | Model: claude-sonnet-4-20250514 === pr-title-description === Running benchmark: pr-title-description-eval ✓ [1/3] Basic Feature PR 🧪 Waza Eval ResultsStatus: ✅ Passed | Score: 1.00 | Duration: 252ms
Task Results
Benchmark: pr-title-description-eval | Skill: git/pr-title-description | Model: claude-sonnet-4-20250514 ═══════════════════════════════════════════════ Skill Status Pass Rate Avg Score |
## Problem Published packages (e.g. `@kin0992/oxc-config@0.3.0`) have **no provenance** — the registry's attestation endpoint returns `Not found` and the #37 release log never printed a "Signed provenance statement". Root cause, from the release log: - The `Configure npm scope auth` step wrote the npm token into `.npmrc`, so `changeset publish` authenticated **by token**. - `changeset publish` did not produce provenance under that path, despite `NPM_CONFIG_PROVENANCE: true` and `publishConfig.provenance: true`. - changesets/action even reported `OIDC is available - using npm trusted publishing`, but the on-disk token overrode it. ## Change Switch to pure **npm Trusted Publishing (OIDC)**: - Remove the `Configure npm scope auth` step (no token on disk). - Remove `NODE_AUTH_TOKEN` from the publish env. - Keep `id-token: write` and `NPM_CONFIG_PROVENANCE`. npm then exchanges the workflow's id-token for a short-lived credential and **signs provenance automatically**. ## Required manual step before merging / next release A **Trusted Publisher** must be configured on npmjs.org for each package, or the next publish will fail auth: > npmjs.org → each of `@kin0992/{oxc-config,skills,tsconfig,vitest-config}` → Settings → Trusted Publisher → GitHub Actions → owner `kin0992`, repo `dev-toolkit`, workflow `release.yml`. Provenance attaches on the **next** version bump; existing `0.3.0` can't be back-filled. `npm_token` secret / `registry-url` input are left declared (marked deprecated) for backward compatibility with any other callers. 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@kin0992/oxc-config@0.3.0
Minor Changes
51632aa: Publish to the public npm registry (npmjs.org) with provenance.
These packages now ship from
https://registry.npmjs.orgunder public accessinstead of GitHub Packages. Consumers no longer need a
read:packagestoken ora scoped
.npmrcentry — a plainpnpm add @kin0992/<pkg>works anonymously.Existing GitHub Packages versions remain available but will not receive updates.
Patch Changes
CHANGELOG.mdfiles in the shared oxfmt and oxlint configs so generatedchangelogs are left untouched by formatting and linting.
@kin0992/skills@0.2.0
Minor Changes
51632aa: Publish to the public npm registry (npmjs.org) with provenance.
These packages now ship from
https://registry.npmjs.orgunder public accessinstead of GitHub Packages. Consumers no longer need a
read:packagestoken ora scoped
.npmrcentry — a plainpnpm add @kin0992/<pkg>works anonymously.Existing GitHub Packages versions remain available but will not receive updates.
@kin0992/tsconfig@0.1.0
Minor Changes
51632aa: Publish to the public npm registry (npmjs.org) with provenance.
These packages now ship from
https://registry.npmjs.orgunder public accessinstead of GitHub Packages. Consumers no longer need a
read:packagestoken ora scoped
.npmrcentry — a plainpnpm add @kin0992/<pkg>works anonymously.Existing GitHub Packages versions remain available but will not receive updates.
@kin0992/vitest-config@0.1.0
Minor Changes
51632aa: Publish to the public npm registry (npmjs.org) with provenance.
These packages now ship from
https://registry.npmjs.orgunder public accessinstead of GitHub Packages. Consumers no longer need a
read:packagestoken ora scoped
.npmrcentry — a plainpnpm add @kin0992/<pkg>works anonymously.Existing GitHub Packages versions remain available but will not receive updates.