Repository navigation
chore: add missing release-it config for lazy-structures - #109
Merged
Merged
Conversation
Every other publishable package ships a two-line .release-it.js pulling in .release-it.base.js (npm publish:false + skipChecks:true, per-package changelog path-scoping, [skip ci] commit format, stage-publish hook). lazy-structures shipped without it, so release-it ran with factory defaults: npm auth validation enabled -> npm whoami under the CI npmrc (OIDC bearer, not a classic token) -> Not authenticated. Reproduced locally: rm config -> exact CI error; restore -> green dry-run.
Root cause was the missing per-package release-it config, not the OIDC token. The mint flow needs no diagnostics.
Farenheith
requested review from
Dodt,
danielgalleni,
douglasdrdc,
fgabrielsilva and
pedrosodre
as code owners
November 19, 2026 01:48
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.
Why
libs/fluent-iterable-lazy-structureswas merged without a.release-it.js. Every other publishable package has the two-line file wiring.release-it.base.js(npm.publish:false+skipChecks:true, path-scoped changelog/increment gate,[skip ci]commit format, stage-publish hook).Without it, release-it ran with factory defaults for this package only:
npm.publishdefaults totrueandskipCheckstofalse→ the npm plugin runs its pre-flight validation (npm ping+npm whoami+npm show);npm whoamifails in a way release-it does not tolerate →ERROR Not authenticated with npm.So the failure was package-specific by construction — no CI-wide auth bug ever existed. This also explains why the other six packages skip cleanly in the very same run and job.
Proof (local, no real credentials)
Simulating the CI npm stack (
NPM_CONFIG_USERCONFIGredirected like setup-node does, unresolvable${NODE_AUTH_TOKEN}):ERROR Not authenticated with npm. Please npm login...(identical to CI)0.1.0 → 0.2.0, hookpnpm stage publish --no-git-checks --provenance, tag stagedChanges
libs/fluent-iterable-lazy-structures/.release-it.js(same two lines as every sibling);Diagnose npm OIDC audiencestep frompublish.yaml(came in via chore(ci): temporary npm OIDC audience diagnostic #108; mint flow is fine).After merge
Dispatch
publish.yaml(dry_run=truefirst). Expect lazy-structures dry-run: minor bump, staged publish hook line; then a real dispatch queues@fluent-iterable/lazy-structures@0.2.0in the npm publish queue.