feat(node): exclude own org packages from pnpm release cooldown#54
Merged
Conversation
pnpm 11 defaults minimumReleaseAge to 1440 minutes, so a freshly published version is not resolved until it is a day old. That cooldown also stalls the org's own packages, blocking fast internal iteration. Add a minimumReleaseAgeExclude block with the @sebastian-gmbh/* and @sebastian-software/* scope globs to the reference and repo pnpm-workspace.yaml so internal releases install immediately while third-party deps keep the secure default. Ship change 0006 (standards version 6) with a judgement step, since pnpm-workspace.yaml is a reference file that apply does not write.
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.
Requirement
The org's own npm packages must load directly, without pnpm's minimum release age cooldown — for every
@sebastian-gmbh/*and@sebastian-software/*package. Added to the node standard and the changelog.Problem
pnpm 11 enables supply-chain protection by default:
minimumReleaseAgedefaults to1440minutes (24h), so a freshly published version is not resolved until it is a day old (pnpm 11 notes). Good for third-party deps, but it also makes a just-released@sebastian-software/*/@sebastian-gmbh/*version invisible to consumers for 24h, blocking fast internal iteration and back-to-back releases.Fix
pnpm's
minimumReleaseAgeExcludeaccepts name patterns (pnpm 10.17 notes). Exempt only the two org scopes; every third-party dependency keeps the secure default.Changes
reference/node/pnpm-workspace.yaml+ repopnpm-workspace.yaml: add theminimumReleaseAgeExcludeblock.changes/0006-pnpm-minimum-release-age-exclude.md: new changelog (node scope, standards v6) with a judgement step.pnpm-workspace.yamlis a reference file only — not managed/seeded (itsallowBuildslist is repo-specific) — sostandards applydoes not write it; propagation to existing repos is the judgement step, per the SKILL.md config-merge rule.manifest.jsoncurrentVersion5 → 6,.repometa.jsonstamp 5 → 6,test/standards.test.tsselectChangesexpectations extended to 6.docs/plan/0015-pnpm-minimum-release-age-exclude.md: completion doc.Verification
pnpm agent:checkgreen — lint, format:check, typecheck, build, 75 tests, andstandards checkself-check (repo matches its own standards at v6).🤖 Generated with Claude Code