Skip to content

docs: close npm-provenance verification (0.2.0 shipped with provenance)#14

Merged
SutuSebastian merged 1 commit into
mainfrom
docs/provenance-verified-strike-roadmap
Jul 6, 2026
Merged

docs: close npm-provenance verification (0.2.0 shipped with provenance)#14
SutuSebastian merged 1 commit into
mainfrom
docs/provenance-verified-strike-roadmap

Conversation

@SutuSebastian

@SutuSebastian SutuSebastian commented Jul 6, 2026

Copy link
Copy Markdown
Contributor

0.2.0 published with SLSA provenance v1 + Sigstore signatures via npm trusted publishing (OIDC) — verified (npm view @stainless-code/persist@0.2.0 shows dist.attestations.provenance). The NPM_TOKEN repo secret is deleted.

  • Strike the roadmap.md "npm provenance — verify on next release" bullet (complete).
  • Append "Sigstore provenance is auto-generated" to CONTRIBUTING.md § Releases (the non-duplicating home for release-workflow facts; architecture.md § Publishing covers the package surface, not releases).

Docs-only.

… provenance in CONTRIBUTING

0.2.0 published with SLSA provenance v1 + Sigstore signatures via npm
trusted publishing (OIDC) — verified (`npm view …@0.2.0` shows
`dist.attestations.provenance`). The `roadmap.md` "npm provenance —
verify on next release" bullet is complete (NPM_TOKEN repo secret also
deleted), so strike it. The durable "trusted publishing + provenance"
fact already lives in CONTRIBUTING.md § Releases; append "Sigstore
provenance is auto-generated" there rather than duplicating into
architecture.md § Publishing (which covers the package surface, not the
release workflow).
@coderabbitai

coderabbitai Bot commented Jul 6, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@SutuSebastian, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 38 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 88d782bd-23e6-493f-b868-f2f25f0c9887

📥 Commits

Reviewing files that changed from the base of the PR and between d75117f and 67ec983.

📒 Files selected for processing (2)
  • .github/CONTRIBUTING.md
  • docs/roadmap.md
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch docs/provenance-verified-strike-roadmap

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@changeset-bot

changeset-bot Bot commented Jul 6, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 67ec983

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@SutuSebastian SutuSebastian merged commit 77c8a77 into main Jul 6, 2026
12 checks passed
@SutuSebastian SutuSebastian deleted the docs/provenance-verified-strike-roadmap branch July 6, 2026 11:27
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.

1 participant