beachball
beachball copied to clipboard
microsoft
The Sunniest Semantic Version Bumper
# Challenges The current bumping flow of the Beachball introduces a few challenges: - Potential inconsistency between versions on the master, and artifacts published to NPM. - Code reverts require...
If you run `beachball publish` from a location other than the root of the git repo, beachball fails to find the change files and reports `Invalid change file change/foo`. The...
When beachball change commits change files, those files should be subject to the same pre-commit logic as regular changes in a repo.
Handle partial publishes: minispec: - add a "sync" command that can synchronize a partially updated git repo with the current versions of the published npm packages. - ~delete change files...
Currently we have user email for each change:  We should change to @githubUsername (e.g. @xugao) Instead of email: https://github.com/microsoft/beachball/blob/01f3bae061bdd91a1e2971fd81a82dc22779bf9e/packages/beachball/src/changefile/promptForChange.ts#L85
When a missing package is detected from registry, beachball should default to publishing the new package.
change and check do not operate correctly when the branch is in an unmergeable state. we need to give warning about this.
When a package is marked private, we skip the publish and the change file deletion step but we still incorrectly bump all the versions of dependent packages. This leads to...
From feedback we can do better with the dependent package changes. ## 1. prompt for dependent bump change type At the time of calling `beachball change`, we should prompt user...
quick design: add a `beachball.config.js` or package.json npm script to call a "postSuccessfulPublish" script