You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
except that in our monorepo, all of our interworkspace dependencies use range dependencies, which, when published to npm, remain and resolve incorrectly.
I'd like for yarn version apply to take a flag to remove the range dependency.
For example, one of our packages
"@react-stately/layout": "^3.0.0-nightly-fb28ab3b4-241024" actually resolves to 3.13.9
Describe the drawbacks of your solution
there shouldn't be any drawbacks
Describe alternatives you've considered
When we switch to the workspace protocol, it'd be simple enough to strip the range through sed or an equivalent.
We could also write a plugin, however, most of the logic already exists in version, so it seems silly to copy all of that for this, when it would probably be used by others. This is the same versioning scheme that other libraries use.
The text was updated successfully, but these errors were encountered:
## What's the problem this PR addresses?
<!-- Describe the rationale of your PR. -->
<!-- Link all issues that it closes. (Closes/Resolves #xxxx.) -->
Closes: #6583
## How did you fix it?
<!-- A detailed description of your implementation. -->
When applying versions, I removed the range character.
## Checklist
<!--- Don't worry if you miss something, chores are automatically
tested. -->
<!--- This checklist exists to help you remember doing the chores when
you submit a PR. -->
<!--- Put an `x` in all the boxes that apply. -->
- [x] I have read the [Contributing
Guide](https://yarnpkg.com/advanced/contributing).
<!-- See
https://yarnpkg.com/advanced/contributing#preparing-your-pr-to-be-released
for more details. -->
<!-- Check with `yarn version check` and fix with `yarn version check
-i` -->
- [x] I have set the packages that need to be released for my changes to
be effective.
<!-- The "Testing chores" workflow validates that your PR follows our
guidelines. -->
<!-- If it doesn't pass, click on it to see details as to what your PR
might be missing. -->
- [x] I will check that all automated PR checks pass before the PR gets
reviewed.
---------
Co-authored-by: Maël Nison <[email protected]>
Describe the user story
As a developer, I often want to do publish all of my packages daily, but I need to coordinate (pin) all the versions of my packages.
Describe the solution you'd like
I'd like to be able to use
yarn version
to apply my changes, which I've set up like soexcept that in our monorepo, all of our interworkspace dependencies use range dependencies, which, when published to npm, remain and resolve incorrectly.
I'd like for
yarn version apply
to take a flag to remove the range dependency.For example, one of our packages
Describe the drawbacks of your solution
there shouldn't be any drawbacks
Describe alternatives you've considered
When we switch to the workspace protocol, it'd be simple enough to strip the range through
sed
or an equivalent.We could also write a plugin, however, most of the logic already exists in
version
, so it seems silly to copy all of that for this, when it would probably be used by others. This is the same versioning scheme that other libraries use.The text was updated successfully, but these errors were encountered: