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
In the monorepo project I'm working on, We want to publish our packages in the ci/cd pipeline. I have some packages that should be bumped but not published.
Right now I was thinking on implementing it by bumping the files locally and then publishing the bumped packages with a --scope flag to only publish certain packages to the registry.
As of now I don't see a way to do this without publish bumping the versions again. Am I missing something? A flag or config setting? Adding --no-bump has no effect to the version number.
I'm wondering the same thing. I want to be able to bump packages, then run some other CI steps, and then publish. Even with --no-bump I end up with a double version bump.
I'm assuming that the correct way to do this is to utilise the prepublish hook, but the process as described above should be far simpler
In the monorepo project I'm working on, We want to publish our packages in the ci/cd pipeline. I have some packages that should be bumped but not published.
Right now I was thinking on implementing it by bumping the files locally and then publishing the bumped packages with a --scope flag to only publish certain packages to the registry.
As of now I don't see a way to do this without publish bumping the versions again. Am I missing something? A flag or config setting? Adding --no-bump has no effect to the version number.
As an example here are the commands I run:
npx beachball change --all --type prerelease --no-commit --message 'Prepare packages for update'
npx beachball bump --prereleasePrefix next --keepChangeFiles
npx beachball publish --tag next --no-push --no-bump --scope CORRECT_SCOPE_HERE
The text was updated successfully, but these errors were encountered: