chore: release v0.8.0

[github-actions]

🤖 New release

• libmagic-rs: 0.7.0 -> 0.8.0 (⚠ API breaking changes)

⚠ libmagic-rs breaking changes

--- failure enum_struct_variant_field_added: pub enum struct variant field added ---

Description:
An enum's exhaustive struct variant has a new field, which has to be included when constructing or matching on this variant.
        ref: https://doc.rust-lang.org/reference/attributes/type_system.html#the-non_exhaustive-attribute
       impl: https://github.com/obi1kenobi/cargo-semver-checks/tree/v0.47.0/src/lints/enum_struct_variant_field_added.ron

Failed in:
  field flags of variant TypeKind::Search in /tmp/.tmp1Dshn1/libmagic-rs/src/parser/ast.rs:679
  field flags of variant TypeKind::Search in /tmp/.tmp1Dshn1/libmagic-rs/src/parser/ast.rs:679
  field flags of variant TypeKind::Search in /tmp/.tmp1Dshn1/libmagic-rs/src/parser/ast.rs:679

--- failure function_parameter_count_changed: pub fn parameter count changed ---

Description:
A publicly-visible function now takes a different number of parameters.
        ref: https://doc.rust-lang.org/cargo/reference/semver.html#fn-change-arity
       impl: https://github.com/obi1kenobi/cargo-semver-checks/tree/v0.47.0/src/lints/function_parameter_count_changed.ron

Failed in:
  libmagic_rs::evaluator::types::read_search now takes 5 parameters instead of 4, in /tmp/.tmp1Dshn1/libmagic-rs/src/evaluator/types/search.rs:150

Changelog

[0.8.0] - 2026-05-28

Features

• Implement search-type flag semantics (closes Implement search-type flag semantics (/s start-anchor, /b binary, etc.) #235) (#297)

Documentation

• third_party: Update NOTICE.md for clarity and accuracy

---

This PR was generated with release-plz.

[mergify]

Merge Protections

Your pull request matches the following merge protections and will not be merged until they are valid.

🟢 Do not merge outdated PRs

Wonderful, this rule succeeded.

Make sure PRs are within 10 commits of the base branch before merging

• #commits-behind <= 10

[dosubot]

Related Knowledge

1 document with suggested updates is ready for review.

libMagic-rs

migration /libmagic-rs/blob/main/docs/src/migration.md — ⏳ Awaiting Merge

^{How did I do? Any feedback?}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[unclesp1d3r]

@Mergifyio queue

[mergify]

Merge Queue Status

• ✅ Entered queue — 2026-05-28 12:50 UTC · Rule: default
• ✅ Checks started · on draft merge queue: embarking main (89fa133) and #299 together #303
• 🚫 Left the queue — 2026-05-28 13:06 UTC · at 79fa48bacd9b81efd8a4e21af129e6dd77d5aef7

This pull request spent 16 minutes 4 seconds in the queue, with no time running CI.

Waiting for

• check-success = coverage
• check-success = quality
• check-success = test
• check-success = test-cross-platform (macos-latest, macOS)
• check-success = test-cross-platform (ubuntu-22.04, Linux)
• check-success = test-cross-platform (ubuntu-latest, Linux)
• check-success = test-cross-platform (windows-latest, Windows)
• any of: [🛡 GitHub repository ruleset rule main]
  • check-neutral = DCO
  • check-skipped = DCO
  • check-success = DCO
• any of: [🛡 GitHub repository ruleset rule main]
  • check-neutral = Mergify Merge Protections
  • check-skipped = Mergify Merge Protections
  • check-success = Mergify Merge Protections

All conditions

• check-success = coverage
• check-success = quality
• check-success = test
• check-success = test-cross-platform (macos-latest, macOS)
• check-success = test-cross-platform (ubuntu-22.04, Linux)
• check-success = test-cross-platform (ubuntu-latest, Linux)
• check-success = test-cross-platform (windows-latest, Windows)
• any of [🛡 GitHub repository ruleset rule main]:
  • check-neutral = DCO
  • check-skipped = DCO
  • check-success = DCO
• any of [🛡 GitHub repository ruleset rule main]:
  • check-neutral = Mergify Merge Protections
  • check-skipped = Mergify Merge Protections
  • check-success = Mergify Merge Protections
• all of [🛡 Merge Protections rule Do not merge outdated PRs]:
  • #commits-behind <= 10
    • chore: release v0.8.0 #299

Reason

Pull request #299 has been dequeued

due to: files are inaccessible

Hint

You should look at the reason for the failure and decide if the pull request needs to be fixed or if you want to requeue it.
If you do update this pull request, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio queue comment.

[unclesp1d3r]

@Mergifyio queue

[mergify]

queue

☑️ Command queue ignored because it is already running from a previous command.