Skip to content

Bump Moq from 4.11.0 to 4.20.72#13

Open
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/nuget/src/Test/main/Moq-4.20.72
Open

Bump Moq from 4.11.0 to 4.20.72#13
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/nuget/src/Test/main/Moq-4.20.72

Conversation

@dependabot
Copy link
Copy Markdown

@dependabot dependabot bot commented on behalf of github Apr 7, 2026

Updated Moq from 4.11.0 to 4.20.72.

Release notes

Sourced from Moq's releases.

4.20.72

What's Changed

🔨 Other

Full Changelog: devlooped/moq@v4.20.71...v4.20.72

4.20.71

What's Changed

🔨 Other

New Contributors

Full Changelog: devlooped/moq@v4.20.70...v4.20.71

4.20.70

What's Changed

🔨 Other

New Contributors

Full Changelog: devlooped/moq@v4.20.69...v4.20.70

4.20.69

Let's make it more memorable when Moq became "safe" again.

What's Changed

4.20.2

What's Changed

🐛 Fixed bugs

NOTE: in addition, there were potential privacy issues raised with regards to the SHA256 hashing of
user' email to check for sponsorship, so it won't be coming back until that's properly addressed

Full Changelog: moq/moq.spikes@v4.20.1...v4.20.2

4.20.1

What's Changed

✨ Implemented enhancements

  • Add Sponsor button to package readme 💜

Full Changelog: moq/moq.spikes@v4.20.0...v4.20.1

4.20.0

What's Changed

✨ Implemented enhancements

🔨 Other

New Contributors

Full Changelog: moq/moq.spikes@v4.18.4...v4.20.0

4.20.0-rc

What's Changed

🔨 Other

Full Changelog: moq/moq.spikes@v4.20.0-beta...v4.20.0-rc

4.20.0-beta

What's Changed

✨ Implemented enhancements

🔨 Other

New Contributors

Full Changelog: moq/moq.spikes@v4.18.4...v4.20.0-beta

4.20.0-alpha

What's Changed

✨ Implemented enhancements

🔨 Other

New Contributors

Full Changelog: moq/moq.spikes@v4.18.4...v4.20.0-alpha

4.18.4

