A way to get versions of packages we are about to publish ?
See original GitHub issueHello
When we publish packages the log output contains something like this
Found 3 packages to publish:
- @super-app/core => 1.5.1-alpha.180+4799bdd496
- @super-app/utils => 1.6.1-alpha.180+4799bdd496
- @super-app/ui => 1.2.1-alpha.180+4799bdd496
Are you sure you want to publish these packages ?
So the question is, does Lerna provide a way to get the same output without intention to publish packages. For example if we need artifacts (versions) for CI pipeline
Thank you
Issue Analytics
- State:
- Created 3 years ago
- Comments:5
Top Results From Across the Web
How to Publish an Updated Version of an npm Package
The easiest way to update your version number is to use the handy npm version command. This will automatically update the version number...
Read more >7. Releasing and versioning - Python Packages
Releasing versions is also an important way of communicating to your users that your package has changed (e.g., bugs have been fixed, new...
Read more >Version and Publish - Lerna
Version and Publish. Lerna can increment your package's versions as well as publish your packages to NPM, and it provides a variety of...
Read more >How to Publish an Open-Source Python Package to PyPI
However, to unlock the full potential of the language, you should also take advantage of the community contributions at PyPI: the Python ...
Read more >7. Releasing your package
7.3. Uploading your package to the Python Package Index ( PyPI )¶ ·. · is a clone of · and you can therefore...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@azakaWow No problem. I realize now the downside of that command is that the project needs to have something changed for it to work.
Edit: Actually you can do
lerna publish --force-publish
to get it to show regardless.echo -en 'n\n' | lerna publish --force-publish | grep '@super-app/core' | rev | cut -d ' ' -f1 | rev
I couldn’t find any option to do this, but with some piping you might be able to get somewhere:
i.e.
echo -en 'n\n' | lerna version | grep '@super-app/core' | rev | cut -d ' ' -f1 | rev