Add a release workflow

[zanieb]

Uses a release workflow with environment protection for publishing releases instead of relying on user invocation.

The release environment can then be protected, e.g., requiring approval from another team member. We can add a tag ruleset to prevent tags from being created outside of the release environment.

I've never used Release drafter, but the workflow here differs from our other projects in that the release process just marks the draft release as final and adds the tag. The draft release is required, for simplicity.

[eifinger]

Looks good and the benefits you describe sound like reason enough to move away from the manual releases.

To clarify I understood this correctly:

1. Release Drafter continues to creates the draft with all the PRs linked and categorized by label
2. I add the manually created release text
3. I start this workflow to change the release from draft to released and create the tag

[zanieb]

Sounds correct to me!

[zanieb]

The only addendum would be 4. Poke the Astral team for a release workflow approval