Changed

  • Update package reference to Castle.Core (DynamicProxy) from version 5.1.0 to 5.1.1 (@​stakx, #​1317)

4.18.3

Fixed

  • SetupAllProperties crashes when invoked on a Mock<T> subclass (@​mo-russo, #​1278)

4.18.2

Changed

  • Update package reference to Castle.Core (DynamicProxy) from version 5.0.0 to 5.1.0 (@​stakx, #​1275)
  • Removed dependency on System.Threading.Tasks.Extensions for netstandard2.1 and net6.0 (@​tibel, #​1274)

Fixed

  • "Expression is not an event add" when using .Raises() with redeclared event (@​howcheng, #​1175)
  • MissingMethodException when mocking interface with sealed default implementation (@​pjquirk, #​1209)
  • Throws TypeLoadException on mock when a record has a base record on .NET 6 (@​tgrieger-sf, #​1273)

4.18.1

Fixed

  • Regression with lazy evaluation of It.Is predicates in setup expressions after updating from 4.13.1 to 4.16.1 (@​b3go, #​1217)
  • Regression with SetupProperty where Moq fails to match a property accessor implementation against its definition in an interface (@​Naxemar, #​1248)
  • Difference in behavior when mocking async method using .Result vs without (@​cyungmann, #​1253)

4.18.0

New major version of DynamicProxy (you may get better performance!), so please update with care.

Changed

  • Update package reference to Castle.Core (DynamicProxy) from version 4.4.1 to 5.0.0 (@​stakx, #​1257)
  • Adjusted our target frameworks to match DynamicProxy's (see their discussion about which frameworks to target):
    • minimum .NET Framework version raised from net45 to net462
    • additional net6.0 TFM

Fixed

  • Can't set up "private protected" properties (@​RobSiklos, #​1170)
  • Using [...] an old version of System.Net.Http which is vulnerable to "DoS", "Spoofing", "Privilege Escalation", "Authentication Bypass" and "Information Exposure" (@​sidseter, #​1219)
  • Failure when invoking a method with by-ref parameter & mockable return type on a mock with CallBase and DefaultValue.Mock configured (@​IanKemp, #​1249)

4.17.2

Fixed

  • Regression: Property stubs not working on sub mock (@​aaronburro, #​1240)

4.17.1

Added

  • SetupSet, VerifySet methods for mock.Protected().As<>() (@​tonyhallett, #​1165)
  • New Throws method overloads that allow specifying a function with or without parameters, to provide an exception, for example .Throws(() => new InvalidOperationException())
    and Setup(x => x.GetFooAsync(It.IsAny<string>()).Result).Throws((string s) => new InvalidOperationException(s)). (@​adam-knights, #​1191)

Changed

  • Update package reference to Castle.Core (DynamicProxy) from version 4.4.0 to 4.4.1 (@​stakx, #​1233)

Fixed

  • The guard against unmatchable matchers (added in #​900) was too strict; relaxed it to enable an alternative user-code shorthand _ for It.IsAny<>() (@​adamfk, #​1199)
  • mock.Protected() setup methods fail when argument is of type Expression (@​tonyhallett, #​1189)
  • Parameter is invalid in Protected().SetupSet() ... VerifySet (@​tonyhallett, #​1186)
  • Virtual properties and automocking not working for mock.Protected().As<>() (@​tonyhallett, #​1185)
  • Issue mocking VB.NET class with overloaded property/indexer in base class (@​myurashchyk, #​1153)
  • Equivalent arrays don't test equal when returned from a method, making Verify fail when it should not (@​evilc0, #​1225)
  • Property setups are ignored on mocks instantiated using Mock.Of (@​stakx, #​1066)
  • SetupAllProperties causes mocks to become race-prone (@​estrizhok, #​1231)

4.16.1

Added

  • CallBase can now be used with interface methods that have a default interface implementation. It will call the most specific override. (@​stakx, #​1130)

Changed

  • Improved error message formatting of It.Is lambda expressions that capture local variables. (@​bfriesen, #​1140)

Fixed

  • AmbiguousMatchException raised when interface has property indexer besides property in VB. (@​mujdatdinc, #​1129)
  • Interface default methods are ignored (@​hahn-kev, #​972)
  • Callback validation too strict when setting up a task's .Result property (@​stakx, #​1132)
  • setup.Returns(InvocationFunc) wraps thrown exceptions in TargetInvocationException (@​stakx, #​1141)

4.16.0

Added

  • Ability to directly set up the .Result of tasks and value tasks, which makes setup expressions more uniform by rendering dedicated async verbs like .ReturnsAsync, .ThrowsAsync, etc. unnecessary:

    -mock.Setup(x => x.GetFooAsync()).ReturnsAsync(foo)
+mock.Setup(x => x.GetFooAsync().Result).Returns(foo)

    This is useful in places where there currently aren't any such async verbs at all:

    -Mock.Of<X>(x => x.GetFooAsync() == Task.FromResult(foo))
+Mock.Of<X>(x => x.GetFooAsync().Result == foo)

    This also allows recursive setups / method chaining across async calls inside a single setup expression:

    -mock.Setup(x => x.GetFooAsync()).ReturnsAsync(Mock.Of<IFoo>(f => f.Bar == bar))
+mock.Setup(x => x.GetFooAsync().Result.Bar).Returns(bar)

    or, with only Mock.Of:

    -Mock.Of<X>(x => x.GetFooAsync() == Task.FromResult(Mock.Of<IFoo>(f => f.Bar == bar)))
+Mock.Of<X>(x => x.GetFooAsync().Result.Bar == bar)

    This should work in all principal setup methods (Mock.Of, mock.Setup…, mock.Verify…). Support in mock.Protected() and for custom awaitable types may be added in the future. (@​stakx, #​1126)

Changed

  • Attempts to mark conditionals setup as verifiable are once again allowed; it turns out that forbidding it (as was done in #​997 for version 4.14.0) is in fact a regression. (@​stakx, #​1121)

Fixed

  • Performance regression: Adding setups to a mock becomes slower with each setup (@​CeesKaas, #​1110)

  • Regression: mock.Verify[All] no longer marks invocations as verified if they were matched by conditional setups. (@​Lyra2108, #​1114)

4.15.2

Changed

  • Upgraded System.Threading.Tasks.Extensions dependency to version 4.5.4 (@​JeffAshton, #​1108)

4.15.1

Added

  • New method overloads for It.Is, It.IsIn, and It.IsNotIn that compare values using a custom IEqualityComparer<T> (@​weitzhandler, #​1064)
  • New properties ReturnValue and Exception on IInvocation to query recorded invocations return values or exceptions (@​MaStr11, #​921, #​1077)
  • Support for "nested" type matchers, i.e. type matchers that appear as part of a composite type (such as It.IsAnyType[] or Func<It.IsAnyType, bool>). Argument match expressions like It.IsAny<Func<It.IsAnyType, bool>>() should now work as expected, whereas they previously didn't. In this particular example, you should no longer need a workaround like (Func<It.IsAnyType, bool>)It.IsAny<object>() as originally suggested in #​918. (@​stakx, #​1092)

Changed

  • Event accessor calls (+= and -=) now get consistently recorded in Mock.Invocations. This previously wasn't the case for backwards compatibility with VerifyNoOtherCalls (which got implemented before it was possible to check them using Verify{Add,Remove}). You now need to explicitly verify expected calls to event accessors prior to VerifyNoOtherCalls. Verification of += and -= now works regardless of whether or not you set those up (which makes it consistent with how verification usually works). (@​80O, @​stakx, #​1058, #​1084)
  • Portable PDB (debugging symbols) are now embedded in the main library instead of being published as a separate NuGet symbols package (`.snupkg) (@​kzu, #​1098)

Fixed

  • SetupProperty fails if property getter and setter are not both defined in mocked type (@​stakx, #​1017)
  • Expression tree argument not matched when it contains a captured variable – evaluate all captures to their current values when comparing two expression trees (@​QTom01, #​1054)
  • Failure when parameterized Mock.Of<> is used in query comprehension from clause (@​stakx, #​982)

4.14.7

Changed

  • Mocks created by DefaultValue.Mock now inherit SetupAllProperties from their "parent" mock (like it says in the XML documentation) (@​stakx, #​1074)

Fixed

  • Setup not triggered due to VB.NET transparently inserting superfluous type conversions into a setup expression (@​InteXX, #​1067)
  • Nested mocks created by Mock.Of<T>() no longer have their properties stubbed since version 4.14.0 (@​vruss, @​1071)
  • Verify fails for recursive setups not explicitly marked as Verifiable (@​killergege, #​1073)
  • Mock.Of<> fails for COM interop types that are annotated with a [CompilerGenerated] custom attribute (@​killergege, #​1072)

4.14.6

Fixed

  • Regression since 4.14.0: setting nested non-overridable properties via Mock.Of (@​mariotee, #​1039)

4.14.5

Fixed

  • Regression since version 4.11.0: VerifySet fails with NullReferenceException for write-only indexers (@​Epicycle23, #​1036)

4.14.4

Fixed

  • Regression: NullReferenceException on subsequent setup if expression contains null reference (@​IanYates83, #​1031)

4.14.3

Fixed

  • Regression, Part II: Verify behavior change using DefaultValue.Mock (@​DesrosiersC, #​1024)

4.14.2

Fixed

  • Regression: Verify behavior change using DefaultValue.Mock (@​DesrosiersC, #​1024)

4.14.1

Added

  • New SetupSequence verbs .PassAsync() and .ThrowsAsync(...) for async methods with void return type (@​fuzzybair, #​993)

Fixed

  • StackOverflowException on VerifyAll when mocked method returns mocked object (@​hotchkj, #​1012)

4.14.0

Added

  • A mock's setups can now be inspected and individually verified via the new Mock.Setups collection and IInvocation.MatchingSetup property (@​stakx, #​984-#​987, #​989, #​995, #​999)

  • New .Protected().Setup and Protected().Verify method overloads to deal with generic methods (@​JmlSaul, #​967)

  • Two new public methods in Times: bool Validate(int count) and string ToString() (@​stakx, 975)

Changed

  • Attempts to mark conditionals setup as verifiable are now considered an error, since conditional setups are ignored during verification. Calls to .Verifiable() on conditional setups are no-ops and can be safely removed. (@​stakx, #​997)

  • When matching invocations against setups, captured variables nested inside expression trees are now evaluated. Their values likely matter more than their identities. (@​stakx, #​1000)

Fixed

  • Regression: Restored Capture.In use in mock.Verify(expression, ...) to extract arguments of previously recorded invocations. (@​vgriph, #​968; @​stakx, #​974)

  • Consistency: When mocking a class C whose constructor invokes one of its virtual members, Mock.Of<C>() now operates like new Mock<C>(): a record of such invocations is retained in the mock's Invocations collection (@​stakx, #​980)

  • After updating Moq from 4.10.1 to 4.11, mocking NHibernate session throws a System.NullReferenceException (@​ronenfe, #​955)

4.13.1

Fixed

  • SetupAllProperties does not recognize property as read-write if only setter is overridden (@​stakx, #​886)

  • Regression: InvalidCastException caused by Moq erroneously reusing a cached auto-mocked (DefaultValue.Mock) return value for a different generic method instantiation (@​BrunoJuchli, #​932)

  • AmbiguousMatchException when setting up the property, that hides another one (@​ishatalkin, #​939)

  • ArgumentException ("Interface not found") when setting up object.ToString on an interface mock (@​vslynko, #​942)

  • Cannot "return" to original mocked type after downcasting with Mock.Get and then upcasting with mock.As<> (@​pjquirk, #​943)

  • params arrays in recursive setup expressions are matched by reference equality instead of by structural equality (@​danielcweber, #​946)

  • mock.SetupProperty throws NullReferenceException when called for partially overridden property (@​stakx, #​951)

4.13.0

Changed

  • Improved error message that is supplied with ArgumentException thrown when Setup or Verify are called on a protected method if the method could not be found with both the name and compatible argument types specified (@​thomasfdm, #​852).

  • mock.Invocations.Clear() now removes traces of previous invocations more thoroughly by additionally resetting all setups to an "unmatched" state. (@​stakx, #​854)

  • Consistent Callback delegate validation regardless of whether or not Callback is preceded by a Returns: Validation for post-Returns callback delegates used to be very relaxed, but is now equally strict as in the pre-Returns case.) (@​stakx, #​876)

  • Subscription to mocked events used to be handled less strictly than subscription to regular CLI events. As with the latter, subscribing to mocked events now also requires all handlers to have the same delegate type. (@​stakx, #​891)

  • Moq will throw when it detects that an argument matcher will never match anything due to the presence of an implicit conversion operator. (@​michelcedric, #​897, #​898)

  • New algorithm for matching invoked methods against methods specified in setup/verification expressions. (@​stakx, #​904)

Added

  • Added support for setup and verification of the event handlers through Setup[Add|Remove] and Verify[Add|Remove|All] (@​lepijohnny, #​825)

  • Added support for lambda expressions while creating a mock through new Mock<SomeType>(() => new SomeType("a", "b")) and repository.Create<SomeType>(() => new SomeType("a", "b")). This makes the process of mocking a class without a parameterless constructor simpler (compiler syntax checker...). (@​frblondin, #​884)

  • Support for matching generic type arguments: mock.Setup(m => m.Method<It.IsAnyType>(...)). (@​stakx, #​908)

    The standard type matchers are:

    • It.IsAnyType — matches any type
    • It.IsSubtype<T> — matches T and proper subtypes of T
    • It.IsValueType — matches only value types

    You can create your own custom type matchers:

    [TypeMatcher]
class Either<A, B> : ITypeMatcher
{
    public bool Matches(Type type) => type == typeof(A) || type == typeof(B);
}

  • In order to support type matchers (see bullet point above), some new overloads have been added to existing methods:

    • setup.Callback(new InvocationAction(invocation => ...)),
      setup.Returns(new InvocationFunc(invocation => ...)):

      The lambda specified in these new overloads will receive an IInvocation representing the current invocation from which type arguments as well as arguments can be discovered.

    • Match.Create<T>((object argument, Type parameterType) => ..., ...),
      It.Is<T>((object argument, Type parameterType) => ...):

      Used to create custom matchers that work with type matchers. When a type matcher is used for T, the argument received by the custom matchers is untyped (object), and its actual type (or rather the type of the parameter for which the argument was passed) is provided via an additional parameter parameterType. (@​stakx, #​908)

... (truncated)

4.12.0

Changed

  • Improved performance for Mock.Of<T> and mock.SetupAllProperties() as the latter now performs property setups just-in-time, instead of as an ahead-of-time batch operation. (@​vanashimko, #​826)
  • Setups with no .Returns(…) nor .CallBase() no longer return default(T) for loose mocks, but a value that is consistent with the mock's CallBase and DefaultValue[Provider] settings. (@​stakx, #​849)

Added

  • New method overload sequenceSetup.ReturnsAsync(Func<T>) (@​stakx, #​841)
  • LINQ to Mocks support for strict mocks, i.e. new method overloads for Mock.Of, Mocks.Of, mockRepository.Of, and mockRepository.OneOf that accept a MockBehavior parameter. (@​stakx, #​842)

Fixed

  • Adding Callback to a mock breaks async tests (@​marcin-chwedczuk-meow, #​702)
  • mock.SetupAllProperties() now setups write-only properties for strict mocks, so that accessing such properties will not throw anymore. (@​vanashimko, #​836)
  • Regression: mock.SetupAllProperties() and Mock.Of<T> fail due to inaccessible property accessors (@​Mexe13, #​845)
  • Regression: VerifyNoOtherCalls causes stack overflow when mock setup returns the mocked object (@​bash, #​846)
  • Capture.In() no longer captures arguments when other setup arguments do not match (@​ocoanet, #​844).
  • CaptureMatch no longer invokes the capture callback when other setup arguments do not match (@​ocoanet, #​844).

Commits viewable in compare view.

Dependabot compatibility score

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)

@dependabot
Bump Moq from 4.11.0 to 4.20.72
30b7da4 
---
updated-dependencies:
- dependency-name: Moq
  dependency-version: 4.20.72
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added .NET Pull requests that update .NET code dependencies Pull requests that update a dependency file labels Apr 7, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file .NET Pull requests that update .NET code

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants