We're getting more and more contributions and are now more at risk from a new problem:

• making a release that has unreleased / unbumped version changes in it.

So it’s kind of hard to explain but the risk here is that:

• I just merged something on main that updates package X & has a changeset for it
• Someone ran yarn release prior to me merging those changes on main
  • package X did not have any changeset for it.
  • Its version did not change.
• Someone opened the version bump PR. It was accepted.
• Someone merges the version bump PR on main
  • main now has my new changes (no version bump)
  • main has new version in all the package.json of all the repos except for X
• Someone runs the GitHub workflow to push stuff to npm
• We run yarn build && yarn publish from main in CI
• Package Y breaks in prod because it points to package X at its old version

TL;DR Right now folks need to rebase & rerun yarn release every time someone merges to main.

The GitHub workflow would eliminate this possibility.