Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Dec 10, 2023

This PR contains the following updates:

Package Type Update Change
mockall dev-dependencies minor 0.11 -> 0.13

Release Notes

asomers/mockall (mockall)

v0.13.1

Compare Source

Fixed
  • Suppress warnings about the #[expect] lint, new in Rust 1.81.0, in
    generated code.
    (#​619)

  • Suppress the #[clippy::ref_option] warning, new in Rust 1.83.0, in
    generated code.
    (#​618)

  • When mocking functions with a closure argument, but not using
    #[concretize], include any additional trait bounds in the trait object
    argument passed to .with and .returning.
    (#​606)

  • Fixed naming conflict when mocking multiple traits with same name but from
    different modules.
    (#​601)

v0.13.0

Compare Source

Added
  • Add the ability to use #[concretize] with methods that have an FnMut
    argument.
    (#​595)

  • Add the ability to mock methods that use #[auto_enum], from the
    auto_enums crate. But only for methods that use RPIT; Mockall can't yet
    handle syntax like -> Result<(), impl T>
    (#​590)

  • Add the ability to mock methods that use #[inline] or #[cold], and
    methods or traits that use #[must_use].
    (#​555)

Changed
  • Raised MSRV to 1.71.0 due to the C-unwind ABI.
    (#​585)

  • No longer poison a Context object's internal Mutex when panicing. This
    requires the "nightly" feature.
    (#​527)

Fixed
  • Fixed panicing within mocked extern "C" functions, for example due to
    unsatisfied expectations, with Rust 1.81.0 or newer.
    (#​585)

v0.12.1

Compare Source

Fixed
  • Fixed using #[mockall::concretize] on functions whose generic types contain
    trait bounds, yet are still object safe.
    (#​531)

  • Fixed mocking methods that use raw identifiers for their names. This was a
    regression in 0.12.0.
    (#​534)

v0.12.0

Compare Source

Added
  • Added #[mockall::concretize], which can be used to mock some generic
    methods that have non-'static generic parameters. It works by turning the
    generic arguments into trait objects for the expectation.
    (#​408)

  • When mocking functions with a non-default ABI (Like extern "C"), the mock
    function will now use the same ABI as the original. Name mangling will also
    be disabled, so the mock function will be callable from external code. For
    example, from C functions.
    (#​504)

Changed
  • Raised predicates, which is reexported, to 3.0.0. This may affect backwards
    compatibility for users who make use of predicates's "color" feature.
    (#​467)

  • Raised MSRV to 1.64.0 because predicates-core and predicates-tree did.
    (#​430)
    (#​467)

  • Better "No matching expectation found" messages on stable.
    (#​425)

Fixed
  • Fixed mocking non-private inherent methods that have attributes with syn
    version 2.0.9 and later.
    (#​486)

  • Suppress clippy::too_many_arguments warnings in the generated code. This
    is most useful when mocking static functions with exactly 7 arguments.
    (#​487)

  • Fixed unused_attributes warnings in the generated code when mocking FFI
    functions that use #[link_name].
    (#​503)

  • Fix a panic during Drop for static methods. One way to trigger it is by
    calling the method more times than is allowed by a .times() constraint.
    Another way would be to explicitly panic during the .returning method.
    (#​516)

Removed
  • Removed syntax deprecated since 0.9.0: using #[automock] directly on an
    extern "C" block, and using trait Foo {} syntax inside of mock!.
    (#​476)

  • Removed default features from predicates dependency. Reexports no longer
    include difflib, normalize-line-endings, regex and float-cmp features.
    (#​517)

v0.11.4

Compare Source

Fixed
  • Static methods' expectations will now be cleared during a panic.
    (#​443)

  • The checkpoint method now works correctly even after a panic due to too many
    method calls.
    (#​472)

  • Methods with unknown size type bounds can now be mocked.
    (#​421)

v0.11.3

Compare Source

Fixed
  • Methods with a where Self: ... clause will now be mocked like concrete
    methods, not generic ones. Among other effects, this prevents "unused method
    expect" warnings from the latest nightly compiler.
    (#​415)

Configuration

📅 Schedule: 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 is behind base branch, 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.

@renovate renovate bot changed the title Update Rust crate mockall to 0.12 Update Rust crate mockall to 0.12.1 May 1, 2024
@renovate renovate bot force-pushed the renovate/mockall-0.x branch 2 times, most recently from 4e825a9 to 0b26305 Compare May 5, 2024 10:18
@renovate renovate bot changed the title Update Rust crate mockall to 0.12.1 Update Rust crate mockall to 0.12 May 5, 2024
@renovate renovate bot force-pushed the renovate/mockall-0.x branch from 0b26305 to ca15f9b Compare July 22, 2024 02:45
@renovate renovate bot changed the title Update Rust crate mockall to 0.12 Update Rust crate mockall to 0.13 Jul 22, 2024
@renovate renovate bot force-pushed the renovate/mockall-0.x branch from ca15f9b to 8553d68 Compare August 10, 2025 13:35
@renovate renovate bot force-pushed the renovate/mockall-0.x branch from 8553d68 to a4c6271 Compare September 25, 2025 20:54
@renovate
Copy link
Contributor Author

renovate bot commented Sep 25, 2025

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: Cargo.lock
Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path Cargo.toml --package [email protected] --precise 0.13.1
error: failed to acquire package cache lock

Caused by:
  failed to open: /home/ubuntu/.cargo/.package-cache

Caused by:
  failed to create directory `/home/ubuntu/.cargo`

Caused by:
  File exists (os error 17)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants