fix: build core before extension release verification#230
Merged
Conversation
Fresh release checkouts have no core dist output, while extension workspaces resolve core types through package exports. Build core before verifying extensions and retry the unpublished train as 0.1.1-rc.1.
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.
Fresh publish checkouts do not contain packages/json-document/dist, while extension typechecks resolve core through package exports. This builds core before extension release verification and advances the unpublished extension retry to 0.1.1-rc.1 so the failed rc.0 tag remains immutable. Local clean-checkout simulation passed all three extension verifies and dry-run packs; docs, metadata, lockfile, and registry availability checks passed.