Repository navigation
chore: manage .release-it.js through config-loom (add/refresh demo) - #111
Open
Farenheith wants to merge 1 commit into
Open
Farenheith wants to merge 1 commit into
Farenheith wants to merge 1 commit into
Conversation
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.
Farenheith
requested review from
Dodt,
danielgalleni,
douglasdrdc,
fgabrielsilva and
pedrosodre
as code owners
November 19, 2026 10:41
This branch has not been deployed
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.
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:
Result: release-it configs join the loom like tsconfig/eslint/jest already had.
Impact
config-loom.yaml— one new entry: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 byconfig-loom syncwhenever missing.Why it matters for this repo
.release-it.js, release-it fell back to factory defaults, and CI died withNot authenticated with npm. From now on,config-loom syncgives 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.config-loom@0.10.0renders this repo byte-identically (proven with the installed binary,checkgreen). No dependency on unreleased features.{{root}}(from monorepo-utils#33) exists exactly to author entries like this one by hand later — hererefreshnormalized everything to concrete bytes.Verified on this branch
config-loom checkwith 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-rununder 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.add, new-package seed,refreshidempotence — feat(config-loom): add & refresh commands monorepo-utils#33 "Verification" section.Notes for review
git show HEAD -- libs/fluent-iterable/.release-it.jsvs the loom default are identical.pnpm config-loom syncthenpnpm config-loom check.