Skip to content

fix: incorrect semver version constraints#9

Draft
vardumper wants to merge 2 commits into
ibexa:masterfrom
vardumper:yarn-berry-compatibility
Draft

fix: incorrect semver version constraints#9
vardumper wants to merge 2 commits into
ibexa:masterfrom
vardumper:yarn-berry-compatibility

Conversation

@vardumper
Copy link
Copy Markdown

@vardumper vardumper commented Feb 7, 2026

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.0 to #v5.0.0
  • @ibexa/ts-config: Changed from #^v1.1.1 to #v1.1.3

Impact

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.

@vardumper
Copy link
Copy Markdown
Author

vardumper commented Feb 7, 2026

actually not really a code change - just a package.json fix based upon v5.0.5 tag ref.
my buest guess is you generate the tags, and probably all skeletons are affected.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants