Prepare for next release

hashicorp · May 11, 2022 · 394eafe · 394eafe
1 parent 52e95d6
commit 394eafe
Show file tree

Hide file tree

Showing 3 changed files with 4 additions and 4 deletions.
diff --git a/.release/ci.hcl b/.release/ci.hcl
@@ -3,7 +3,7 @@ schema = "1"
 project "nomad" {
   team = "nomad"
   slack {
-    notification_channel = "CUYKT2A73"
+    notification_channel = "C03B5EWFW01"
   }
   github {
     organization = "hashicorp"

diff --git a/GNUmakefile b/GNUmakefile
@@ -49,7 +49,7 @@ PROTO_COMPARE_TAG ?= v1.0.3$(if $(findstring ent,$(GO_TAGS)),+ent,)
 
 # LAST_RELEASE is the git sha of the latest release corresponding to this branch. main should have the latest
 # published release, and release branches should point to the latest published release in the X.Y release line.
-LAST_RELEASE ?= v1.2.6
+LAST_RELEASE ?= v1.3.0
 
 default: help
 

diff --git a/version/version.go b/version/version.go
@@ -11,12 +11,12 @@ var (
 	GitDescribe string
 
 	// The main version number that is being run at the moment.
-	Version = "1.3.0"
+	Version = "1.3.1"
 
 	// A pre-release marker for the version. If this is "" (empty string)
 	// then it means that it is a final release. Otherwise, this is a pre-release
 	// such as "dev" (in development), "beta", "rc1", etc.
-	VersionPrerelease = ""
+	VersionPrerelease = "dev"
 
 	// VersionMetadata is metadata further describing the build type.
 	VersionMetadata = ""