[COMPASS-5394] Update peerDeps version during the packages-version command Created: 07/Jan/22 Updated: 27/Oct/23 Resolved: 02/Sep/22 |
|
| Status: | Closed |
| Project: | Compass |
| Component/s: | Packaging |
| Affects Version/s: | None |
| Fix Version/s: | No version |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Sergey Petushkov | Assignee: | Unassigned |
| Resolution: | Gone away | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Documentation Changes: | Not Needed | ||||||||
| Description |
|
Lerna does not support auto-upating peerDependencies during the publish and even though misaligned peerDependencies versions for monorepo packages don't cause issues for ci / install / bootstrap, it can cause issues when adding / removing packages from the workspace. We should mitigate that by 1) making sure all monorepo packages that are mentioned in peerDependencies have the same version specified there as a package (so no *) 2) making sure that our packages-version script handles updating peerDependencies version also |
| Comments |
| Comment by Maurizio Casimirri [ 02/Sep/22 ] |
|
already done with the automated bump of packages |