chore: update self-host image release references#4136
Conversation
|
WalkthroughThis pull request modifies two GitHub Actions publish workflows (webapp and worker-v4) to conditionally append Changes
Sequence Diagram(s)flowchart TD
ResolveTag --> CheckSemver
CheckSemver -->|matches v4.x.y| AppendV4AndLatest
CheckSemver -->|no match| KeepOriginalTags
AppendV4AndLatest --> PushImage
KeepOriginalTags --> PushImage
Estimated code review effort: 2 (Low) Related issues: None specified. Related PRs: None specified. Suggested labels: ci, documentation Suggested reviewers: None specified. Tags of 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
89c2b24 to
d8123ba
Compare
@trigger.dev/build
trigger.dev
@trigger.dev/core
@trigger.dev/python
@trigger.dev/react-hooks
@trigger.dev/redis-worker
@trigger.dev/rsc
@trigger.dev/schema-to-json
@trigger.dev/sdk
commit: |
Summary
Stable v4 Docker image builds now also publish
v4andlatesttags, giving Docker-based self-hosters a maintained floating tag to use after a stable release. The Kubernetes guide now uses the current Helm chart line and current pinned examples, so new installs and upgrades resolve to the 4.5 chart line instead of the 4.0 line.Design
The publish workflows add the floating tags only for stable
v4.x.ximage tags. Prerelease andmainbuilds keep their existing tags.