Skip to content

ci: tag main builds dev-latest, reserve latest for tagged prod releases - #177

Merged
murrayju merged 1 commit into
mainfrom
murrayju/dev-latest-docker-tag
Jul 30, 2026
Merged

ci: tag main builds dev-latest, reserve latest for tagged prod releases#177
murrayju merged 1 commit into
mainfrom
murrayju/dev-latest-docker-tag

Conversation

@murrayju

Copy link
Copy Markdown
Member

Problem

Every merge to main published the floating latest Docker tag, so anything pulling memory-engine:latest was tracking unreleased main. latest should mean "current production release."

Change

Trigger Tags published (before) Tags published (after)
push to main auto-<sha>, latest auto-<sha>, dev-latest
push of server/v* tag auto-<sha> auto-<sha>, latest
  • deploy-dev.yaml: keeps "latest": true but adds "env_prefix": "dev".
  • deploy-prod.yaml: flips "latest": false -> true.

Both knobs are existing inputs of the shared build workflow in timescale/tiger-agents-deploy, which resolves the floating tag as:

tags: |
  ${{ inputs.latest && (inputs.env_prefix != '' && format('{0}-latest', inputs.env_prefix) || 'latest') || '' }}
  auto-${{ inputs.sha }}

Notes

  • The dev floating tag is dev-latest, not a bare dev — the shared workflow only supports the <prefix>-latest shape, and its deploy.yaml uses the same convention. A bare dev tag would require a new input upstream.
  • No deploy behavior changes. Both workflows dispatch the deploy with sha, which resolves to the immutable auto-<sha> tag; neither env pulls a floating tag. This PR only changes which floating pointers get published for external consumers.

Testing

CI-config only; no application code touched. Verified both dispatch payloads parse as valid JSON with the expected keys.

Every merge to main was publishing the floating `latest` tag, so any
consumer pulling `latest` tracked unreleased main. Move main's floating
tag to `dev-latest` (via the shared build workflow's `env_prefix`) and
publish `latest` from the `server/v*` tagged prod deploy instead.

Deploys themselves are unaffected: both workflows dispatch the deploy
with `sha`, which resolves to the immutable `auto-<sha>` tag.
Copilot AI review requested due to automatic review settings July 30, 2026 15:14
@murrayju
murrayju requested review from cevian and jgpruitt as code owners July 30, 2026 15:14

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the GitHub Actions deploy workflows so the Docker floating tag latest is only produced for tagged production releases, while main builds publish a separate dev-latest pointer—preventing consumers of memory-engine:latest from tracking unreleased main.

Changes:

  • Prod workflow now publishes latest for server/v* tag builds.
  • Dev workflow now publishes dev-latest (via env_prefix: "dev") for main builds, while keeping immutable auto-<sha> tags.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File Description
.github/workflows/deploy-prod.yaml Switches build dispatch input to publish the floating latest tag for tagged prod releases.
.github/workflows/deploy-dev.yaml Adds env_prefix: "dev" so main builds publish dev-latest instead of latest.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

"dockerfile_path": "packages/server/Dockerfile",
"sha": "${{ needs.resolve.outputs.sha }}",
"latest": false
"latest": true
@murrayju
murrayju merged commit 2a9bdff into main Jul 30, 2026
7 checks passed
@murrayju
murrayju deleted the murrayju/dev-latest-docker-tag branch July 30, 2026 15:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants