Releases: Forward-Future/DeployBot
DeployBot v0.2.15
DeployBot v0.2.15 removes serial exact-head CI starvation across cumulative integration pull requests.
- Dispatches every missing integration CI workflow before waiting, so one slow GitHub runner cannot delay dispatch for later integration batches.
- Polls all active integration PRs together under one shared deadline.
- Prevents duplicate workflow dispatches while GitHub registers a requested run.
- Reports the exact missing, queued, or failed integration workflow in slow-queue status.
- Adds production-shaped regression coverage for parallel dispatch and delayed run visibility.
Privileged runtime pin: 1170353958fb31718977dfff465ce9e1a89b8db4.
Merged main: 53f1adc0bf1763866eeccbfbde923be2c60746c7 · CI.
DeployBot v0.2.14
DeployBot v0.2.14 removes verified-release follower churn and makes native receipt ownership explicit.
- Stops scheduled workers from spending 77–84 seconds retrying source-owned receipts when no delivery webhook exists.
- Caches the append-only registry once per worker.
- Returns a mandatory receipt handoff from deployment requests.
- Requires Cursor, Codex, and Claude source threads to attach their native follow-up before returning.
Privileged runtime pin: a5f80423f5168873d0801694baaf9d8b35d96ebd.
DeployBot v0.2.11
Codex now uses DeployBot directly through the installed CLI without starting a local MCP subprocess. The release removes Codex MCP wiring and dependencies, converts Codex skills to explicit CLI commands, preserves the optional MCP server for Claude Code, Cursor, and generic MCP clients, and ensures CI runs when draft pull requests become ready.
DeployBot v0.2.10
What's Changed
- [codex] Fix DeployBot delivery stalls and observability by @mberman84 in #32
- Release DeployBot v0.2.10 by @mberman84 in #33
Full Changelog: v0.2.9...v0.2.10
DeployBot v0.2.9
What's Changed
- Document the complete DeployBot interface by @mberman84 in #23
- [codex] Harden burst delivery coordination by @mberman84 in #27
- Notify source threads after verified deployment by @mberman84 in #29
- Make deployment receipts human-readable by @mberman84 in #30
- [codex] Prepare DeployBot v0.2.9 global plugin release by @mberman84 in #31
Full Changelog: v0.2.8...v0.2.9
DeployBot v0.2.8
What changed
- preserves release takeover after an empty-queue wake-up
- follows only when exact-main CI, deployment, failure handling, or final completion still needs an owner
- skips idle all-mode integration batches instead of holding the coordinator for the full timeout
- adds direct regression coverage for both the takeover and all-mode paths
Verification
- 91 tests across Python 3.11, 3.12, and 3.13
- optional MCP-free install verified (89 passed, 2 optional skips)
- Ruff and package build passed
DeployBot v0.2.7
DeployBot now follows the active exact-main release when an event wakes it after the merge queue is already empty. This closes the CI-completion bootstrap gap and ensures the protected Deploy workflow is dispatched and followed through verification.
- Follow releases on empty-queue event wakeups
- Keep CI dispatch limited to invocations that actually merged work
- Add regression coverage for the event-driven handoff
- Pin Codex, Cursor, and Claude Code adapters to the reviewed implementation commit
DeployBot v0.2.6
DeployBot v0.2.6 finishes the review cleanup from the Astro release canary.
- Compares CI and deployment timestamps as normalized instants.
- Handles equivalent ISO timestamps with offsets and fractional seconds correctly.
- Repairs Claude Code and Codex MCP adapter formatting.
- Includes 89 passing tests across Python 3.11–3.13.
DeployBot v0.2.5
DeployBot v0.2.5 completes the built-in-token release chain.
- Explicitly dispatches protected deployment workflows after token-driven exact-main CI succeeds.
- Carries the exact successful CI SHA and run ID into deployment.
- Ignores skipped deployment wake-ups that never attempted a release.
- Lets newer successful CI supersede an older failed deployment attempt.
- Pauses safely if deployment dispatch cannot be completed.
Deployment workflows should accept workflow_dispatch inputs named ci_sha and ci_run_id and verify that run before release.
DeployBot v0.2.4
Patch release for review-driven delivery hardening.
- privileged wake events are scoped to trusted labels, same-repository PR events, or PR-associated external checks
- workflow-run history is fully paginated
- integration status and merge authorization re-check every source intent
- persistent HTTP health failures report
verify-failedand pause delivery - consumers pin implementation commit
9986210b077ebb4c53f2c5b1bbd461ba02dfce19 - CI passed on Python 3.11, 3.12, and 3.13