v2.0.0

2.0.0

Release Manager Actions v2 is a release support workflow based on the develop-stable branches system.
It is incompatible with v1.

Migration

Migration is deprecated because it is so different from v1, but if it is necessary, do the following:

1. Create a stable branch and register its name as a STABLE_BRANCH variable.
2. Since ruleset management is no longer needed, remove RULESET_EDIT_APP_PRIVATE_KEY, RULESET_ID_WITHIN_RELEASE, and RULESET_ID_OUT_OF_RELEASE. Also, the rulesets used in v1 should be deleted.
3. Grant Repository - Pull request - Read and Write permission to the GitHub App for on: release. If you don't have it, please create it.
   In the Install App tab, select org or user right ⚙️ and go to the App installation management screen, where you will see (app) is requesting an update to its permissions. [Review Request]. Select Review Request and on the next screen select Accept new permissions.
4. Create a ruleset to protect the stable branch according to README.md.
5. Override the three release manager workflows.
   Set line 6 of release-edit-with-push.yml to the name of the develop branch (the default branch in your repository).

Screenshots to grant permission to the app