Cutting a release¶
When we “cut” a release, we begin the process of making a release. (This is not to be confused with publishing a release, which is the last step.) After a release is cut, we can perform manual QA testing and polish any remaining small changes.
-
Set a VERSION variable in your shell
Run this command to set a local variable within your shell to the version number of the release you’re making.
Note
Do not prefix the version with
v
. -
Cut the release branch
Run these commands from within the repo, locally.
-
Update version numbers
-
Create the release PR
-
Publish Docker images
-
Log in to DockerHub
(Use your personal Docker credentials. Your personal Docker account will need to be a member of our mathesar Docker org.)
-
Locally clone the repo into a clean directory and go there.
REPO_DIR=$(pwd) CLEAN_REPO_DIR=$(mktemp -d) cd $CLEAN_REPO_DIR git clone -b $VERSION --single-branch --no-tags "$REPO_DIR" .
(This ensures that files which are ignored by git don’t end up in the Docker image.)
-
Build and push images to DockerHub
docker buildx build \ -t mathesar/mathesar-caddy:$VERSION \ --builder=cloud-mathesar-release-builder \ --platform=linux/amd64,linux/arm64 \ --push \ -f Dockerfile.caddy . docker buildx build \ -t mathesar/mathesar-prod:$VERSION \ --builder=cloud-mathesar-release-builder \ --platform=linux/amd64,linux/arm64 \ --push .
(These images are intentionally not tagged as latest — that will happen during publication.)
-
Clean up
-