microsoft / microsoft/beachball
Undefined behavior when dep range checked in is out of sync
Open
Nobody has claimed this yet.
bug
- Dominant language
- TypeScript
- Stars
- 815
- Forks
- 93
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 12
Description
These are repro cases:
- the first commit where a new dep is introduced + that dep being bumped while publishing
- a package version are out of sync as checked in & a dep change bump happened on that out-of-sync package
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. Start by reproducing the two dependency-range and publishing cases described in the issue, then trace the range-checking and version-bump flow. The expected behavior for both out-of-sync scenarios must be established before the work can be considered done.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- release
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100