Automated release is broken by branch protection #1029
Description
I don't have permissions to update this, and it's fine if we want to make releasing happen by creating a tag on GH and running GH Actions or something, but as it stands, it's literally impossible to run the configured release-it workflow correctly. The behavior at this point is: it will publish to npm but fail when attempting to push the commit on master to GitHub. 😑
A possible workaround between now and whenever the branch config is fixed/a GH Actions-based flow is set up: do the release on a release branch and push that, and then merge the PR with it.