How to ignore changed files when publishing with Lerna

Before tagging a new version, lerna scans your codebase for changed files. If it finds a changed file, it’ll recommend a new version. This is really useful most of the time, but you only want to bump to a new version when some library functionality changes. You certainly don’t want to introduce a new version just because you changed the README.md file.

There are two ways that you can tell lerna to ignore specific changed files.

The — ignore-changes flag

--

--

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store