foster/denoland-deno
1
0
Fork 0
mirror of https://github.com/denoland/deno.git synced 2024-11-28 16:20:57 -05:00
Code Issues Packages 1 Wiki Activity

docs(release): update to include deno_docker release workflow (#18323)

Browse source
This commit is contained in:
David Sherret 2023-03-21 11:38:59 -04:00 committed by GitHub
parent 7cf6e2a7a6
commit 0366d6833f
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 6 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

12
tools/release/release_doc_template.md
View file

@ -20,7 +20,7 @@ cut.**
## Patch release preparation
**If you are cutting a patch release**: First you need to sync commit to the
**If you are cutting a patch release**: First you need to sync commits to the
relevant minor branch in the `deno` repo, so if you are cutting a `v1.17.3`
release you need to sync `v1.17` branch.
@ -85,8 +85,8 @@ verify on GitHub that everything looks correct.
repo's actions:
https://github.com/denoland/deno/actions/workflows/version_bump.yml
1. Click on the "Run workflow" button.
1. In the drop down, select the minor branch if doing a patch release or the
main branch if doing a minor release.
1. In the drop down, select the minor branch (ex. `vx.xx`) if doing a patch
release or the main branch if doing a minor release.
1. For the kind of release, select either "patch", "minor", or "major".
1. Run the workflow.
@ -194,9 +194,9 @@ script generates the symbols based on the latest tags.
## Updating `deno_docker`
- [ ] Open a PR on the `deno_docker` repo that bumps the Deno version in all
Dockerfiles, the README and the example Dockerfile. Get it reviewed and
merge it.
- [ ] Run the version bump workflow:
https://github.com/denoland/deno_docker/actions/workflows/version_bump.yml
- [ ] This will open a PR. Review and merge it.
- [ ] Create a tag with the version number (_without_ `v` prefix).
## All done!