Skip to content

chore: use latest self-host compose images #4140

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
carderne wants to merge 1 commit into
base: main
Choose a base branch
from
Open

chore: use latest self-host compose images #4140

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/self-hosting/docker.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -339,7 +339,7 @@ There are several reasons to lock the version of your Docker images:
By default, the images will point at the latest versioned release via the `latest` tag. You can override this by specifying a different tag in your `.env` file. For example:
```bash
TRIGGER_IMAGE_TAG=v4.0.0
TRIGGER_IMAGE_TAG=v4.5.0
```
## Task events
Expand Down
4 changes: 2 additions & 2 deletions hosting/docker/.env.example
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,8 +34,8 @@ DIRECT_URL=postgresql://postgres:unsafe-postgres-pw@postgres:5432/main?schema=pu

# Trigger image tag
# - This is the version of the webapp and worker images to use, they should be locked to a specific version in production
# - For example: TRIGGER_IMAGE_TAG=v4.0.0-v4-beta.21
TRIGGER_IMAGE_TAG=v4-beta
# - For example: TRIGGER_IMAGE_TAG=v4.5.0
TRIGGER_IMAGE_TAG=latest

@devin-ai-integration devin-ai-integration Bot Jul 3, 2026

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.

🚩 Default image tag change from v4-beta to latest affects existing self-hosters

Existing self-hosters who cloned the repo and used the .env.example as their starting point with TRIGGER_IMAGE_TAG=v4-beta won't be affected (their .env is already set). However, anyone setting up fresh from this point forward will get latest by default. Since the latest tag is only pushed for stable v4.x.y releases (per the new workflow logic), this is safe - but it's worth noting that latest won't exist in the registry until the first stable v4 release is published with the new workflow. If someone tries to use this before that first publish, the image pull will fail.

Open in Devin Review

Was this helpful? React with 👍 or 👎 to provide feedback.


# Webapp
# - These should generally be set to the same value
Expand Down
2 changes: 1 addition & 1 deletion hosting/docker/webapp/docker-compose.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ x-logging: &logging-config

services:
webapp:
image: ghcr.io/triggerdotdev/trigger.dev:${TRIGGER_IMAGE_TAG:-v4-beta}
image: ghcr.io/triggerdotdev/trigger.dev:${TRIGGER_IMAGE_TAG:-latest}
restart: ${RESTART_POLICY:-unless-stopped}
logging: *logging-config
ports:
Expand Down
2 changes: 1 addition & 1 deletion hosting/docker/worker/docker-compose.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ x-logging: &logging-config

services:
supervisor:
image: ghcr.io/triggerdotdev/supervisor:${TRIGGER_IMAGE_TAG:-v4-beta}
image: ghcr.io/triggerdotdev/supervisor:${TRIGGER_IMAGE_TAG:-latest}
restart: ${RESTART_POLICY:-unless-stopped}
logging: *logging-config
depends_on:
Expand Down