From b9907d10d440ccad0f72dbd14969e9da0f1ec100 Mon Sep 17 00:00:00 2001 From: David Sherret Date: Thu, 2 Feb 2023 18:41:46 -0500 Subject: [PATCH] chore: add release checklist step to check the benchmarks page (#17632) The 1.30.1 release had a performance regression that would have been caught by looking at the benchmarks page. This adds a pre-flight step to the release checklist for the person doing the release to go to this page and look at the output. This would have prevented #17629 --- tools/release/release_doc_template.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/tools/release/release_doc_template.md b/tools/release/release_doc_template.md index 0bc6c11e9a..eae7aee123 100644 --- a/tools/release/release_doc_template.md +++ b/tools/release/release_doc_template.md @@ -13,6 +13,8 @@ release from) should be frozen and no commits should land until the release is 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 ()`