Alerts: wire up worker image releases
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 39.9k
- Forks
- 3.4k
- Avg merge
- 6h 51m
- Merged PRs (30d)
- 232
Description
Current status — deferred
This work is parked, not completed, and is not a blocker for the next development slice. Revisit before production rollout.
Automatic worker image releases/promotion are deferred. Changes to an enabled worker fleet still need an explicit verified release/promotion path; do not assume later source changes reach workers automatically.
Scope
Wire worker image releases for #97317 using the current release pipeline conventions.
Release names:
temporal-worker-alerts-product-evaluationtemporal-worker-alerts-product-delivery
Remaining
- Trace the current image-build/release path and add or confirm both fleets' path filters and dispatch/release configuration.
- Confirm an image containing the merged workflows and schedule can reach each enabled dev fleet.
- Record evidence that a later source change produces the expected release/freight for both fleets.
- Keep promotion limited to environments already rolled out; no production activation here.
Merged dev onboarding: PostHog/charts#15461. Schedule: #99141 / #97448. Deployment verification: PostHog/charts#15371.
Cleanup inspection found no alerts-product entries in .github/workflows/container-images-cd.yml on master. That is not proof of a missing release path elsewhere; trace the current pipeline before implementing or closing this issue.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Trace the current image-build and release path, starting with .github/workflows/container-images-cd.yml and the related dispatch or release configuration. Check the filters and release behavior for temporal-worker-alerts-product-evaluation and temporal-worker-alerts-product-delivery, then verify that a later source change produces the expected release evidence for both enabled dev fleets without activating production.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, github-actions
- Domain
- ci-cd, devops, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100