diff options
Diffstat (limited to 'tools')
| -rw-r--r-- | tools/cut_a_release.md | 45 | ||||
| -rwxr-xr-x[-rw-r--r--] | tools/release/01_bump_dependency_crate_versions.ts | 0 |
2 files changed, 25 insertions, 20 deletions
diff --git a/tools/cut_a_release.md b/tools/cut_a_release.md index 5ce421d8b..a4fed35d1 100644 --- a/tools/cut_a_release.md +++ b/tools/cut_a_release.md @@ -6,25 +6,30 @@ cut.** ## Updating `deno_std` -1. Open a PR on the `deno_std` repo that bumps the version in `version.ts` and +1. Checkout a branch for releasing `std` (e.g. `release_#.#.#`). + +2. Open a PR on the `deno_std` repo that bumps the version in `version.ts` and updates `Releases.md` -2. 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). -3. Create a tag with the version number (_without_ `v` prefix). +4. Create a tag with the version number (_without_ `v` prefix). ## Updating the main repo -1. Run `./tools/release/01_bump_dependency_crate_versions.ts` to increase the +1. Checkout a branch for releasing crate dependencies (e.g. `deps_#.#.#`). + +2. Run `./tools/release/01_bump_dependency_crate_versions.ts` to increase the minor versions of all crates in the `bench_util`, `core`, `ext`, and `runtime` directories. -2. Create a PR for this change. +3. Commit these changes with a commit message like + `chore: bump crate version for #.#.#` and create a PR for this change. -3. Make sure CI pipeline passes (DO NOT merge yet). +4. Make sure CI pipeline passes (DO NOT merge yet). -4. Run `./tools/release/02_publish_dependency_crates.ts` to publish these bumped +5. Run `./tools/release/02_publish_dependency_crates.ts` to publish these bumped crates to `crates.io` **Make sure that `cargo` is logged on with a user that has permissions to @@ -34,35 +39,35 @@ cut.** code, then after applying the fixes they should be committed and pushed to the PR. -5. Once all crates are published merge the PR. +6. Once all crates are published merge the PR. -6. Run `./tools/release/03_bump_cli_version.ts` to bump the CLI version. +7. Run `./tools/release/03_bump_cli_version.ts` to bump the CLI version. -7. Use the output of the above command to update `Releases.md` +8. Use the output of the above command to update `Releases.md` -8. Create a PR for these changes. +9. Create a PR for these changes. -9. Make sure CI pipeline passes. +10. Make sure CI pipeline passes. -10. Publish `cli` crate to `crates.io` +11. Publish `cli` crate to `crates.io` -11. Merge the PR. +12. Merge the PR. -12. Create a tag with the version number (with `v` prefix). +13. Create a tag with the version number (with `v` prefix). -13. Wait for CI pipeline on the created tag branch to pass. +14. Wait for CI pipeline on the created tag branch to pass. The CI pipeline will create a release draft on GitHub (https://github.com/denoland/deno/releases). -14. Upload Apple M1 build to the release draft & to dl.deno.land. +15. Upload Apple M1 build to the release draft & to dl.deno.land. -15. Publish the release on Github +16. Publish the release on Github -16. Update the Deno version on the website by updating +17. Update the Deno version on the website by updating https://github.com/denoland/deno_website2/blob/main/versions.json. -17. Push a new tag to [`manual`](https://github.com/denoland/manual). The tag +18. Push a new tag to [`manual`](https://github.com/denoland/manual). The tag must match the CLI tag; you don't need to create dedicated commit for that purpose, it's enough to tag the latest commit in that repo. diff --git a/tools/release/01_bump_dependency_crate_versions.ts b/tools/release/01_bump_dependency_crate_versions.ts index b5ee6968d..b5ee6968d 100644..100755 --- a/tools/release/01_bump_dependency_crate_versions.ts +++ b/tools/release/01_bump_dependency_crate_versions.ts |