Add v prefix to versions to be compatible with go.mod (#169)

cognitedata · Sep 18, 2023 · 499f489 · 499f489
1 parent b02ab2c
commit 499f489
Show file tree

Hide file tree

Showing 2 changed files with 5 additions and 3 deletions.
diff --git a/.github/workflows/release.yaml b/.github/workflows/release.yaml
@@ -4,7 +4,7 @@ name: Release
 on:
   push:
     tags:
-      - "*.*.*"
+      - "v*.*.*"
 
 jobs:
   build:

diff --git a/RELEASING.md b/RELEASING.md
@@ -1,4 +1,6 @@
 # Releasing Bazel-snapshots
 
-To release a new version of Bazel-snapshots, create a new git tag in following semver versioning format, eks. `x.y.z`. When a tag of this format is pushed
-to Github the release action will run and generate a new draft Github Release. The draft can be promoted to a proper release at your convenience after you've verified that everything looks right in the draft.
+To release a new version of Bazel-snapshots, create a new git tag in following semver versioning format, eks. `vx.y.z`.
+The v prefix is necessary for being able to import it from a go.mod.
+When a tag of this format is pushed to Github the release action will run and generate a new draft Github Release.
+The draft can be promoted to a proper release at your convenience after you've verified that everything looks right in the draft.