Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Filing this as draft but I would like to make this switch at some point in the near future. We opted for independent versioning at the start so importing existing packages would be easier. In the long term, in my opinion, independent versioning does not work very well with conventional commits. One issue is that when adding new packages at 0.x they never get automatically bumbed to 1.x with conventional commits - they should be bumped manually, but who can determine when te correct time is 🤷 . For example, look at the versions of our core/web packages :)
Additionally, fixed versioning should work better with communicating what versions of different packages work together. Right now, we have some cases in docs where we need to specify "needs fractal X and mandelbrot Y" (for example, the root collections option), because the packages are bumped independently. With fixed versioning, we could always say that "use version X of both or latest".
Notes on merging/releasing this:
v1.2.3
. That should inform lerna/conventional commits that that's the correct release to bump from.