chore: use latest self-host compose images (#4140)
## Summary Depends on #4136. Docker Compose self-hosting now uses the maintained `latest` image tag by default instead of the frozen prerelease tag. The version-locking docs keep pointing production users at explicit versioned tags when they want pinned upgrades.
This commit is contained in:
@@ -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
|
||||
|
||||
Reference in New Issue
Block a user