foster/deno
0
0
Fork 0
mirror of https://github.com/denoland/deno.git synced 2025-03-03 17:34:47 -05:00
Code Issues Packages 1 Wiki Activity

chore: update cut_a_release.md (#11522)

Browse source
This commit is contained in:
Bartek Iwańczuk 2021-07-27 00:26:39 +02:00 • committed by GitHub
parent c6f4e41529
commit a05bb3924a
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 9 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
tools/cut_a_release.md
View file

@ -8,7 +8,11 @@ cut.**
1. Open a PR on the `deno_std` repo that bumps the version in `version.ts` and 1. Open a PR on the `deno_std` repo that bumps the version in `version.ts` and
updates `Releases.md` updates `Releases.md`
2. Create a tag with the version number (_without_ `v` prefix).
2. Before merging the PR, make sure that all tests pass when run using binary
produced from bumping crates (point 3. from below).
3. Create a tag with the version number (_without_ `v` prefix).
## Updating the main repo ## Updating the main repo
@ -80,6 +84,10 @@ The CI pipeline will create a release draft on GitHub
13. Update the Deno version on the website by updating 13. Update the Deno version on the website by updating
https://github.com/denoland/deno_website2/blob/main/versions.json. https://github.com/denoland/deno_website2/blob/main/versions.json.
14. Push a new tag to [`manual`](https://github.com/denoland/manual). The tag
must match the tag from point 9; you don't need to create dedicated commit
for that purpose, it's enough to tag the latest commit in that repo.
## Updating `deno_docker` ## Updating `deno_docker`
1. Open a PR on the `deno_docker` repo that bumps the Deno version in all 1. Open a PR on the `deno_docker` repo that bumps the Deno version in all