Skip to content

Release v2.4.4#74

Merged
nmbrthirteen merged 1 commit into
mainfrom
release/v2.4.4
Jul 9, 2026
Merged

Release v2.4.4#74
nmbrthirteen merged 1 commit into
mainfrom
release/v2.4.4

Conversation

@nmbrthirteen

Copy link
Copy Markdown
Owner

Ships the field-report reliability fixes merged in #73.

What's in this release

Multi-segment clips. Web UI and export paths keep segments/keep_segments through batch, MCP, and re-render recipes. Boundary revert respects deliberate cuts instead of the outer span.

Suggest reliability. Long episodes use bucketed Claude suggestions with 900s timeouts. The UI resets from a stuck "suggesting" phase on failure.

Thumbnails. 4K face ROI normalization, tile-seam crop clamping, and empty-frame warnings in API + UI.

Loud failures. Export summary shows partial batch failures; thumbnail/error toasts use error styling.

Launcher diagnostics. podcli doctor SHA256-checks key backend files against the embedded bundle. podcli setup fails loudly when backend extract fails with no fallback.

Version

package.json 2.4.3 → 2.4.4, with cli/VERSION regenerated by go generate.

Made with Cursor

Bump package.json and regenerate cli/VERSION for the multi-segment export
and field-report reliability fixes merged in #73.
@coderabbitai

coderabbitai Bot commented Jul 9, 2026

Copy link
Copy Markdown

Warning

Review limit reached

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

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

Run ID: 0f48bc38-869e-4bfc-bd20-c105217a560a

📥 Commits

Reviewing files that changed from the base of the PR and between 5816e70 and a57bf42.

⛔ Files ignored due to path filters (1)
  • package-lock.json is excluded by !**/package-lock.json
📒 Files selected for processing (2)
  • cli/VERSION
  • package.json
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch release/v2.4.4

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

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

@nmbrthirteen nmbrthirteen merged commit 44b3c05 into main Jul 9, 2026
5 of 6 checks passed
@nmbrthirteen nmbrthirteen deleted the release/v2.4.4 branch July 9, 2026 18:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant