-
fix: sync declarative schedules on deployment rollback (#3468)
frostbyte_neo released this
2026-05-01 14:39:19 +00:00 | 777 commits to main since this release✅ Checklist
- I have followed every step in the contributing
guide - The PR title follows the convention.
- I ran and tested the code works
Testing
- Reviewed the code flow for deployment rollback
(ChangeCurrentDeploymentService) and confirmed it was missing schedule
sync - Verified all 4 callers of
ChangeCurrentDeploymentService(UI
rollback, UI promote, API promote, finalize deployment) are now covered - Ran
pnpm run typecheck --filter webapp— passes cleanly
Changelog
When rolling back (or manually promoting) a deployment, declarative
schedules were not being synced to match the target deployment's worker
metadata. Schedules remained as configured by the most recent deployment
rather than reflecting the target version's schedule configuration.This fix adds a call to
syncDeclarativeSchedulesin
ChangeCurrentDeploymentServiceafter the deployment promotion is
updated. It parses the target deployment's stored
BackgroundWorkerMetadatato restore the correct schedule state. This
covers both rollback and promote paths (UI and API). Errors are handled
gracefully so they don't block the deployment change itself.
Screenshots
N/A — backend-only change.
💯
Link to Devin session:
https://app.devin.ai/sessions/0debf012b58c4132be778f8ea88cd2b6
Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
Co-authored-by: nick 55853254+nicktrn@users.noreply.github.comDownloads
- I have followed every step in the contributing