Skip to content

fix: reconcile schedules after runner upgrades - #100

Merged
vishr merged 1 commit into
mainfrom
fix/schedule-apply
Aug 23, 2026
Merged

fix: reconcile schedules after runner upgrades#100
vishr merged 1 commit into
mainfrom
fix/schedule-apply

Conversation

@vishr

@vishr vishr commented Aug 23, 2026

Copy link
Copy Markdown
Member

Summary

  • add an explicit ob schedule apply convergence path
  • serialize it with the application lock, schedule mutex, fence, and journal
  • cover legacy runner units on a real SSH/systemd host
  • update the generated CLI reference and operator guide

Closes #99

Verification

  • 1,531 uncached Go tests
  • just check
  • just lint
  • Docker E2E: 286.649s
  • real-server E2E on final code: 650.402s

Add an explicit locked and journaled apply path so units generated by an older runner can converge without an unrelated deploy.

Closes #99
@vishr
vishr merged commit 2c8d113 into main Aug 23, 2026
5 checks passed
@vishr
vishr deleted the fix/schedule-apply branch August 23, 2026 01:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

schedule: job units converge only through a deploy, so a runner upgrade leaves the old units installed

1 participant