don't remove Standard-Change label on failed releases (#11126)

CHANGELOG_BEGIN
CHANGELOG_END
This commit is contained in:
Gary Verhaegen 2021-10-06 12:12:11 +02:00 committed by GitHub
parent 261d4db656
commit 4cb521b406
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -306,6 +306,9 @@ patches we backport to the 1.0 release branch).
1. If the release is bad, delete the release from the [releases page]. Mention
why it is bad as a comment on your PR, and **stop the process here**.
Note that **the Standard-Change label must remain on the PR**, even if the
release has failed.
1. Announce the release on the relevant internal Slack channels (`#product-daml`,
`#team-daml`). For a stable release, direct people to the release blog post;
for a prerelease, you can include the raw output of the `unreleased.sh`