build(deps): bump mockall from 0.13.1 to 0.14.0

[dependabot]

Bumps mockall from 0.13.1 to 0.14.0.

Changelog

Sourced from mockall's changelog.

[ 0.14.0 ] - 2025-11-22

Added

• Allow mocking structs and traits with const generics. (#649)

• Compatibility with the #[trait_variant::make] macro. (#640)

• Allow Expectations with a non-exact call count to be used in Sequences. (#660)

Changed

• The MSRV is now Rust 1.77.0. (#650)

Fixed

• No longer poison a static mock method's internal Mutex when panicing, even when using a stable Rust compiler. Also, no longer poison it even if there is no Context object. For example, if the user never set an Expectation at all. (#650)

• Suppress single-use-lifetimes lints in the generated code, for cases where the orginal code wouldn't have triggered the warning. (#627)

• Fix mocking foreign functions with a variadic argument and no pattern, for example fn foo(...) as opposed to fn bar(x: ...). That worked in prior versions of Mockall only until Rust 1.93.0, which made such arguments illegal for Rust functions. (#673)

• Fully qualify Send and Sync traits in generated code, allowing structs named Send or Sync to be in scope without conflicts. (#672)

Commits

• 4401e5a chore: Release
• 73e6c8b Merge pull request #649 from jonatanzeidler/f.const-generics
• c8920ba Add a CHANGELOG entry for PR #649
• dcbad06 Actually use a struct in the const_generic_struct_with_static_method test
• e9d52fb Don't create () fields for each const generic paramters
• b734232 Allow const generics in automock
• b2133c9 Allow methods on mocks to be called with a range of times in a Sequence (#660)
• ae37861 Fully qualify Send and Sync marker traits (#672)
• 695e55a Fix mocking foreign functions with a variadic argument and no pattern (#673)
• d50aa1d improve error message (#668)
• Additional commits viewable 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 merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @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)

Summary by CodeRabbit

• Chores
  • Updated development dependencies to maintain tooling compatibility.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

The mockall dev-dependency version is bumped from 0.13 to 0.14 in Cargo.toml. This is a routine dependency update with no functional logic changes to the codebase.

Changes

Cohort / File(s)	Summary
Dependency Version Bump Cargo.toml	Updated dev-dependency mockall from version 0.13 to 0.14

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

• No code logic changes; purely a dependency version update
• No breaking changes anticipated based on standard semantic versioning for a patch-level bump

Possibly related PRs

• build(deps): bump mockall from 0.12.1 to 0.13.1 #285: Previous mockall version bump from 0.12 to 0.13, continuing the pattern of keeping the mocking library up-to-date.

Suggested reviewers

• elmattic
• akaladarshi
• hanabi1224

Poem

🐰 Hop, hop, the versions align,
Mockall climbs to 0.14 so fine!
With gentle bumps and tests so bright,
Dependencies flow, all feels right! ✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately and concisely describes the main change: bumping mockall from v0.13.1 to v0.14.0, which directly matches the changeset.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch dependabot/cargo/mockall-0.14.0

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 728c549 and 2821e89.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (1)

• Cargo.toml (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (5)

• GitHub Check: E2E Claim Token API CORS Tests
• GitHub Check: E2E Browser Tests
• GitHub Check: E2E API Tests
• GitHub Check: deploy
• GitHub Check: codedov

🔇 Additional comments (2)

Cargo.toml (2)

57-57: The key breaking change in mockall v0.14 is that mock checkpoint methods will no longer check static expectations, which may impact tests. Additionally, predicates was bumped to v3.0.0, which may also introduce breaking changes.

Let me verify if the codebase's tests use these affected features:

Let me verify if the codebase uses the affected APIs in mockall and predicates:

MSRV requirement met; verify test code compatibility with mockall v0.14 breaking changes.

The project's Rust toolchain (1.91.0) meets mockall v0.14.0's MSRV requirement of 1.77.0. However, mockall v0.14 introduces a breaking change where mock objects' checkpoint methods will no longer check static expectations. Additionally, predicates was bumped to v3.0.0, which has trait-level API changes.

Verify that your test code doesn't rely on checkpoint methods verifying static method expectations, and confirm compatibility with any predicates v2-specific APIs now that predicates has been upgraded to v3.

---

57-57: I'll search for the official mockall v0.14.0 changelog to identify any breaking changes.

I need to search more specifically for the Rust mockall crate v0.14.0 release notes.

Let me search directly for mockall releases on GitHub:

Based on my search results, I can now provide a definitive rewritten review comment:

The specified mockall v0.14.0 does not appear to exist; latest available version is v0.13.1.

The version constraint mockall = "0.14" in Cargo.toml would fail to resolve during dependency resolution, as mockall v0.13.1 is the latest available version. Across multiple queries of official registries and release pages, no v0.14.0 release was found.

If the intent is to update to the latest mockall, change the dependency to mockall = "0.13" or mockall = "0.13.1". Otherwise, verify whether the version specification is correct before merging.

Likely an incorrect or invalid review comment.

---

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

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 41.11%. Comparing base (728c549) to head (2821e89).

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #358   +/-   ##
=======================================
  Coverage   41.11%   41.11%           
=======================================
  Files          40       40           
  Lines        2668     2668           
=======================================
  Hits         1097     1097           
  Misses       1571     1571           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.