summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--tools/cut_a_release.md19
1 files changed, 18 insertions, 1 deletions
diff --git a/tools/cut_a_release.md b/tools/cut_a_release.md
index 2940d762b..872f13be2 100644
--- a/tools/cut_a_release.md
+++ b/tools/cut_a_release.md
@@ -8,7 +8,8 @@
- [ ] Forks and local clones of
[`denoland/deno`](https://github.com/denoland/deno/),
[`denoland/deno_std`](https://github.com/denoland/deno_std/),
- [`denoland/dotland`](https://github.com/denoland/dotland/) and
+ [`denoland/dotland`](https://github.com/denoland/dotland/),
+ [`denoland/docland`](https://github.com/denoland/docland/),
[`denoland/deno_docker`](https://github.com/denoland/deno_docker/)
- [ ] Ensure that external dependencies are up-to date in `denoland/deno` (e.g.
`rusty_v8`, `serde_v8`, `deno_doc`, `deno_lint`).
@@ -100,6 +101,22 @@ cut.**
been updated to reflect Web API changes in this release. Usually done ahead
of time by @lucacasonato.
+## Updating `doc.deno.land`
+
+This should occur after the Deno CLI is fully published, as the build script
+queries the GitHub API to determine what it needs to change and update.
+
+1. Goto the cloned report for `denoland/docland`.
+
+2. Checkout a new branch (e.g. `git checkout -b deno_1.17.0`).
+
+3. Execute `./build.ts` (or
+ `deno run --config deno.jsonc --import-map import-map.json --allow-read=. --allow-write=./static --allow-net build.ts`).
+
+4. Commit changes and raise a PR on `denoland/docland`.
+
+5. Merging the approved PR will trigger deployment to Deploy of the updates.
+
## Updating `deno_docker`
1. Open a PR on the `deno_docker` repo that bumps the Deno version in all