foster/denoland-deno
1
0
Fork 0
mirror of https://github.com/denoland/deno.git synced 2024-12-22 07:14:47 -05:00
Code Issues Packages 1 Wiki Activity

chore: update cut_a_release.md (#13444)

Browse source
This commit is contained in:
Bartek Iwańczuk 2022-01-21 10:16:57 +01:00 committed by GitHub
parent 2ea535c8c1
commit 56d0ca7f52
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 11 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

16
tools/cut_a_release.md
View file

@ -33,8 +33,8 @@ Before starting the process write a message in company's #general channel:
2. Open a PR on the `deno_std` repo that bumps the version in `version.ts` and 2. Open a PR on the `deno_std` repo that bumps the version in `version.ts` and
updates `Releases.md`. You can use following command to generate a short list updates `Releases.md`. You can use following command to generate a short list
that needs to be updated: `git log --oneline <previous_tag>..` (replace that needs to be updated: `git log --oneline <previous_tag>..` (replace
`<previous_tag>` with actual latest tag). Remove all commits that are not `<previous_tag>` with actual latest tag, eg. `git log --oneline 0.122.0..`).
`feat` or `fix`. Remove all commits that are not `feat` or `fix`.
3. Before merging the PR, make sure that all tests pass when run using binary 3. Before merging the PR, make sure that all tests pass when run using binary
produced from bumping crates (point 3. from below). produced from bumping crates (point 3. from below).
@ -42,7 +42,10 @@ Before starting the process write a message in company's #general channel:
4. When merging the PR, ensure that the commit name is exactly the version name. 4. When merging the PR, ensure that the commit name is exactly the version name.
Eg. `0.121.0`, not `0.121.0 (#1810)`. Eg. `0.121.0`, not `0.121.0 (#1810)`.
5. Create a tag with the version number (_without_ `v` prefix). 5. Pull the latest `main` branch and make sure the commit from the merged PR is
there. Create a tag with the version number (_without_ `v` prefix), eg.
`deno tag 0.122.0 <commit_hash>`, then push the tag to the
`denoland/deno_std` repository, eg. `git push upstream 0.122.0`.
6. Once CI passes, copy contents of `Releases.md` you added, and create a new 6. Once CI passes, copy contents of `Releases.md` you added, and create a new
release on GitHub (https://github.com/denoland/deno_std/releases). release on GitHub (https://github.com/denoland/deno_std/releases).
@ -93,7 +96,10 @@ verify on GitHub that everything looks correct.
9. If you are doing a patch release, answer `y` to the _Increment patch?_ 9. If you are doing a patch release, answer `y` to the _Increment patch?_
prompt. prompt.
10. Use the output of the above command to update `Releases.md` 10. Use the output of the above command to update `Releases.md`. **If you are
cutting a minor release**: make sure that there are no duplicate entries in
previous releases; most often commits with `fix` prefix would have been
included in patch releases.
11. Update link in `cli/compat/mod.rs` with the released version of `deno_std` 11. Update link in `cli/compat/mod.rs` with the released version of `deno_std`
and do a search through the tests to find std urls that need to be updated. and do a search through the tests to find std urls that need to be updated.
@ -103,7 +109,7 @@ verify on GitHub that everything looks correct.
13. Make sure CI pipeline passes. 13. Make sure CI pipeline passes.
14. Publish `cli` crate to `crates.io` 14. Publish `cli` crate to `crates.io`: `cd cli && cargo publish`
15. Merge the PR. 15. Merge the PR.