Skip to content

Exempt our own scope from the npm release-age window - #10

Merged
ABilenduke merged 1 commit into
mainfrom
docs/adr-0001-own-scope-release-age
Oct 9, 2026
Merged

ABilenduke merged 1 commit into
mainfrom
docs/adr-0001-own-scope-release-age

Conversation

@ABilenduke

Copy link
Copy Markdown
Contributor

What changed

ADR 0001 (Node.js LTS with a hardened npm) is amended: every repository that installs our packages adds min-release-age-exclude[]=@reference-systems-lab/* to its .npmrc. The Status line, the Decision and the Consequences record the change and the reason, dated 2026-10-09.

min-release-age=7 refused the design system's first release, 0.1.0, with notarget (Reference-Systems-Lab/design-system#2), so each release of ours would be unusable by the other repositories for a week. npm's min-release-age-exclude exempts named packages. Our packages are built from our own repositories, locked by hash and attested, so the waiting period's protection isn't needed for them.

Same change: Reference-Systems-Lab/design-system#7 (consumer instructions). Noted for the first consumer in Reference-Systems-Lab/commerce-storefront#2.

Verification

A scratch consumer with the hardened .npmrc plus the exclusion installed the four design-system packages at 0.1.0 and passed eslint, prettier, vue-tsc and vite build. Without it, the install failed with notarget.

Risk and rollback

Docs only; to roll back, revert this PR.

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