You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is a number of private packages (private set to false in package.json) that get version bumps when publishing new changes with Lerna to npm. They also get CHANGELOG files updated. It creates some friction with the packages maintained by the mobile team that uses its own process and doesn't have immediate plans to publish them to npm.
Proposed solution
We should prevent updates to the version field in package.json and CHANGELOG.md files for WordPress packages that are marked as private.
I found something promising - flag that skips private packages when bumping versions. The challenge is that we use lerna publish that uses lerna version internally. I'm sure we can find a way to make it work if that flag is working as I assumed 😃
The text was updated successfully, but these errors were encountered:
gziolo
changed the title
npm Packages: Improvements to the publishing process
npm Packages: Improvements to the publishing process for private packages
Jan 11, 2021
Description
There is a number of private packages (
private
set tofalse
inpackage.json
) that get version bumps when publishing new changes with Lerna to npm. They also get CHANGELOG files updated. It creates some friction with the packages maintained by the mobile team that uses its own process and doesn't have immediate plans to publish them to npm.Proposed solution
We should prevent updates to the version field in
package.json
andCHANGELOG.md
files for WordPress packages that are marked as private.Related comment in #28042 (comment):
https://www.npmjs.com/package/@lerna/version?activeTab=readme#--no-private
I found something promising - flag that skips private packages when bumping versions. The challenge is that we use
lerna publish
that useslerna version
internally. I'm sure we can find a way to make it work if that flag is working as I assumed 😃The text was updated successfully, but these errors were encountered: