[kixelated]

Release moq-vaapi 0.1.1 with #5: the crate no longer forces log/release_max_level_debug, so a consumer such as moq can choose its own release log level.

Approved by the maintainer on 2026-11-04 (/quest-unblock). nix develop --command just ci passes on this head.

🤖 Generated with Claude Code

(Written by Claude Opus 5.5)

[coderabbitai]

No actionable comments were generated in the recent review.

Walkthrough

The moq-vaapi package version in Cargo.toml changes from 0.1.0 to 0.1.1.

Merge Risk: Minimal · up to 03afa

The version bump presents no identified merge-blocking risk and is ready to merge subject to normal release checks.

Pre-merge checks: 5

Check name	Status	Explanation
Title check		The title "chore: release moq-vaapi 0.1.1" matches the changeset, which bumps the moq-vaapi version in Cargo.toml from 0.1.0 to 0.1.1. It names the primary change, a release bump. It does not mention …
Description check		The description states that moq-vaapi 0.1.1 is released with the change from #5, which stops forcing log/release_max_level_debug. This relates directly to the Cargo.toml version bump. It …
Docstring Coverage		No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentat…
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.

Full details: Title check

Explanation

The title "chore: release moq-vaapi 0.1.1" matches the changeset, which bumps the moq-vaapi version in Cargo.toml from 0.1.0 to 0.1.1. It names the primary change, a release bump. It does not mention the underlying log-level change, but the summary says the change is a release and the scope is narrow, so the title is accurate and specific.

Full details: Description check

Explanation

The description states that moq-vaapi 0.1.1 is released with the change from #5, which stops forcing log/release_max_level_debug. This relates directly to the Cargo.toml version bump. It also gives approval and CI details. The description is on-topic and specific enough for the check.

Full details: Docstring Coverage

Explanation

No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentation-only edits and deletions within surviving functions are included; unchanged diff context and fully deleted functions are excluded. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)

Finishing Touches

Simplify code

• Commit to this branch
• Create a new PR

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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

Recent review info

Run configuration

• Source mode: Auto
• Repository: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: Organization UI
• Review profile: CHILL
• Plan: Advanced
• Run ID: e70a88f7-2723-4eb9-b6c5-04151095791a

Commits

Reviewing files that changed from the base of the PR and between 09ff001 and 03afaa8.

Files selected for processing: 1

• Cargo.toml

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.