Replies: 3 comments 2 replies
-
I notice the same issue. Regression?
|
Beta Was this translation helpful? Give feedback.
-
@emewjin Please always try to share a repro case in a runnable form - providing a git repository to clone should be OK. OSS maintainers usually can't afford the time to set up the repro, even if exact steps are given. I can't possibly know what might be wrong in your case without the ability to inspect a sample repo. @unional your situation is related to using changesets/packages/assemble-release-plan/src/determine-dependents.ts Lines 193 to 197 in 1d3f9f2 I actually have a pending fix for this in a form of a draft PR: I plan to get back to this draft soon - the only thing that I need there is writing tests for fixed cases. |
Beta Was this translation helpful? Give feedback.
-
@Andarist I noticed that this situation was exact work by check this documentation. This was not a bug 🙏🏻 |
Beta Was this translation helpful? Give feedback.
-
Hi, I got problem that minor change of peer & dev dependency causes major change.
I already see similar issue and try to add experimental config like below, but it still in trouble.
Unfortunately the repo is private because of owner's decision, so I please ask for your understanding about just describe problem by text.
There is package A and B.
A depends on B (peer&dev).
If I make minor change on B, A got major changes.
Here is screenshot that changeset bot made.
This is minor change on B.
This is major change on A.
Why minor change of peer dependency causes major change even if I set
onlyUpdatePeerDependentsWhenOutOfRange
true?Did I something wrong in config?
Beta Was this translation helpful? Give feedback.
All reactions