-
Notifications
You must be signed in to change notification settings - Fork 38
Description
Our release broke after the second run on 6.0.X, and we tracked the cause down to dependencies not being bumped as expected.
With 6.0.X:
package A (no dependencies)
package B (depends on A)
make change in A
run release script
A gets a new release
B gets no new release, does not get a bumped dependency on A UNEXPECTED BEHAVIOUR
With 5.0.X (and earlier versions):
package A (no dependencies)
package B (depends on A)
make change in A
run release script
A gets a new release
B gets a new release (bumped dep A) EXPECTED BEHAVIOUR
The same issue applies even if we make changes to both package A and B, when on 6.0.X. B will not get a bumped dependency on A.
Is this expected behaviour? I'm not sure how to interpret the drop support for cycled monorepos line from the release notes.