[Release|CI/CD] adjust release pipelines (#6366)
This PR contains adjustments to the release pipelines. - RC Automation and Branchoff pipelines now use the PGPKMS key generated by the release team to sign related commits directly in the Github flow - RC Automation does not use old tagging action. Instead, it creates a tag and pushes it using git - RC binary is going to be done on the larger github runners setup in the` paritytech-release` org Closes: https://github.com/paritytech/release-engineering/issues/233
Showing
- .github/scripts/common/lib.sh 2 additions, 1 deletion.github/scripts/common/lib.sh
- .github/workflows/release-10_rc-automation.yml 40 additions, 7 deletions.github/workflows/release-10_rc-automation.yml
- .github/workflows/release-branchoff-stable.yml 15 additions, 9 deletions.github/workflows/release-branchoff-stable.yml
- .github/workflows/release-build-rc.yml 8 additions, 0 deletions.github/workflows/release-build-rc.yml
- .github/workflows/release-reusable-rc-buid.yml 1 addition, 1 deletion.github/workflows/release-reusable-rc-buid.yml
Please register or sign in to comment