[hardbyte]

Prepares 0.6.17 on release/0.6.6. The release is cut by pushing the v0.6.17 tag on the merge commit once branch CI has passed on it.

Changes

• Workspace, CLI and Python package versions go from 0.6.16 to 0.6.17, with the three lockfiles.
• The changelog's Unreleased section becomes [0.6.17] — 2026-11-12 with a summary paragraph.
• The Ring prunes starve under claim load: claim_ready_runtime locks every slot child, so the 10 ms ACCESS EXCLUSIVE never wins #721 changelog entry is rewritten to say what fix(queue-storage): keep prune's checks off the exclusive lock and remove its lock-order cycles (#721) #723 does and what it leaves open: queue prune's checks no longer run under ACCESS EXCLUSIVE and two lock-order cycles are gone, but prune is still blocked in most attempts under a large abandoned-claim backlog.
• docs/upgrade-0.6.16-to-0.6.17.md covers the two schema patches and the grant for awa.runtime_maintenance_eligibility, asynchronous claim commits, the maintenance recovery loop, opting out of leadership, prune lock waits, the changed /api/stats and admin::state_counts shape, Python handler cancellation, and rollback.
• The README's documentation table links the new guide.

Evidence for the release

• Throughput. Three interleaved rounds against 0.6.16 on PostgreSQL 18 with synchronous_commit = on gave 19 to 21% more jobs per second at 4, 16 and 64 workers, and end-to-end p99 at 800 jobs/s fell from 31 ms to 24 ms (posted on fix(queue-storage): keep prune's checks off the exclusive lock and remove its lock-order cycles (#721) #723).
• Soak. 14 personas with 25,000 abandoned claims per killed process on pg17 and pg18: no deadlocks and no violation type that 0.6.16 does not also have, each at the same or a lower count (posted on fix(queue-storage): keep prune's checks off the exclusive lock and remove its lock-order cycles (#721) #723). Both builds fail that soak on promotion_stall, rescue_backlog_slow and claim_ring_stalled.

Known and unchanged from 0.6.16

• Ring prunes starve under claim load: claim_ready_runtime locks every slot child, so the 10 ms ACCESS EXCLUSIVE never wins #721 stays open: with a large backlog of abandoned claims, ring prune is blocked in most attempts.
• Enqueues to one lane wait behind each other for the length of the enqueue transaction, on the per-lane sequence advisory lock.
• With tens of thousands of claims held by one process and a short heartbeat staleness, rescue can close claims of a live process.

---

Generated by Claude Code

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

Run configuration

• Source mode: Auto
• Repository: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: Organization UI
• Review profile: CHILL
• Plan: Advanced
• Run ID: c24758af-bb61-471f-8048-ef3c15f8810e

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• Trigger review

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

• X
• Mastodon
• Reddit
• LinkedIn

[chatgpt-codex-connector]

Codex Review Summary: ✅ Completed

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-11-11T19:18:09.204228Z	d5f3e34	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: d5f3e34c39

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".