microsoft / microsoft/beachball
Beachball tries bumping package to version that already exist despite no changes
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 815
- Forks
- 93
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 12
Description
Our publishing pipeline occasionally fails when beachball tries bumping a package to a version that already exists despite no changes in that package. We're not sure why this happens but it seems occur with newer packages that were recently added to the repo. In order to fix the pipeline, we've been making small changes in the package that beachball tried bumping in order to trigger a version bump in that package. This unblocks us for a bit but the issue continues to pop up.
We saw this issue and are wondering if it could be related to this problem?
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 comparing this behavior with the linked issue #281 and trace the publishing pipeline's version-bumping logic for recently added packages. The issue is resolved when unchanged packages no longer receive an already-existing version and the pipeline completes without requiring artificial package changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- ci-cd, release
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 32/100