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
Enabling branch protection rules to require signed commits causes the current release process to fail during the release when the version is incremented and the new version is committed to git without a signed commit. Need to re-enable branch protections and update the release process to work with those protections enabled. see: .circleci/ci-publish.sh
Investigate semantic-release tools that leverage GH_TOKEN, etc
The text was updated successfully, but these errors were encountered:
Enabling branch protection rules to require signed commits causes the current release process to fail during the release when the version is incremented and the new version is committed to git without a signed commit. Need to re-enable branch protections and update the release process to work with those protections enabled. see: .circleci/ci-publish.sh
Investigate semantic-release tools that leverage GH_TOKEN, etc
The text was updated successfully, but these errors were encountered: