diff options
| -rw-r--r-- | tools/cut_a_release.md | 28 |
1 files changed, 11 insertions, 17 deletions
diff --git a/tools/cut_a_release.md b/tools/cut_a_release.md index ca2d2d273..499642e0e 100644 --- a/tools/cut_a_release.md +++ b/tools/cut_a_release.md @@ -28,27 +28,21 @@ Before starting the process write a message in company's #general channel: ## 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 - updates `Releases.md`. You can use following command to generate a short list - that needs to be updated: `git log --oneline <previous_tag>..` (replace - `<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 - produced from bumping crates (point 3. from below). +2. Click on the "Run workflow" button. + 1. For the kind of release, select "minor". + 2. Run the workflow. -4. When merging the PR, ensure that the commit name is exactly the version name. - Eg. `0.121.0`, not `0.121.0 (#1810)`. +3. A PR will be automatically created. Follow the checklist in the PR and review + it. -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. - `git tag 0.122.0 <commit_hash>`, then push the tag to the `denoland/deno_std` - repository, eg. `git push upstream 0.122.0`. +4. Merge the PR. While doing so, ensure that the commit name is exactly the + version name. Eg. `0.121.0`, not `0.121.0 (#1810)`. -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). +5. Wait for the CI run to complete which will tag the repo and create a draft + release. Review the draft release and then publish it. ## Updating the main repo |