You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Following the instructions as written only works if the releaser bypasses branch protections. They must be an admin or an admin must add them to the list of people allowed to bypass. I added @nikki-t to the bypass list, then cleaned up the list after she successfully pushed. IMO, We should instead document a release process that uses a branch and a PR to make the required changes.
Additionally, the uv-lock pre-commit job will fail on every release because it will try and resolve the new version into the environment lock file before it's been pushed to PyPI.
The text was updated successfully, but these errors were encountered:
protected branch hook declined
...
Changes must be made through a Pull Request
Following the instructions as written only works if the releaser bypasses branch protections. They must be an admin or an admin must add them to the list of people allowed to bypass. I added @nikki-t to the bypass list, then cleaned up the list after she successfully pushed. IMO, We should instead document a release process that uses a branch and a PR to make the required changes.
Additionally, the
uv-lock
pre-commit job will fail on every release because it will try and resolve the new version into the environment lock file before it's been pushed to PyPI.The text was updated successfully, but these errors were encountered: