Currently when release drafter tags a major / minor release, it is not released to production. Previously it has been agreed that Production should be a manual, human-led process. Hence, documentation / a playbook should be created to document the merging of production and a given version tag.
Generally agreed on Discord (shortly after writing this) that Production should be a manual, human-led process. Ergo, this ticket becomes "Document workflow for publishing to production".
Currently when release drafter tags a major / minor release, it is not released to production. Previously it has been agreed that Production should be a manual, human-led process. Hence, documentation / a playbook should be created to document the merging of production and a given version tag.