Skip to content

chore(release): cut v0.8.0-rc.1 — Trusted Publishing smoke test#479

Merged
Luis85 merged 1 commit into
mainfrom
chore/release-v0.8.0-rc.1
May 10, 2026
Merged

chore(release): cut v0.8.0-rc.1 — Trusted Publishing smoke test#479
Luis85 merged 1 commit into
mainfrom
chore/release-v0.8.0-rc.1

Conversation

@Luis85
Copy link
Copy Markdown
Owner

@Luis85 Luis85 commented May 10, 2026

Summary

Bump package.json + README + docs/specorator.md + CHANGELOG to v0.8.0-rc.1 so the next release dispatch exercises npmjs.com Trusted Publishing on a low-stakes version before we cut v0.8.0 final.

Why

ADR-0041's NPM_TOKEN fallback shipped v0.7.0 / v0.7.1. ADR-0044 (landed in #478) restored the OIDC + --provenance path after the npmjs.com Trusted Publisher was activated against release.yml on the release deployment environment (closes #411). The first dispatch under the new auth is the v0.8.0 release. If the Trusted Publisher configuration is misaligned (wrong workflow ref, wrong environment, wrong repo) the publish step fails closed, and recovery either repairs the config + re-dispatches or reverts ADR-0044 with a one-line PR re-adding NODE_AUTH_TOKEN and falling back to NPM_TOKEN.

Cutting v0.8.0-rc.1 first burns the RC slot rather than 0.8.0 if the validation fails. If the RC dispatch succeeds, we follow up with a back-bump PR (0.8.0-rc.1 -> 0.8.0), tag, and dispatch.

Surface content

Unchanged from v0.8.0 — this is a TP smoke test, not new feature work. README banner and docs/specorator.md version line reframe as RC; CHANGELOG adds a one-paragraph [v0.8.0-rc.1] section above the planned [v0.8.0] entry.

Test plan

  • npm run check:fast (with sites workspace installed) — 445 tests pass under sequential pool.
  • npm run check:public-surfaces — README badge + status line and docs/specorator.md version line match package.json#version 0.8.0-rc.1.
  • npm run check:claude-plugin — bundle absent on this branch (gitignored), so structural-only.
  • CI green on this PR.
  • After merge: tag v0.8.0-rc.1, dispatch release.yml -f version=0.8.0-rc.1 -f dry_run=false -f prerelease=true -f publish_package=true -f confirm=0.8.0-rc.1. Expected: OIDC mints, npm publish --provenance succeeds, npm view specorator@0.8.0-rc.1 --json | jq '.dist.attestations' returns a sigstore provenance URL.
  • If RC publish succeeds: open back-bump PR 0.8.0-rc.1 -> 0.8.0 and proceed with v0.8.0 final dispatch.

Out of scope

  • v0.8.0 final dispatch (handled separately after RC validates).
  • Decommissioning the NPM_TOKEN repo secret (handled after first successful OIDC publish per ADR-0044).

🤖 Generated with Claude Code

Release-candidate dispatch slot for the v0.8.0 cycle. Smoke-tests the
restored npmjs.com Trusted Publishing path (ADR-0044, supersedes
ADR-0041) before the v0.8.0 final dispatch — exercises the OIDC
+ --provenance shape end-to-end on a low-stakes version.

Surface content unchanged from v0.8.0:
- README badge + status banner reframed as RC; references ADR-0044 and
  acknowledges v0.7.x shipped via the ADR-0041 NPM_TOKEN fallback.
- docs/specorator.md version line updated; v0.8.x publish-via-OIDC
  narrative replaces the earlier "deferred per ADR-0041" line.
- CHANGELOG adds a minimal [v0.8.0-rc.1] section above the planned
  [v0.8.0] entry.

Post-RC: bump back to 0.8.0 in a follow-up PR, tag, dispatch v0.8.0
final.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@Luis85 Luis85 merged commit c7fc549 into main May 10, 2026
11 checks passed
@Luis85 Luis85 deleted the chore/release-v0.8.0-rc.1 branch May 10, 2026 21:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants