microsoft / microsoft/beachball
Support separate bump and publish steps (without bumping again)
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 815
- Forks
- 93
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 12
Description
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
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the separate beachball change, bump, and publish --no-bump --scope commands from the issue and trace their release entry points. The change is done when packages can be bumped without publishing, then selected packages can be published without another version bump, with the existing scope and prerelease options preserved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- ci-cd, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100