fix: depend on published metadata-connect instead of a local file path - #12
Merged
Merged
Conversation
…cal path package.json pointed metadata-connect at file:../metadata-connect, so a clean install only worked on a machine that happened to have that sibling checkout. metadata-connect 1.2.0 is on npm now, so depend on ^1.2.0 and record the registry resolution in the lockfile. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Owner
|
@Kyuko Thank you for catching that! |
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
2 participants
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.
Switches the
metadata-connectdependency fromfile:../metadata-connectto the published^1.2.0on npm. The local-path reference brokenpm install/npm cifor anyone without a siblingmetadata-connectcheckout. Build and full test suite pass from a cleannpm ci.