ci: tag main builds dev-latest, reserve latest for tagged prod releases - #177
Merged
Conversation
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.
Contributor
There was a problem hiding this comment.
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
latestforserver/v*tag builds. - Dev workflow now publishes
dev-latest(viaenv_prefix: "dev") formainbuilds, while keeping immutableauto-<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 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Every merge to
mainpublished the floatinglatestDocker tag, so anything pullingmemory-engine:latestwas tracking unreleasedmain.latestshould mean "current production release."Change
mainauto-<sha>,latestauto-<sha>,dev-latestserver/v*tagauto-<sha>auto-<sha>,latestdeploy-dev.yaml: keeps"latest": truebut 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:Notes
dev-latest, not a baredev— the shared workflow only supports the<prefix>-latestshape, and itsdeploy.yamluses the same convention. A baredevtag would require a new input upstream.sha, which resolves to the immutableauto-<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.