From ee27cde39156ee5ebd1755edcbd6ed0ea25091fd Mon Sep 17 00:00:00 2001 From: Mateus Oliveira Date: Mon, 19 Jun 2023 10:54:18 -0300 Subject: [PATCH] fixup! fix: Lastest release link in website Signed-off-by: Mateus Oliveira --- site/content/docs/main/release-instructions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/site/content/docs/main/release-instructions.md b/site/content/docs/main/release-instructions.md index c8eb317dd..014653979 100644 --- a/site/content/docs/main/release-instructions.md +++ b/site/content/docs/main/release-instructions.md @@ -159,7 +159,7 @@ What to include in a release blog: Release blog post PR: * Prepare a PR containing the release blog post. Read the [website guidelines][2] for more information on creating a blog post. It's usually easiest to make a copy of the most recent existing post, then replace the content as appropriate. -* You also need to update `site/index.html` to have "Latest Release Information" contain a link to the new post. +* You also need to update `site/content/_index.md` to have "Latest Release Information" contain a link to the new post. * Plan to publish the blog post the same day as the release. ## Announce a release