chi3316 opened a new issue, #8565: URL: https://github.com/apache/rocketmq/issues/8565
### Before Creating the Bug Report - [X] I found a bug, not just asking a question, which should be created in [GitHub Discussions](https://github.com/apache/rocketmq/discussions). - [X] I have searched the [GitHub Issues](https://github.com/apache/rocketmq/issues) and [GitHub Discussions](https://github.com/apache/rocketmq/discussions) of this repository and believe that this is not a duplicate. - [X] I have confirmed that this bug belongs to the current repository, not other repositories of RocketMQ. ### Runtime platform environment Github Action ### RocketMQ version branch : develop ### JDK Version _No response_ ### Describe the Bug The workflow retry mechanism fails to trigger because of recent changes to the repository's action permissions, which now default to read-only. This prevents the GH_TOKEN from having the necessary actions: write permission to trigger the retry mechanism. ### Steps to Reproduce 1. Push a commit to trigger the workflow. 2. Allow the workflow to fail. 3. Observe that the retry mechanism is not triggered. ### What Did You Expect to See? The workflow retry mechanism should trigger after a failure, attempting to rerun the workflow ### What Did You See Instead? The workflow retry mechanism does not trigger because the GH_TOKEN does not have the required actions: write permission.  ### Additional Context _No response_ -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
