foster/denoland-deno
1
0
Fork 0
mirror of https://github.com/denoland/deno.git synced 2025-01-11 16:42:21 -05:00
Code Issues Packages 1 Wiki Activity

chore: update release doc template (#26406)

Browse source
This commit is contained in:
Bartek Iwańczuk 2024-10-19 04:42:19 +01:00
parent 11b3bccf30
commit fc098332fa
No known key found for this signature in database
GPG key ID: 0C6BCDDC3B3AD750
1 changed files with 5 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

9
tools/release/release_doc_template.md
View file

@ -30,7 +30,7 @@ Release checklist: <LINK TO THIS FORKED GIST GOES HERE>
## Patch release preparation ## Patch release preparation
**If you are cutting a patch release**: First you need to sync commits to the ⛔ **If you are cutting a patch release**: First you need to sync commits to the
`v$MINOR_VERSION` branch in the `deno` repo. `v$MINOR_VERSION` branch in the `deno` repo.
To do that, you need to cherry-pick commits from the main branch to the To do that, you need to cherry-pick commits from the main branch to the
@ -75,13 +75,13 @@ verify on GitHub that everything looks correct.
1. Click on the "Run workflow" button. 1. Click on the "Run workflow" button.
1. In the drop down, select the minor branch (`v$MINOR_VERSION`) if doing a 1. In the drop down, select the minor branch (`v$MINOR_VERSION`) if doing a
patch release or the main branch if doing a minor release. patch release or the main branch if doing a minor release.
1. For the kind of release, select either "patch", "minor", or "major". 1. For the kind of release, select either `patch` or `minor`.
1. Run the workflow. 1. Run the workflow.
- [ ] Wait for the workflow to complete and for a pull request to be - [ ] Wait for the workflow to complete and for a pull request to be
automatically opened. Review the pull request, make any necessary changes, automatically opened. Review the pull request, make any necessary changes,
and merge it. and merge it.
- ⛔ DO NOT create a release tag manually That will automatically happen. - ⛔ **DO NOT** create a release tag manually That will automatically happen.
<details> <details>
<summary>Failure Steps</summary> <summary>Failure Steps</summary>
@ -120,7 +120,8 @@ verify on GitHub that everything looks correct.
(https://github.com/denoland/deno/releases). (https://github.com/denoland/deno/releases).
- ⛔ Verify that: - ⛔ Verify that:
- [ ] There are 14 assets on the release draft. - [ ] There are 24 assets on the
[GitHub release draft](https://github.com/denoland/deno/releases/v$VERSION).
- [ ] There are 10 zip files for this version on - [ ] There are 10 zip files for this version on
[dl.deno.land](https://console.cloud.google.com/storage/browser/dl.deno.land/release/v$VERSION). [dl.deno.land](https://console.cloud.google.com/storage/browser/dl.deno.land/release/v$VERSION).