docs: capture release-please single-root-package lesson#229
Open
theagenticguy wants to merge 1 commit into
Open
docs: capture release-please single-root-package lesson#229theagenticguy wants to merge 1 commit into
theagenticguy wants to merge 1 commit into
Conversation
Document why collapsing to a single root release-please component with a scoped package-name cannot create a release (the `||` coercion derives a component the component-less release PR can't match -> release_created=false -> npm never publishes), and that the fix is two components + the linked-versions plugin so the published CLI bumps on every commit. Indexed in .erpaval/INDEX.md.
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
1 participant
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
Captures the durable lesson from this session's release-pipeline recovery as an ERPAVal solution doc + index pointer.
.erpaval/solutions/conventions/release-please-single-root-package-cannot-release.md— why a single root release-please component with a scopedpackage-namecannot create a release in release-please v17 (this.component = options.component || normalizeComponent(packageName)falsy-coerces an empty component → derivescli→buildRelease's standalone-component check rejects the component-less release PR →release_created=false→ npm never publishes), and the fix: two components + thelinked-versionsplugin so the published CLI bumps in lockstep with root on every commit. Also documents the migration gotchas (boundary tags, the manual-recovery / OIDC trusted-publisher trap)..erpaval/INDEX.md— one-line pointer to the new lesson.Why
This bug (npm stuck at 0.7.4 while the private root ran ahead) cost a multi-attempt recovery; the single-component "fix" turned out structurally impossible. Documenting it so a future session reaches for
linked-versionsdirectly instead of rediscovering the||coercion the hard way.Docs-only; no code or release-config change.