release

docs/changelog.md

@@ -4,6 +4,7 @@ Lines for version numbers should always be formatted as `* MAJOR.MINOR.PATCH`
 with nothing else on the line.
 -->
 * HEAD
+* 0.12.0
     * [feature] BREAKING CHANGE: Allow specifying resource requirements for Kubernetes
     jobs. `KubernetesResourceRequirements` has a new required field, `requests`
     * [feature] Add `has_container_image()` API for better control over launch workflows

docs/deploy.md

@@ -22,10 +22,11 @@ Then, SSH into your remote server:
 $ ssh my-remote-server.dev
 ```
 
-Pull the latest server image
+Pull the server image for the release of Sematic you want to deploy
 
 ```shell
-$ sudo docker pull sematicai/sematic-server:latest
+$ DEPLOY_VERSION=v<MAJOR.MINOR.PATCH>  # use the actual version numbers here
+$ sudo docker pull sematicai/sematic-server:$DEPLOY_VERSION
 ```
 
 launch the server
@@ -37,7 +38,7 @@ $ sudo docker run -d -p 80:80 \
     [-e SEMATIC_AUTHENTICATE=1 -e GOOGLE_OAUTH_CLIENT_ID=123456789.apps.googleusercontent.com \]
     [-e SEMATIC_AUTHORIZED_EMAIL_DOMAIN=yourdomain.com \]
     [-p 443:443 -e CERTIFICATE=/path/to/certificate.pem -e PRIVATE_KEY=/path/to/private.key \]
-    sematicai/sematic-server:latest
+    sematicai/sematic-server:$DEPLOY_VERSION
 ```
 
 where `DATABASE_URL` is the fully-qualified URL of your Postgres database. It

sematic/versions.py

@@ -5,7 +5,7 @@
 # the sdk. Should be bumped any time a release is made. Should be set
 # to whatever is the version after the most recent one in changelog.md,
 # as well as the version for the sematic wheel in wheel_version.bzl
-CURRENT_VERSION = (0, 11, 0)
+CURRENT_VERSION = (0, 12, 0)
 
 # Represents the smallest client version that works with the server
 # at the CURRENT_VERSION. Should be updated any time a breaking change

sematic/wheel_version.bzl

@@ -2,4 +2,4 @@
 # changelog.md.
 # This is the version that will be attached to the
 # wheel that bazel builds for sematic.
-wheel_version_string = "0.11.0"
+wheel_version_string = "0.12.0"