chore(deps): update dependency mockolate to v3#5801
Conversation
thomhurst
added
dependencies
thomhurst
had a problem deploying
to
Pull Requests
GitHub Actions
Failure
![claude[bot]](https://avatars.githubusercontent.com/in/1236702?s=60&v=4){kind=small}
There was a problem hiding this comment.
Dependency Update Review: Mockolate 2.4.0 → 3.0.0
This is a Renovate-generated major version bump. Here's my analysis:
Scope & Impact
Good news: Mockolate is only used in TUnit.Mocks.Benchmarks — not in any production, test infrastructure, or shipped packages. The blast radius of this upgrade is limited to benchmark comparisons.
Breaking Changes Worth Noting
The v3.0.0 release contains numerous breaking changes (marked with ! in the changelog), several of which directly touch APIs used in the benchmark code:
-
feat!: update CreateMock overloads to accept typed constructor arguments— The benchmarks callICalculatorService.CreateMock()(no args). Per the companion commitfeat!: omit constructor parameters overloads for interfaces and types with only parameterless constructors, parameterless overloads are preserved for interfaces, so this should remain safe. -
refactor!: introduce ITypedParameter and ITypedMethodMatch interfaces— The benchmarks cast toMockolate.Mock.IMockForICalculatorServiceand call into the Setup API. If the interface shape changed, the source-generated mock class forICalculatorServicewill need to be regenerated — which happens automatically at build time via the source generator. -
refactor!: use Callbacks<T> class/perf!: reduce allocations in setup/interaction/verify— Internal-only, shouldn't affect benchmark call sites, but worth confirming the setup chains inInvocationBenchmarks.csstill compile.
No Issues Found
The change itself is minimal (one line in Directory.Packages.props), and the dependency is isolated to a benchmarks project. All the v3.0.0 breaking changes align with the API surface as used by TUnit — primarily source-generated mocks of interfaces with parameterless constructors, and standard setup/invocation chains. The upgrade should compile cleanly; the source generator will regenerate the mock wrapper at build time to match the new interfaces.
The performance-focused changes in v3.0.0 (avoiding boxing, removing closures, typed storage) are actually a net positive for a benchmarks project — the comparison numbers will be more representative of Mockolate's real-world performance.
Verdict: Safe to merge. The auto-merge already enabled on this PR is appropriate.
Up to standards ✅🟢 Issues
|
| Metric | Results |
|---|---|
| Complexity | 0 |
NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.
2 participants
This PR contains the following updates:
2.4.0→3.0.0Release Notes
aweXpect/Mockolate (Mockolate)
v3.0.0What's Changed
DebuggerNonUserCodeattribute in DEBUG mode by @vbreuss in #636Callbacks<T>class by @vbreuss in #648ContainsandSequenceEqualsby @vbreuss in #650InvocationCounttoNin benchmarks by @vbreuss in #661"in exception message by @vbreuss in #711MockRegistrytests by @vbreuss in #729MockRegistry.Interactionsedge case tests by @vbreuss in #731MockRegistryby @vbreuss in #732It.*by @vbreuss in #736Full Changelog: Testably/Mockolate@v2.4.0...v3.0.0
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Enabled.
♻ 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.
This PR has been generated by Mend Renovate.