microsoft / microsoft/beachball
Beachball Should Handle Monrepo Packages Atomically
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 815
- Forks
- 93
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 12
Description
In the case where Beachball is publishing multiple packages to npm, it's possible to publish a package to npm but not push changes to Git because another package fails to be published. Trying to publish again will cause errors because we try to bump to something already in the registry. This requires manually bumping in the repo to fix.
Beachball should try to handle packages more atomically to prevent one failing to publish from leading to a bad repo state.
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
No files, tests, or entry points are named. Trace the npm publishing and Git push flow to understand how multiple packages are processed, then verify that a failed package cannot leave the repository and registry in an unrecoverable state.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, typescript
- Domain
- release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100