chore(release): 0.0.15

[ulmentflam]

Version bump for v0.0.15, plus a .gitignore fix the bump itself exposed.

Versions

Nine files bumped together — _version.py plus the eight pyproject.tomls. That is what test_version_consistency.py has enforced since 0.0.14, when the two silently disagreed for two releases.

iCloud conflict-copy ignores

Not cosmetic. Staging the bump swept up AGENTS 3.md, Makefile 2, and .gitignore 2 — conflict copies the existing rules missed on two counts:

• the list enumerated extensions ( 2.md, 2.py, …), so anything extension-less slipped through — and the files Finder collides on most in this repo have no extension
• it stopped at 2, while the counter keeps climbing

Matching the <digits> suffix covers every shape. Verified against AGENTS 3.md, Makefile 2, .gitignore 2, .venv 2, foo 10.toml, and demo 2.gif, and confirmed no real file is caught.

The tradeoff: a deliberately-named Chapter 2.md would also be ignored. Noted inline, with the git add -f escape.

The four copies already on disk are deleted. Each was checked first — AGENTS 2.md and CLAUDE 2.md were byte-identical to their originals, .gitignore 2 was the pre-edit revision, .venv 2 an empty directory.

Verification

1563 tests pass. nightly verify clean on all five checks.

🤖 Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

@ulmentflam, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 37 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: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: bfa57bee-d7d1-4985-b96b-5a19208d17d2

📥 Commits

Reviewing files that changed from the base of the PR and between 95a5a6a and 55e20a4.

⛔ Files ignored due to path filters (1)

• uv.lock is excluded by !**/*.lock

📒 Files selected for processing (10)

• .gitignore
• packages/nightly-core/pyproject.toml
• packages/nightly-core/src/nightly_core/_version.py
• packages/nightly-host-antigravity/pyproject.toml
• packages/nightly-host-claude/pyproject.toml
• packages/nightly-host-codex/pyproject.toml
• packages/nightly-host-cursor/pyproject.toml
• packages/nightly-host-gemini/pyproject.toml
• packages/nightly-host-opencode/pyproject.toml
• pyproject.toml

---

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

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