chore: release v1.0.1

[nerdCopter]

AI Generated pull-request

Summary

Version bump to 1.0.1, packaging all changes merged to master since the 1.0.0 release:

Added

• Firmware vendor transition detection (warns and corrects output filename prefixes when a BBL/BFL file spans multiple firmware vendors, e.g. Betaflight sessions before a reflash to EmuFlight)
• QUIC_ (Quicksilver) fork exemption from false-positive vendor-transition renames
• sanitize_base_name_override() to prevent path traversal via the public library API
• vendor_name_for_prefix() as single source of truth for prefix-to-display-name mapping

Fixed

• Universal gyro activity filtering (fix: Universal gyro activity filtering to skip ground test logs #40): ground-test logs without duration metadata no longer produce "Data Unavailable" output; switched to scale-independent gyro range detection (MIN_GYRO_RANGE = 500.0), lowered fallback frame threshold (FALLBACK_MIN_FRAMES = 7,500), fixed NaN propagation in calculate_range()
• Release workflow binary version check (was comparing against a string missing the bbl_parser prefix)
• time crate RUSTSEC-2026-0009 (DoS via stack exhaustion, CVSS 6.8) via update to 0.3.53

Changed

• Release artifacts now packaged as ZIP archives instead of loose binaries
• Broad cargo update dependency sweep (clap, serde, regex, syn, libc, and others)
• Build tooling: vergen 8 → vergen-gitcl 10 (env var names unchanged, no downstream code changes)

Full details in CHANGELOG.md.

Test plan

• cargo build --release and cargo test --release pass (19 unit/integration tests + 3 doc-tests)
• bbl_parser --version reports 1.0.1

[coderabbitai]

Warning

Review limit reached

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

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

Plan: Pro

Run ID: 600050cb-1eff-43b1-ad05-1a4e888ad47b

📥 Commits

Reviewing files that changed from the base of the PR and between 9e93c7c and e2837d6.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (2)

• CHANGELOG.md
• Cargo.toml

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch release/v1.0.1

---

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