question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

version 5.1.3 broken version bump for internal monorepo packages

See original GitHub issue

Current Behavior

When using version 5.1.3 or above more than half of our packages don’t get their version correctly updated. The UI correctly lists all packages and shows the version correctly (which is misleading) but after checking git status we can see that only 8 packages got updated.

Expected Behavior

All versions get updated in multiple package.json files for each of the packages our monorepo has.

Steps to Reproduce

Unfortunately I don’t have a repro to provide you since our project is not open source. But I have confirmed that until 5.1.2 all our package versions get correctly updated, however from 5.1.3 less than half of the packages get updated.

We ran the following command:

npx lerna version --no-git-tag-version --no-push --no-commit-hooks --loglevel debug --exact 6.0.0

I’ve also tried with different parameters etc but no impact.

Issue Analytics

  • State:closed
  • Created a year ago
  • Comments:5

github_iconTop GitHub Comments

1reaction
ghiscodingcommented, Aug 11, 2022

in case that helps, the fix was already applied in Lerna-Lite or you could wait for it to be applied here. Nice to see more confirmation of the issue & fix. Thanks

0reactions
JamesHenrycommented, Aug 12, 2022

Thanks for reporting this @gmcestari let us know if you have any issues with lerna 5.4.1 which includes the fix for this

Read more comments on GitHub >

github_iconTop Results From Across the Web

Fixed Versioning seems broken · Issue #1611 · lerna ... - GitHub
With Fixed versioning, Lerna Version is only bumping the version of packages which had a change in the previous commit.
Read more >
Challenges of major version bumps in a monorepo - HackMD
More often, we've used it to mean that when the suite major bumps, every published package must major bump (even if the major...
Read more >
Guide to version management with changesets
Maintainers need to track merging changes, document how apps should upgrade, update packages within the repository, and publish packages.
Read more >
Lerna NPM | npm.io
One issue with this approach is that a major change in any package will result in all packages having a new major version....
Read more >
GitLab chart versions
Breaking changes are anticipated that may have to be introduced to the chart that would warrant a major version bump, and the requirement...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found