Use "*" instead of exact version number for internal dependencies

[trivikr]

Is your feature request related to a problem? Please describe.

Rebasing takes time as we need to manually resolve package version number before merge.
If there is a mistake while rebasing, the CI fails on main branch. Example: #2697

Describe the solution you'd like

Use "*" instead of specifying exact version number for internal dependencies.

[trivikr]

The "*" mentioned in the dependencies is changed to the exact version number when lerna version is run. Verified in commit: trivikr/test-lerna-monorepo-publish@2b60543

Command run:

$ ./node_modules/.bin/lerna version --exact --conventional-commits --no-push --no-git-tag-version --no-commit-hooks --yes

We can use "*", given that we create another commit to replace version numbers for internal dependencies back to "*" after the release commit.

[trivikr]

AWS CDK uses 0.0.0 as version marker, added in aws/aws-cdk#6463

[trivikr]

The "*" mentioned in the dependencies is changed to the exact version number when lerna version is run.

Open question in lerna lerna/lerna#3063

[trivikr]

AWS CDK uses custom script for managing versions
https://github.com/aws/aws-cdk/blob/master/scripts/align-version.js

[trivikr]

Decision: we'll continue to use lerna version command for creating release commit, and update internal release scripts as follows:

• Push changes made by running version command in tag branch.
• Undo version numbers in deps/devDeps/peerDeps back to * and push it to main branch.
• Npm publish from tag branch.

[github-actions]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread.