Release 2.7.0

[nmbrthirteen]

Rebased onto main, which now carries everything below. This is the last content before the tag.

package.json is the single source of truth; cli/VERSION is regenerated by go generate ./... in cli/. go test ./... passes with the refreshed version.

What 2.7.0 is

Four fixes measured against a published short (#148)

• --logo reached only the branded caption style; two gates dropped it everywhere else. A branded render is byte-identical after the fix.
• Subtle captions faded in and cut, flickering at every chunk boundary. They crossfade now, with no caption timing moved.
• An intro or outro was joined through 0.8s of black, eating 0.77s of a 6s + 2s join. --bookend-fade, defaulting to a cut.
• A guest lower third: --name-card, --name-card-sub. Only Remotion draws it, so --fast and an ASS fallback now refuse the combination instead of returning a clip without it.

Motion as a value (#149)

• {enter, exit, duration, feel} per part, replacing numbers hard-coded in each component. Every style ships what it already had; frame hashes identical across all four.

Templates for Pro, wherever you are signed in (#150)

• podcli templates and --template <name|id> on process and studio, resolved from the account. The primitives stay core, free and offline.
• studio and the MCP clip tools caught up on --logo, --name-card and --motion.
• --thumbnail-placement off separates drawing a thumbnail from welding it onto the video.

Audiograms for audio-only episodes (#153)

• An episode with no video renders as a waveform instead of not rendering.

The suggested moments get compared before one is chosen (#159)

• A long episode is searched in three to six timeline buckets, each its own call, and their scores were never comparable. One transcript-free pass now ranks the whole pool. Ties at the cut line used to be broken by list position, which favoured the opening minutes.
• A Pro workspace's published-clip history moves from discovery, where it was fetched once per bucket, to the ranking pass, where retention data actually answers the question. It also reaches local Claude Code and Codex now, not only the cloud backend.
• podcli process and the studio go through one selection path and ship the same clips from the same episode.

Dependencies

• numpy (Update numpy requirement from >=2.5.1 to >=2.5.2 in /backend #154), @types/node (Bump @types/node from 22.19.12 to 26.2.0 #158), the npm minor/patch group (Bump the npm-minor-patch group with 6 updates #155), zod 4 (Bump zod from 3.25.76 to 4.4.3 #156).
• zod 4 drops additionalProperties: false from the MCP tool schemas and changes zod's own error strings. Runtime behaviour is unchanged and nothing in this repo reads either, but an external MCP client validating against the advertised schema may notice.
• vite 8 (Bump vite from 5.4.21 to 8.2.1 #157) and @vitejs/plugin-react 6 (Bump @vitejs/plugin-react from 4.7.0 to 6.0.5 #143) are held: they deadlock on each other and on Remotion's babel pin. One replacement PR follows the release.

After the tag

The cloud worker still pins PODCLI_VERSION: 2.6.0. Bumping it is what carries all of this to podcli.com, and it should happen only once the release assets exist.

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 30 minutes

Limit details: You’ve used the included review currently available.

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

Wait for the limit to reset, then comment @coderabbitai review or push new commits to the PR.

An organization admin can change what happens after included review limits in Billing.

How do review limits work?

CodeRabbit enforces per-developer PR review limits within each organization.

For paid Pro and Pro+ reviews, CodeRabbit uses a developer's included PR review attempts over the past 7 days to set the current hourly allowance. At typical activity levels, the full plan allowance applies. Higher sustained activity can lower the allowance until earlier attempts leave the 7-day window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: a13977c9-3e0a-4871-91ab-71dae623b35d

📥 Commits

Reviewing files that changed from the base of the PR and between 8c917c1 and 70dd6c5.

📒 Files selected for processing (2)

• cli/VERSION
• package.json

---

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