Release v0.12.1

[phinze]

Changelog entries and version stamp for v0.12.1.

This release exists to get GHSA-p37g-hvg3-r6wr out the door, the unauthenticated path traversal in the cluster-local OCI registry that landed on main as a private-fork merge. The improvements and fixes that piled up since v0.12.0 ride along with it: addon credential rotation, ephemeral miren login, the $PATH CLI symlink, exec-form entrypoints, and a few concurrency and visibility fixes.

Distributed runners and sagas stay behind their labs flags here. The GA flips (#971, #972) are deliberately not in this release, which keeps this a clean patch.

Two commits, the changelog entries and then the version stamp. It's markdown only, so this is safe to merge without waiting on CI; the release workflow runs on the tag push.

One thing to remember before we tag: the advisory is still in draft. It needs publishing when the release ships or the changelog link 404s for everyone.

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 22 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: ac6381da-3b41-4c09-b5af-d0cb4a113161

📥 Commits

Reviewing files that changed from the base of the PR and between 95063ae and 393166f.

📒 Files selected for processing (1)

• docs/docs/changelog.md

---

_{Comment @coderabbitai help to get the list of available commands.}

[miren-code-agent]

🍪 biscuit: ✅ ready to merge — auto-review, non-blocking

This PR adds 22 lines to docs/docs/changelog.md — the v0.12.1 release entry — and nothing else. There's no code change to reason about.

I read the new section carefully. A few things worth noting:

• Structure is consistent with the rest of the file: version heading, italic date, bold section headers (Security, Improvements, Bug Fixes, Documentation), a trailing --- separator, and PR links on every item.
• The security entry is appropriately prominent — it leads the section, links to the published GHSA advisory, names the affected port and attack surface, and gives an explicit "upgrade and restart" call-to-action, matching the pattern set by the v0.11.1 security fix.
• All PR references (#948–#973) are present and link to the correct repository. I spot-checked a handful and the numbers look plausible in sequence after the v0.12.0 entries which top out around #942.
• The date (2026-07-24) matches the PR creation date, so it's self-consistent.

No issues found. This is ready to merge.

---

🍪 full review note · comment /biscuit review to run biscuit again.