chore(release): v0.107.0

[mabry1985]

Version bump 0.106.0 → 0.107.0 + rolled changelog for the release (10 PRs merged since v0.106.0).

What ships in v0.107.0

Added

• Versioned file artifacts — save_file_artifact + a file artifact kind (sidecar blobs, diffable text preview, image thumbnails, download card). ADR 0092 D2 (feat(artifact): versioned file/download artifacts — save_file_artifact (ADR 0092 D2) #2126)
• Document-generation stack in the desktop bundle, on by default — cowork's docx/xlsx/pptx/pdf skills work on desktop; protobanana's pillow refusal gone. ADR 0092 D1 (feat(desktop): bundle the document-generation stack (ADR 0092 D1) #2123)
• Fleet agents accept operator inputs + secrets at create time — peek_bundle/lock expose bundle inputs+secrets, backend seeds them, new-agent input picker + preview, Settings ▸ Secrets behind secrets-panel flag (feat: console: gate Settings ▸ Secrets behind secrets-panel dev flag #2121/feat: Enrich peek_bundle + lock to expose bundle mcp inputs and secrets #2122/feat: Backend — accept operator inputs + secrets at fleet create time #2125/feat: Frontend — input picker in NewAgentPanel + preview dialog enrichment #2127)
• Deterministic persona-drift detection (feat: Deterministic Persona Drift Detection (#1986) - V2 #2116)
• Chat tab context menu — Close Others / Left / Right (feat: Add Close Others/Left/Right to chat tab context menu #2112)

Fixed

• Archetype-catalog bundling — cowork/archetypes now in the desktop + pip new-agent picker (fix(build): bundle archetype-catalog.json into the wheel + desktop sidecar #2115)
• PyPI publishes on the tag push, not the derivative release event (fix(ci): publish to PyPI on the tag push, not the derivative release event #2113)

Release mechanics

Prepared locally (equivalent to prepare-release.yml): version bump, CHANGELOG.md [Unreleased] backfilled for the feature PRs that lacked entries then rolled to [0.107.0], marketing changelog.json scaffolded + polished (no overclaims — every bullet is a shipped change), uv.lock project-version line only (surgical, to avoid uv 0.11.13-vs-pinned-0.11.29 marker drift).

After merge: tag v0.107.0 → release.yml (Docker + GitHub Release + Discord) + publish.yml (PyPI); then dispatch desktop-build.yml -f tag=v0.107.0 for the desktop app.

🤖 Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 45 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: ASSERTIVE

Plan: Pro

Run ID: 56a2bcdf-3df6-435b-b54c-7a893bd993b3

📥 Commits

Reviewing files that changed from the base of the PR and between 0d7cda9 and 4f050b3.

⛔ Files ignored due to path filters (2)

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

📒 Files selected for processing (2)

• pyproject.toml
• sites/marketing/data/changelog.json

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch release/v0.107.0

---

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

[protoreview]

QA panel review — PASS

code-review-structural · head 4f050b3e8c21 · formal

[review-synthesizer completed: workflow code-review-structural:report]

Prose Brief

Overall risk: None — this is a pure release chore bumping the version from 0.106.1 to 0.107.0 across four metadata files (CITATION.cff, CHANGELOG.md, Cargo.toml, pyproject.toml). No production code, logic, or configuration semantics change.

Fix-first item: Nothing to fix. The diff is correct on its face: every version string is updated consistently.

Panel disagreement: None. The panel (LLM finders + protoPatch structural pass) produced no findings that survived dedup, and the verifier confirmed that the protoPatch flags were all on pre-existing lines untouched by the diff.

What verification changed: Nothing to change — the input findings array was already empty, and the verifier confirmed this matches the diff.

Gaps: The structural pass (protoPatch) flagged stale pyproject.toml dependency pins, but those lines are outside the diff hunk and correctly excluded. A possible missing link-reference footer for [0.107.0] in CHANGELOG.md was noted in the brief; it's an editorial concern (not a code defect) and was never filed as a formal finding. No coverage gaps — every changed file was read.

[]

[protoreview]

Promoting the PASS verdict for head 4f050b3e8c21: all checks terminal-green, zero unresolved review threads. (approve-on-green)