docs(releasing): three-field version bump, exact core pin, core-before-cli publish order - #849
Merged
Merged
Conversation
…e-cli publish order The #847 version gate fails the old single-workspace bump flow, and the exact @codeburn/core pin makes publish order load-bearing: a CLI published before its core version exists on the registry is uninstallable.
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.
Required follow-up to #847 (flagged in its review): RELEASING.md still documented
npm version -w codeburn, which bumps only the CLI and now failscheck:workspace-versions, and it never mentioned publishing@codeburn/core— which must now go FIRST, since the CLI's exact pin makes it uninstallable until its core version exists on the registry (verifiedETARGETfailure mode in the #847 review). Docs only.