Skip to content

chore: manage .release-it.js through config-loom (add/refresh demo) - #111

Open
Farenheith wants to merge 1 commit into
masterfrom
feat/config-loom-release-it
Open

Farenheith wants to merge 1 commit into
masterfrom
feat/config-loom-release-it

Conversation

@Farenheith

Copy link
Copy Markdown
Member

What this PR shows

This whole diff was not hand-written — it is the literal output of the two commands from codibre/monorepo-utils#33, run once on a fresh checkout of master:

config-loom add .release-it.js
config-loom refresh .release-it.js

Result: release-it configs join the loom like tsconfig/eslint/jest already had.

Impact

config-loom.yaml — one new entry:

  • default = the canonical 3-line shim shared by the 6 TS packages;
  • one rule keeps the two Rust bridges verbatim: libs/(?:fluent-iterable-rs|fluent-lazy-structures-rs) → the cargo-publish hook config, byte-for-byte (add adopts divergent on-disk files as rules — it never rewrites what exists).

.gitignore — one line inside the loom block: libs/**/.release-it.js.

The 8 files leave the index (git rm --cached — the same contract init established): still on disk for tooling, regenerated by config-loom sync whenever missing.

Why it matters for this repo

  • The chore: add missing release-it config for lazy-structures #109 incident class dies. lazy-structures shipped without a .release-it.js, release-it fell back to factory defaults, and CI died with Not authenticated with npm. From now on, config-loom sync gives every workspace its shim — a new package cannot be born without one.
  • config-loom check (in CI / postcheckout) now also guarantees release-it config drift across packages.
  • The committed loom contains no new syntax: the released config-loom@0.10.0 renders this repo byte-identically (proven with the installed binary, check green). No dependency on unreleased features. {{root}} (from monorepo-utils#33) exists exactly to author entries like this one by hand later — here refresh normalized everything to concrete bytes.

Verified on this branch

  • config-loom check with installed 0.10.0 → check ok (all 8 files byte-identical to the committed blobs before untracking).
  • libs/fluent-iterable-rxjs: release-it --ci --dry-run under a token-less CI npmrc → path-scoped skip, zero auth errors (base guard intact through the generated file).
  • libs/fluent-iterable-rs/.release-it.js — cargo hook untouched on disk; the loom rule preserves it.
  • Full drill (before touching this repo): fresh clone + add, new-package seed, refresh idempotence — feat(config-loom): add & refresh commands monorepo-utils#33 "Verification" section.

Notes for review

  • Files show as deleted — that is the untracking contract; git show HEAD -- libs/fluent-iterable/.release-it.js vs the loom default are identical.
  • To see it live: pnpm config-loom sync then pnpm config-loom check.
  • Merge order: none. This works with the released config-loom today; monorepo-utils#33 only adds the generator commands.

Generated entirely by 'config-loom add .release-it.js' +
'config-loom refresh .release-it.js' from codibre/monorepo-utils PR #33:

- the 8 package shims leave the index; the loom reproduces them
  (byte-identical, verified with the released config-loom 0.10.0 check);
- the two -rs cargo-publish configs are adopted as a rule
  (libs/(?:fluent-iterable-rs|fluent-lazy-structures-rs)), untouched;
- .gitignore block gains 'libs/**/.release-it.js'.

New packages now inherit their release-it shim from sync — the class of
miss fixed retroactively in #109 becomes structurally impossible.

This branch has not been deployed

No deployments
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