Call release-final from release-prepare workflows

[angusbayley]

Ticket here

This changes the release workflows such that we now explicitly call release-final from release-prepare workflows, passing a ref input as we do so. The automatic follow-on workflow_run trigger is removed in this PR, meaning that inputs.ref is now guaranteed to be available in the workflow (passing inputs is not possible with the workflow_run trigger). This solves the issue seen in the above ticket.

A side-effect of this approach is we won't be able to see these follow-on runs of release-final in the workflow history for release-final, seen as the workflow was called by release-prepare or release-prepare-hotfix. Runtime/failures/successes will be attributed to the release-prepare or release-prepare-hotfix workflow, making it a little harder to monitor/audit the runs IMO.

(An alternative fix to this problem is #8713, however I'm closing that PR and going with this PR's approach instead because the workflow_run trigger is so limited [can't specify branch, can't pass inputs]).

Testing

Test PR here:

• run release-prepare
• ensure release-final is called
• ensure it echos out the correct value for inputs.ref and the checkout step proceeds smoothly
• repeat for release-prepare-hotfix instead of release-prepare

🟢 Passing - see this comment

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

4 Skipped Deployments

Name	Status	Preview	Comments	Updated (UTC)
ledger-live-github-bot	⬜️ Ignored (Inspect)			Dec 17, 2024 1:24pm
native-ui-storybook	⬜️ Ignored (Inspect)			Dec 17, 2024 1:24pm
react-ui-storybook	⬜️ Ignored (Inspect)			Dec 17, 2024 1:24pm
web-tools	⬜️ Ignored (Inspect)			Dec 17, 2024 1:24pm