Stable Deployment Branches¶
For deployments that need a fixed release with cherry-picked hotfixes (rather than upgrading to the latest), create a stable branch:
Tag patch releases on the stable branch:
This triggers the release workflow, which builds and pushes versioned images. A downstream deployment fork pins a version by checking out the tag (git checkout v0.1.1) before building the host image.
Note: do not use + in tags — Docker image tags don't allow the + character.
Because the workspace base image is pinned in the Dockerfile, stable branches are isolated from base image changes on main. The branch only gets changes that are explicitly cherry-picked onto it.