build(deps): bump tabuna/breadcrumbs from 4.3.0 to 5.0.0

[dependabot]

Bumps tabuna/breadcrumbs from 4.3.0 to 5.0.0.

Release notes

Sourced from tabuna/breadcrumbs's releases.

5.0.0

✨ New Features

• Named parameter resolution for breadcrumbs Breadcrumb closures now support resolving parameters by name via Laravel’s container (app()->call()), removing dependency on positional arguments.

  ->breadcrumbs(fn (Trail $trail, Post $post) =>
      $trail->push($post->title, route('post', $post->id))
  );

• Note parameters resolved by name Internal improvements ensure note parameters are consistently resolved using named bindings.

🧪 Testing & Quality Improvements

• 100% Mutation Testing Coverage (MSI) achieved Significant improvements to test suite robustness and reliability.

• Added test coverage for:

  • Blade component registration
  • Macro overwrite protection (hasMacro guard)
  • Fluent return behavior of breadcrumbs() macro
  • Breadcrumbs::has() with explicit route names
  • Exception handling in Registrar::get() for missing definitions
  • Isolation of generate() from current route parameters
  • Cleanup behavior in BreadcrumbsMiddleware::forgetParameter

• Refactored:

  • Trail::call() visibility changed from protected → private to enforce stricter encapsulation

Full Changelog: tabuna/breadcrumbs@4.4.0...5.0.0

4.4.0

What's Changed

• Test breadcrumbs overwrite with null by @​danielh-official in tabuna/breadcrumbs#52
• Laravel 13.x Compatibility by @​laravel-shift in tabuna/breadcrumbs#54

New Contributors

• @​danielh-official made their first contribution in tabuna/breadcrumbs#52

Full Changelog: tabuna/breadcrumbs@4.3.0...4.4.0

Commits

• cba6a65 Added note parameters are resolved by name
• 7498dcc Improve mutation test coverage to 100% MSI
• aa63b8d Use named parameters in breadcrumb closures via app()->call()
• 120322c Laravel 13.x Compatibility (#54)
• a6c728e Fixed code style
• 33a6d64 refs #52 Changed the route name check to a chain.
• 91baeb8 Test breadcrumbs overwrite with null (#52)
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)