From 905cbb582fa6d975afa9634c443c66bbf41f01ee Mon Sep 17 00:00:00 2001
From: Alex Eagle <alex@aspect.dev>
Date: Thu, 11 Nov 2021 07:02:50 -0800
Subject: [PATCH] release: update instructions

---
 BUILD.bazel     | 1 -
 CONTRIBUTING.md | 8 ++++----
 2 files changed, 4 insertions(+), 5 deletions(-)

diff --git a/BUILD.bazel b/BUILD.bazel
index f0b4111c9..95e70d7e0 100644
--- a/BUILD.bazel
+++ b/BUILD.bazel
@@ -17,7 +17,6 @@ pkg_tar(
     name = "bazel_lib",
     srcs = [
         "README.md",
-        "version.bzl",
         "//lib:package_content",
     ],
     extension = "tar.gz",
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index dd5c6269e..390764154 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -39,9 +39,9 @@ This means that any usage of `@aspect_bazel_lib` on your system will point to th
 
 ## Releasing
 
-1. Update the constant in `version.bzl`
-1. `git commit -a -m 'release'`
-1. `git tag v$(grep VERSION version.bzl | cut -d'"' -f2)`
-1. git push && git push --tags
+1. Make sure your git state is at the right place (something like `git fetch; git checkout origin/main`)
+1. Determine the next release version, following semver (could automate in the future from changelog)
+1. `git tag -a v1.2.3` (will open an editor to put release notes)
+1. `git push --tags`
 1. Watch the automation run on GitHub actions
 1. Update the release page with auto-generated release notes