Replies: 2 comments
-
With default settings, the versions are bumped if dependency ranges stop being satisfied, see the options here. And this is graph-based - so if pkg A depends on pkg B and pkg B gets a new major version then we compute that we also have to create a patch bump for A, this can happen recursively, etc.
On the other hand, |
Beta Was this translation helpful? Give feedback.
-
So if I understand correctly, by making my config file like this {
"$schema": "https://unpkg.com/@changesets/config@2.3.0/schema.json",
"changelog": "@changesets/cli/changelog",
"commit": false,
"fixed": [],
"linked": [],
"access": "restricted",
"baseBranch": "main",
"updateInternalDependencies": "patch",
"___experimentalUnsafeOptions_WILL_CHANGE_IN_PATCH": {
"updateInternalDependendents": "always"
},
"ignore": []
} should fit my needs, but maybe I miss something, when i make an update on my Here is a repo to demonstrate, everything is not really clear to me 🥲 |
Beta Was this translation helpful? Give feedback.
-
Hello there ! 😃
I am currently doing research, planning to migrate my multiple replicated projects under a monorepo (with Turborepo).
My file tree will looks like this:
My needs are the following:
ui
, both projects ABC depends on it, so they should have their version bumped too.project-A
, only this one should have his version bumped. not the 2 others projects, nor theui
package.This is where I think is the limit with changesets ? What I would like to write in the config would be:
But I got an error from the CLI when doing so
Is this something possible with changesets, or should I look for another solution ?
Thanks in advance 🙏
Beta Was this translation helpful? Give feedback.
All reactions