CI / dev experience remaining issues about manifold HOT 5 OPEN

auto bump version in the main package.json (currently ocular-publish only bumps versions in modules package.json

lerna bump typically only bumps modules in the workspace. Since example/ and website/ are not in the workspace (and supposedly not), it is not necessary for "bump" to work for them.

from manifold.

lerna bump typically only bumps modules in the workspace. Since example/ and website/ are not in the workspace (and supposedly not), it is not necessary for "bump" to work for them.

But that will create confusion. Imagine someone new will have to go to modules subdirectories to find out what current version is.

from manifold.

Not sure if this is a relevant comment, but I prefer using synchronized versioning of submodules. I.e. all modules get published with the same version even if only some have changed. That version is then in lerna.json in the root.

from manifold.

Not sure if this is a relevant comment, but I prefer using synchronized versioning of submodules. I.e. all modules get published with the same version even if only some have changed. That version is then in lerna.json in the root.

We are already doing that

from manifold.

I changed my mind and I think aligning the versions on website/ and example/ is actually a good idea, because we will have a documentation website later on and the documentation version should align with the module versions, so should be the demo in or referenced by the documentation.

To do so you can make some scripts following the lerna bump to copy over the version number from the modules to the docs/websites.

from manifold.