From 40049d65a9d336689abde02bfbb6d6ef8f913452 Mon Sep 17 00:00:00 2001 From: Yoshiya Hinosawa Date: Sat, 27 Apr 2024 19:11:44 +0900 Subject: [PATCH] chore(tools): update release template --- tools/release/release_doc_template.md | 48 ++------------------------- 1 file changed, 3 insertions(+), 45 deletions(-) diff --git a/tools/release/release_doc_template.md b/tools/release/release_doc_template.md index bed3a4def4602..ee334352f1ea3 100644 --- a/tools/release/release_doc_template.md +++ b/tools/release/release_doc_template.md @@ -4,7 +4,6 @@ - Forks and local clones of [`denoland/deno`](https://github.com/denoland/deno/), - [`denoland/deno_std`](https://github.com/denoland/deno_std/), [`denoland/dotcom`](https://github.com/denoland/dotcom/), [`denoland/deno_docker`](https://github.com/denoland/deno_docker/), [`denoland/deno-docs`](https://github.com/denoland/deno-docs) @@ -16,7 +15,7 @@ cut.** - [ ] Check https://deno.land/benchmarks?-100 and ensure there's no recent regressions. - [ ] Write a message in company's #cli channel: - `:lock: deno and deno_std are now locked ()` + `:lock: deno is now locked ()` ## Patch release preparation @@ -41,42 +40,6 @@ verify on GitHub that everything looks correct. - [ ] Unstable `feat` commits were merged. - [ ] Internal API commits like `feat(core)` were merged. -## Updating `deno_std` - -- [ ] Go to the "version_bump" workflow in the deno_std repo's actions: - https://github.com/denoland/deno_std/actions/workflows/version_bump.yml - 1. Click on the "Run workflow" button. - 1. For the kind of release, select "minor". - 1. Run the workflow. - -- [ ] A PR will be automatically created. Follow the checklist in the PR, review - it, and merge the PR. - - ⛔ DO NOT create a release tag manually. That will automatically happen. - -
- Failure Steps - - 1. Checkout the latest main. - 2. Manually run `./_tools/release/01_bump_version.ts --minor` - 1. Ensure the version in `version.ts` is updated correctly. - 2. Ensure `Releases.md` is updated correctly. - 3. Ensure all the tests pass with the latest build (examine the repo for - what the command is and run the local built deno binary) - 3. Open a PR with the changes and continue with the steps below. -
- -- Wait for the CI run to complete which will automatically tag the repo and - create a draft release. - - [ ] Review the draft release and then publish it. - -
- Failure Steps - - 1. Tag the repo manually in the format `x.x.x` - 2. Draft a new GH release by copying and pasting the release notes from - `Releases.md` -
- ## Updating `deno` ### Phase 1: Bumping versions @@ -154,7 +117,7 @@ verify on GitHub that everything looks correct. automatically opened that forwards the release commit back to main. If so, merge it. If not and it failed, please manually create one. -## Updating `deno.land/api` & `deno.land/std` symbols +## Updating `deno.land/api` symbols This should occur after the Deno CLI & std are fully published, as the build script generates the symbols based on the latest tags. @@ -163,17 +126,12 @@ script generates the symbols based on the latest tags. branch: https://github.com/denoland/apiland_scripts/actions/workflows/release_cli.yml - [ ] Verify the workflow ran successfully. -- [ ] Run the `release STD` workflow in the apiland_scripts repo on the main - branch: - https://github.com/denoland/apiland_scripts/actions/workflows/release_std.yml - - [ ] Verify the workflow ran successfully.
Failure Steps 1. Clone `deno/apiland_scripts`. 2. Execute `deno task release:cli`. - 3. Execute `deno task release:std`.
## Updating `deno_docker` @@ -193,4 +151,4 @@ script generates the symbols based on the latest tags. ## All done! - [ ] Write a message in company's #cli channel: - `:unlock: deno and deno_std are now unlocked`. + `:unlock: deno is now unlocked`.