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

chore(ci): update deno_std release steps (#14178)

Browse source
This commit is contained in:
David Sherret 2022-04-04 09:37:54 -04:00 committed by GitHub
parent 995d1666ff
commit fcd986875a
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 11 additions and 17 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

28
tools/cut_a_release.md
View file

@ -28,27 +28,21 @@ Before starting the process write a message in company's #general channel:
## Updating `deno_std` ## Updating `deno_std`
1. Checkout a branch for releasing `std` (e.g. `release_#.#.#`). 1. Go to the "version_bump" workflow in the deno_std repo's actions:
https://github.com/denoland/deno/actions/workflows/version_bump.yml
2. Open a PR on the `deno_std` repo that bumps the version in `version.ts` and 2. Click on the "Run workflow" button.
updates `Releases.md`. You can use following command to generate a short list 1. For the kind of release, select "minor".
that needs to be updated: `git log --oneline <previous_tag>..` (replace 2. Run the workflow.
`<previous_tag>` with actual latest tag, eg. `git log --oneline 0.122.0..`).
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. A PR will be automatically created. Follow the checklist in the PR and review
produced from bumping crates (point 3. from below). it.
4. When merging the PR, ensure that the commit name is exactly the version name. 4. Merge the PR. While doing so, ensure that the commit name is exactly the
Eg. `0.121.0`, not `0.121.0 (#1810)`. version name. Eg. `0.121.0`, not `0.121.0 (#1810)`.
5. Pull the latest `main` branch and make sure the commit from the merged PR is 5. Wait for the CI run to complete which will tag the repo and create a draft
there. Create a tag with the version number (_without_ `v` prefix), eg. release. Review the draft release and then publish it.
`git 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
release on GitHub (https://github.com/denoland/deno_std/releases).
## Updating the main repo ## Updating the main repo