CI - Applied ruleset for master branch blocks release process

[YOU54F]

See https://github.com/pact-foundation/pact_broker/actions/runs/13307341292/job/37161272200

logs

Calculating increment since last release...
  Performing minor release
  2.[11](https://github.com/pact-foundation/pact_broker/actions/runs/13307341292/job/37161272200#step:4:12)3.0
  Generating RELEASE_NOTES.md
  Updating CHANGELOG.md
  [master 4bb820b6] chore(release): version 2.1[13](https://github.com/pact-foundation/pact_broker/actions/runs/13307341292/job/37161272200#step:4:14).0
   2 files changed, 13 insertions(+), 1 deletion(-)
  Releasing gem to Rubygems
  pact_broker 2.113.0 built to pkg/pact_broker-2.113.0.gem.
  Tagged v2.113.0.
  Untagging v2.113.0 due to error.
  rake aborted!
  Running `git push origin refs/heads/master` failed with the following output:
  
  remote: error: GH013: Repository rule violations found for refs/heads/master.        
  remote: Review all repository rules at https://github.com/pact-foundation/pact_broker/rules?ref=refs%2Fheads%2Fmaster        
  remote: 
  remote: - Changes must be made through a pull request.        
  remote: 
  remote: - Required status check "Test completion check" is expected.        
  remote: 
  To https://github.com/pact-foundation/pact_broker
   ! [remote rejected]   master -> master (push declined due to repository rule violations)
  error: failed to push some refs to 'https://github.com/pact-foundation/pact_broker'

will disable for now to allow release to proceed.

edit: disabled temporarily for release and then re-instated. Would be nice for manually triggered releases to use pact-dev automation user, and that user be setup with an exemption role :)

cc: @JP-Ellis

[JP-Ellis]

Hmm, should it be pushing directly to master? Would it not be better if it created a PR to merge into master to ensure there's a review?

In any case, it should be possible to allow CI to bypass the branch protection rules. Do you know which account is being used?

[YOU54F]

i dont think it needs a review, it is simply pushing the changelog and version bump after a release along with the tag

[JP-Ellis]

Do you know which account is being used to push to master? The rules can be configured to exempt this specific user.

[YOU54F]

sorry, mega late reply, whichever user kicks off the release either via script locally and rest api call, or manually triggering of the release workflow.