Repository navigation
chore: staged publishing for TS releases (pnpm 12 + pnpm stage publish) - #106
Merged
Merged
Conversation
- .release-it.base.js after:bump: pnpm publish -> pnpm stage publish, mirroring monorepo-utils: CI queues the version (OIDC provenance) and the owner approves from the npm publish queue with 2FA proof-of-presence. The -rs bridges override this hook with the cargo script; crates.io is unaffected. - packageManager pnpm@11.1.3 -> pnpm@12.21.0: the stage command only exists in pnpm 12 (verified: 11.1.3 'Command stage not found'). chore commit on purpose: path-scoped release-it ignores chore, so nothing releases by merging this. Local gates on pnpm 12.21.0: install clean (lockfile = package-manager metadata only, zero dependency changes); turbo build 9/9; lazy 12/12; augmentative 53/53; config-loom check ok. (pre-commit skipped: husky env resolves a stale corepack pnpm 11.1.3 -> version guard, not a lint failure; CI lints the branch.)
Farenheith
requested review from
Dodt,
danielgalleni,
douglasdrdc,
fgabrielsilva and
pedrosodre
as code owners
November 19, 2026 01:03
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
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.
Every TS package now stages instead of publishing live, same as monorepo-utils (
.release-it.base.js:54there): CI queues the version with OIDC provenance; you approve with 2FA proof-of-presence (pnpm stage approveor the npm publish queue).The pnpm pin bump is required:
pnpm stagedoes not exist in pnpm@11.1.3 (current pin); 12.21.0 is exactly what monorepo-utils runs. Lockfile diff is pnpm-12 package-manager-dependency metadata only — zero dependency version changes.All
chorecommits — path-scoped release-it won't fire a release from this PR.-rsbridges override the hook with the cargo script → crates.io unaffected.The run-44428219192 failure, precisely
Not authenticated with npmis not about staging: release-it authenticates CI with the GitHub OIDC token, and the registry accepts it only when the package's Trusted Publisher names this repo +publish.yaml. The older packages have that relationship (@codibre/fluent-iterable@2.0.1published from CI on Nov 14); the three-hour-old@fluent-iterable/lazy-structuresdoes not. One-time npmjs.com click — same triple as crates.io: ownercodibre/ repofluent-iterable/ workflowpublish.yaml. With that + this PR, the next publish run stages lazy-structures 0.2.0 for your approval.