From e90d6480230ddb6e12d5695eaf004e1fc84bc6b2 Mon Sep 17 00:00:00 2001
From: Doug Beatty <44704949+dbeatty10@users.noreply.github.com>
Date: Wed, 28 Aug 2024 12:22:03 -0600
Subject: [PATCH] Update release instructions (#942)

---
 RELEASE.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/RELEASE.md b/RELEASE.md
index ac542676..459c1044 100644
--- a/RELEASE.md
+++ b/RELEASE.md
@@ -15,7 +15,7 @@ There's a few scenarios that might prompt a release:
 1. Click "Choose a tag", then paste your version number (with no "v" in the name), then click "Create new tag: x.y.z. on publish"
     - The “Release title” will be identical to the tag name
 1. Click the "Generate release notes" button
-1. Copy and paste the generated release notes into `CHANGELOG.md`, commit, and merge into the `main` branch
+1. Copy and paste the generated release notes into [`CHANGELOG.md`](https://github.com/dbt-labs/dbt-utils/blob/main/CHANGELOG.md?plain=1), reformat to match previous entries, commit, and merge into the `main` branch ([example](https://github.com/dbt-labs/dbt-utils/pull/901))
 1. Click the "Publish release" button
     - This will automatically create an "Assets" section containing:
         - Source code (zip)