fix: default image tag to latest — 2.0.0-dev was stale

The 2.0.0-dev tag was only built from the now-merged
feature/serverless-2.0.0 branch. Pushes to main only tagged latest,
so the 2.0.0-dev image in the registry was frozen and missing all
recent fixes. Default to latest and also tag main builds as 2.0.0-dev
for backwards compatibility.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
2026-02-25 17:50:19 -05:00
parent c670dd124f
commit 04ed52bc8d
2 changed files with 3 additions and 4 deletions
+1 -2
View File
@@ -47,8 +47,7 @@ jobs:
type=ref,event=pr
type=sha,prefix=sha-
type=raw,value=latest,enable={{is_default_branch}}
# Development tags for serverless features
type=raw,value=2.0.0-dev,enable=${{ github.ref == 'refs/heads/feature/serverless-2.0.0' }}
type=raw,value=2.0.0-dev,enable={{is_default_branch}}
- name: Build and push Docker image
uses: docker/build-push-action@v6
+2 -2
View File
@@ -13,7 +13,7 @@ deploymentMode: persistent # persistent | dynamic
# Container image configuration
image:
repository: ghcr.io/cpfarhood/devcontainer
tag: 2.0.0-dev
tag: latest
pullPolicy: Always
# GitHub repository to clone into /workspace (ignored in dynamic mode - uses URL routing)
@@ -217,7 +217,7 @@ dynamic:
replicas: 2 # High availability
image:
repository: ghcr.io/cpfarhood/devcontainer-routing-proxy
tag: 2.0.0-dev
tag: latest
pullPolicy: Always
resources: