Update Rust crate bzip2 to 0.6

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
bzip2	dependencies	minor	0.5 → 0.6

---

Release Notes

trifectatechfoundation/bzip2-rs (bzip2)

v0.6.1

Compare Source

v0.6.0

Compare Source

Highlights

This release switches to libbz2-rs-sys as the default bzip2 backend. It is written in rust, making it much easier to cross-compile. The new implementation is also more performant.

The rust implementation does not export C symbols by default. An explicit dependency on libbz2-rs-sys and setting the export-symbols feature flag will fix that if needed.

The bzip2-sys feature flag can be used to continue to use the C backend (either the system library of a C version built from source).

This is a breaking release, given that we want this update to be opt-in. We've used the occasion to perform an MSRV bump to 1.82.0. The libbz2-rs-sys crate has the bzip2-1.0.6 license. Arguably, that is the license that bzip2-sys should have had too, given that it is just a wrapper of the original bzip2 (and libbz2-rs-sys is a derivative work). You may need to allow this license when using cargo-deny.

What's Changed

• Release 0.6.0 by @​folkertdev in #​141

Full Changelog: trifectatechfoundation/bzip2-rs@v0.5.2...v0.6.0

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[greptile-apps]

PR author is in the excluded authors list.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: e9517ae908

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[chatgpt-codex-connector]

Restore cargo-deny license compatibility

Upgrading to bzip2 = "0.6" pulls in libbz2-rs-sys (visible in Cargo.lock), but the repository license policy currently allows only MIT/Apache/BSD/ISC/Unicode/Zlib (deny.toml:5-15), and CI always runs cargo-deny check --all-features (.github/workflows/ci.yml:359-374). Because libbz2-rs-sys uses the bzip2-1.0.6 license, this change will make the dependency-lint job fail on every PR/build until the allowlist or dependency choice is adjusted.

Useful? React with 👍 / 👎.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 0f71fb7f-4699-4704-8d31-b2c2dbea0da9

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch renovate/bzip2-0.x

✨ Simplify code

• Create PR with simplified code
• Commit simplified code in branch renovate/bzip2-0.x

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[kilo-code-bot]

Code Review Summary

Status: 1 Issue Found | Recommendation: Address before merge

Overview

Severity	Count
CRITICAL	0
WARNING	1
SUGGESTION	0

Fix these issues in Kilo Cloud

Issue Details (click to expand)

WARNING

File	Line	Issue
Cargo.lock	2217	libbz2-rs-sys is introduced by bzip2 0.6, but its bzip2-1.0.6 license is not in deny.toml, so the cargo-deny CI job will fail until the license policy or dependency feature choice is updated.

Other Observations (not in diff)

No additional issues found in unchanged code that cannot receive inline comments.

Files Reviewed (2 files)

• Cargo.lock - 1 issue
• crates/scanner-scheduler/Cargo.toml - 0 issues

---

_{Reviewed by gpt-5.5-2026-04-23 · 482,081 tokens}