microsoft / microsoft/beachball
Allow overriding dependentChangeType for a package
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 815
- Forks
- 93
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 12
Description
Motivation: Fluent UI has a custom eslint plugin which is published, and all the packages in our monorepo have it as a dev dependency. However, since it's just a dev dependency, bumping the plugin version should NOT cause the other packages to bump.
Right now we're trying to catch this in PRs and manually override dependentChangeType to none in the change file, but it would be nice if you could do this in that package's beachball settings (in package.json) to force it to always use none:
"beachball": {
"dependentChangeType": "none"
}
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 locating how beachball reads the package.json beachball settings and how dependentChangeType is applied. Add support for configuring dependentChangeType as none in a package's settings, then verify that dev-dependency version bumps do not cause dependent package bumps.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- release
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100