if i made a release with the command fullrelease of the zest.releaser package the i got in the last step the following Info message from github.
I think the security changes in the collective namespace are the reason. it's only an info, but is there a way with zest.releaser not break the configured rules?
remote: Bypassed rule violations for refs/heads/main:
remote:
remote: - Changes must be made through a pull request.
remote:
remote: - 3 of 3 required status checks are expected.
remote:
To github.com:collective/collective.outputfilters.tinymceaccordion.git
1842564..9859ae9 main -> main
INFO remote: Bypassed rule violations for refs/heads/main:
remote:
remote: - Changes must be made through a pull request.
remote:
remote: - 3 of 3 required status checks are expected.
remote:
To github.com:collective/collective.outputfilters.tinymceaccordion.git
1842564..9859ae9 main -> main
To github.com:collective/collective.outputfilters.tinymceaccordion.git
* [new tag] 2.0.1 -> 2.0.1
INFO To github.com:collective/collective.outputfilters.tinymceaccordion.git
* [new tag] 2.0.1 -> 2.0.1
INFO Finished full release.
INFO Reminder: tag checkout is in /tmp/collective.outputfilters.tinymceaccordion-2.0.1-fwr2zbpy/gitclone