chore(release): bump version to 0.5.16#538
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Version bump for release v0.5.16. The release will be published after this PR passes the required checks and merges.
dispatch 0.5.16
Highlights
In-app scheduler (retires external cron/heartbeat). Scheduled sync, the
groomer, PR follow-up, and closed-issue pruning now run on internal timers
inside the app process instead of external CronJobs. Opt in with
DISPATCH_SCHEDULER_ENABLED=true. Once enabled, you can retire thedispatch-heartbeatcron. (#515, #520)0to disable that job:DISPATCH_SYNC_INTERVAL_MS(default 15m)DISPATCH_GROOMER_INTERVAL_MS(default 10m)DISPATCH_PR_FOLLOWUP_INTERVAL_MS(default 15m)DISPATCH_PRUNE_CLOSED_INTERVAL_MS(default daily)DISPATCH_SCHEDULER_STARTUP_DELAY_MSso migrationsfinish first. Left disabled, dev/CI never spin timers.
Closed issues always move to
status/done. Sync now enforces the terminalstatus: a closed issue has its status label reconciled to
status/done(andother
status/*labels stripped) directly on GitHub, so the next sync can'trevert it. (#521)
Schema-constrained groomer output. The groomer requests
json_schemaresponses (with the lane enum built from your configured lanes) and falls back
to
json_objecton a 400. This lets smaller models — e.g. a 4B — groomreliably. (#516)
Groomer runs are serialized. A DB-backed lock (reusing the
sync_locktable) prevents overlapping groomer runs. (#517)
Fixes & internals
postinstallonly when the schema is present,fixing Docker builds where
npm ciruns before the schema is copied. (chore(db): generate prisma client on postinstall #512)isStatusLabelguard across routes; tighter$transactionadaptercast; removed dead lane-classification code and the unused
effectdependency. (refactor(routes): share the isStatusLabel guard #518, refactor(prisma): tighten the $transaction adapter cast #519, refactor(lane): remove dead lane-classification code #522, chore(deps): remove unused effect dependency #513)
Tests
sync mutex. (test(agent-queue-fetch): cover the queue/next-task fetch path #524)
Dependencies