fix: incorrect semver version constraints#9
Draft
vardumper wants to merge 2 commits into
Draft
Conversation
Author
|
actually not really a code change - just a package.json fix based upon v5.0.5 tag ref. |
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.
Problem
Yarn Berry doesn't support semver range operators (like
^) with Git URL dependencies. When using Git URLs with branch or tag references, the caret operator causes dependency resolution to fail or behave unexpectedly.Changes
Removed the
^prefix from the following Git URL dependencies:@ibexa/frontend-config: Changed from#^v5.0.0to#v5.0.0@ibexa/ts-config: Changed from#^v1.1.1to#v1.1.3Impact
This fix ensures proper dependency resolution with Yarn Berry (4.x), allowing the project to install dependencies without errors.
References
Git URL dependencies should always specify exact tags or commits, not semver ranges. The
^operator only works with npm registry versions.