fix: stage npm releases with OIDC

[mynameistito]

Summary

• stage npm releases directly through trusted publishing
• remove the stage list preflight, which npm does not authorize for OIDC trust tokens
• add a patch changeset and update the release regression test

Testing

• bun test
• bun run typecheck
• bun run check
• bun run build

---

Summary by cubic

Fix npm release staging with OIDC trusted publishing by skipping the unsupported npm stage list and staging directly with npm stage publish. This unblocks releases for @mynameistito/codex-usage.

• Bug Fixes
  • Remove npm stage list preflight (not authorized with OIDC trust tokens).
  • Update release regression test to expect direct staging.

^{Written for commit ca1317c. Summary will update on new commits.}

Note

Fix npm staged releases to skip npm stage list when using OIDC trusted publishing

• Removes the pre-check that called npm stage list <package> --json before publishing, since this command is unsupported in trusted publishing (OIDC) environments.
• runNpmRelease in publish.ts now goes directly from a 404 on npm view to executing npm stage publish ..
• Behavioral Change: when a version is already staged, the function no longer exits early with staged: 'true'; instead it falls through to the publish conflict check and writes published: 'true'.

^{Macroscope summarized ca1317c.}

[changeset-bot]

🦋 Changeset detected

Latest commit: ca1317c

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@mynameistito/codex-usage	Patch

Not sure what this means? Click here to learn what changesets are.

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

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 44 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: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 38772af9-a892-4f74-a42f-bf3d3362e812

📥 Commits

Reviewing files that changed from the base of the PR and between aed73db and ca1317c.

📒 Files selected for processing (3)

• .changeset/every-seals-kick.md
• __tests__/release.test.ts
• scripts/publish.ts

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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

[pkg-pr-new]

Open in StackBlitz

bun add https://pkg.pr.new/@mynameistito/codex-usage@ca1317c

commit: ca1317c

[cubic-dev-ai]

No issues found across 3 files

_{Re-trigger cubic}