chore(main): release 0.24.0

[mlorentedev]

🤖 I have created a release beep boop

0.24.0 (2026-06-26)

Features

• ci: lint bats @test names to stop silent-skipped tests (#619) (614f4ec)
• secrets: add BWWriter (bw write seam, read-modify-write) (#620) (f936649)
• secrets: add SetBackendBW registry mutation primitive (#617) (c6f659f)

---

This PR was generated with Release Please. See documentation.

[coderabbitai]

Warning

Review limit reached

@mlorentedev, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 1 minute and 12 seconds. Learn how PR review limits work.

To continue reviewing without waiting, enable usage-based billing in the billing tab.

⌛ How to resolve this issue?

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 credits.

🚦 How do rate 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 see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: d2bdc1c2-20e1-49e5-bde4-2640edd89afd

📥 Commits

Reviewing files that changed from the base of the PR and between c8fd0e1 and 11dc0f1.

📒 Files selected for processing (3)

• .release-please-manifest.json
• CHANGELOG.md
• versions.conf

📝 Walkthrough

Walkthrough

The PR updates the release metadata for version 0.24.0, adds the matching changelog entry, and bumps the pinned DOTF_VERSION value.

Changes

Release metadata update

Layer / File(s)	Summary
Version bump and release note .release-please-manifest.json, versions.conf, CHANGELOG.md	The root release version moves to 0.24.0, DOTF_VERSION is pinned to 0.24.0, and CHANGELOG.md adds the 0.24.0 features entry for SetBackendBW.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• mlorentedev/dotfiles#614: Updates the same release/version metadata files for a prior 0.23.0 release bump.
• mlorentedev/dotfiles#599: Also advances .release-please-manifest.json, CHANGELOG.md, and versions.conf together.
• mlorentedev/dotfiles#590: Shares the same release-bump pattern and includes a secrets changelog entry.

Poem

I hop through the changelog, bright and neat,
0.24.0 pats my fluffy feet.
The version pin is snug, the release notes sing,
In secret burrows, new registry springs.
Hoppy days! 🐰

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description is a release note, but it omits the required Summary, SDD checklist, and Test plan sections from the repo template.	Add the template sections with the required bullets/checklists, and include SDD skip rationale only if the skip-sdd label applies.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely identifies the release version being merged.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch release-please--branches--main

---

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

[mlorentedev]

🤖 Created releases:

• v0.24.0

🌻