jdaugherty opened a new pull request, #16417:
URL: https://github.com/apache/grails-core/pull/16417
The Forge AWS deploy workflow (`forge-deploy-aws.yml`) checks out and builds
the ref selected in **Use workflow from**, so the deployed Forge version is
whatever version is on that ref.
The release instructions said to dispatch from the maintenance branch and
never from a historical tag. Once a release closes, though, the maintenance
branch has already moved to the next `-SNAPSHOT` version, so following those
instructions deploys the wrong version.
Changes:
- `release.yml`: the `🚀 MANUAL - Deploy Grails Forge` reminder now says to
use the release tag (`${TAG}`) and lists the release slots.
- `RELEASE.md`: release slots use the release tag and snapshot slots use the
maintenance branch. The slot table now shows example refs. The local packaging
fallback is kept only for tags that predate the workflow (`v7.0.16`, `v7.1.6`,
`v7.2.3`, `v8.0.0-M6` and earlier). `v7.0.17`, `v7.1.7`, `v7.2.4`, and
`v8.0.0-RC1` all contain the workflow.
- `forge-deploy-aws.yml`: the header comment matches the new wording. No
behavior change.
--
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]
