Bump Moq from 4.14.1 to 4.14.7

dependabot-preview[bot] commented 4 years ago

Bumps Moq from 4.14.1 to 4.14.7.

Changelog

4.14.7 (2020-10-14)

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 (2020-09-30)

Fixed

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

4.14.5 (2020-07-01)

Fixed

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

4.14.4 (2020-06-24)

Fixed

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

4.14.3 (2020-06-18)

Fixed

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

4.14.2 (2020-06-16)

Fixed

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

Commits

02f14d5 Update version to 4.14.7
05f1d5f Merge branch 'com-interop' into hotfix-release
4d7d3c7 Update the changelog
9a936b9 More precise check for anonymous types
69c0223 Mock.Of\<> can't handle [CompilerGenerated] COM interop types
3b537f6 Merge branch 'inner-mock-setups' into hotfix-release
cd9a3c2 Update the changelog
b9e733b Don't require inner mock setups to be matched
42c0083 Inner mock setup causes verification failure
ab83afc Merge branch 'inner-mocks-inherit-setupallproperties' into hotfix-release
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 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 use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language - `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com): - Update frequency (including time of day and day of week) - Pull request limits (per update run and/or open at any time) - Out-of-range updates (receive only lockfile updates, if desired) - Security updates (receive only security updates, if desired)