Path to immutable releases
#2359 was fixed in #2416 which carves a path towards achieving a fully immutable release process in Turtles (Phase 1 of a gradual migration):
Phase 1: Draft-first flow, manual undraft. Gives us confidence that the suggested process works reliably without the risk of being stuck with a broken immutable release. (✅ completed now). This issue is track Phase 2 and 3 of this gradual migration.
Phase 2 (follow-up, once Phase 1 is validated over a few releases): Uncomment the Publish release step already included in the workflow. This automates the undraft as the very last step, only after all assets are confirmed present, fully following GitHub's recommended immutable release workflow
Phase 3 (no code change needed, a follow-up once Phase 2 is validated): Enable immutable releases in the
repository settings under Settings -> Releases -> "Enable release immutability".
We can start tackling this issue after few release using the current worklow (Phase 1 state) and once we sure and confident we won't have any surprises and failures, this can be picked up and completed.
Path to immutable releases
#2359 was fixed in #2416 which carves a path towards achieving a fully immutable release process in Turtles (Phase 1 of a gradual migration):
Phase 1: Draft-first flow, manual undraft. Gives us confidence that the suggested process works reliably without the risk of being stuck with a broken immutable release. (✅ completed now). This issue is track Phase 2 and 3 of this gradual migration.
Phase 2 (follow-up, once Phase 1 is validated over a few releases): Uncomment the Publish release step already included in the workflow. This automates the undraft as the very last step, only after all assets are confirmed present, fully following GitHub's recommended immutable release workflow
Phase 3 (no code change needed, a follow-up once Phase 2 is validated): Enable immutable releases in the
repository settings under Settings -> Releases -> "Enable release immutability".
We can start tackling this issue after few release using the current worklow (Phase 1 state) and once we sure and confident we won't have any surprises and failures, this can be picked up and completed.