Elizabeth Craig
Elizabeth Craig
With the `groupChanges` option in a monorepo, beachball will currently create a new file each time you run `yarn change` (with additional changed packages) even if a multi-package change file...
@ling1726 pointed out in https://github.com/microsoft/beachball/pull/606#issuecomment-937760446 that grouped change files won't work well if there's a `--scope` specified when publishing (as we do now in fluentui) and the There's not a...
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...
Previously when running `beachball change`, it would fetch changes from the remote (and do a bunch of expensive git/filesystem operations) during both `validate` and `promptForChange`. This PR adds caching of...
The `change` command runs `git fetch` at least twice. Example from the beachball repo: ``` $ yarn change yarn run v1.22.10 $ node ./lib/cli.js change Checking for changes against "origin/master"...
Sometimes it's helpful to be able to see exactly what publish is going to do without actually publishing anything. Today beachball doesn't have an option which completely handles this.
Sometimes it would be useful to be able to specify multiple packages for the `--package` option. (Real example: force publishing a new patch of several packages after fixing a shared...
We discovered in Fluent UI that the `sync` command was not respecting per-package `tag` options. Fix is in the helper function which fetches the versions, each package info's `combinedOptions` already...
### Background We'd like to migrate from enzyme to [testing-library](https://testing-library.com/docs/) since enzyme is effectively unmaintained (over a year and no official React 17 adapter) and testing-library provides a better, more...
The publish flow for beachball is currently as follows: 1. bump packages locally 2. publish to npm 3. push to git Currently when publishing packages, if the git auth is...