fix(self-modification): release CI - resolve packed eve locally - #2576
Merged
Conversation
Signed-off-by: Andrew Barba <barba@hey.com>
Contributor
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.
Summary
Release PR #2514 exposed that the packed-package scenario resolves
@eve/self-modification's rewrittenevedependency from npm, where the Changesets-bumped version is not published yet. The disposable consumer now writes a pnpm workspace override that resolves everyevedependency from the locally packed tarball. This is test-only and does not change published package behavior.Validation
Reproduced with
eve@0.45.0onchangeset-release/main, then confirmed the focused package-consumption scenario passes and the replacement CI workflow on #2514 is green.Checklist
CONTRIBUTING.mdevepackagegit commit --signoff)Diff size
Docs — 0 files ·
+0 / -0Not applicable.
Implementation — 0 files ·
+0 / -0Not applicable; published package behavior is unchanged.
Tests — 1 file ·
+5 / -0Makes the existing package-consumption scenario hermetic when Changesets has bumped
eveto an unpublished version.