[quick_actions]: Bump mockito-core from 3.2.4 to 4.6.1 in /packages/quick_actions/quick_actions_android/android

[dependabot]

Bumps mockito-core from 3.2.4 to 4.6.1.

Release notes

Sourced from mockito-core's releases.

v4.6.1

Changelog generated by Shipkit Changelog Gradle Plugin

4.6.1

• 2022-06-02 - 6 commit(s) by Andy Coates, Chen Ni, dependabot[bot]
• Bump material from 1.6.0 to 1.6.1 [(#2662)](mockito/mockito#2662)
• Bump core-ktx from 1.7.0 to 1.8.0 [(#2661)](mockito/mockito#2661)
• Bump groovy from 3.0.10 to 3.0.11 [(#2660)](mockito/mockito#2660)
• Fix for Issue2656 [(#2659)](mockito/mockito#2659)
• Bump assertj-core from 3.22.0 to 3.23.1 [(#2658)](mockito/mockito#2658)
• Regression? Strictness set in @MockitoSettings ignored after upgrade from 4.5.1 to 4.6.0 [(#2656)](mockito/mockito#2656)
• Fix typo [(#2655)](mockito/mockito#2655)

v4.6.0

Changelog generated by Shipkit Changelog Gradle Plugin

4.6.0

• 2022-05-27 - 14 commit(s) by Hervé Boutemy, K. Siva Prasad Reddy, Rafael Winterhalter, dependabot[bot]
• Bump shipkit-changelog from 1.1.15 to 1.2.0 [(#2654)](mockito/mockito#2654)
• Bump versions.errorprone from 2.13.1 to 2.14.0 [(#2653)](mockito/mockito#2653)
• Bump shipkit-auto-version from 1.1.20 to 1.2.0 [(#2651)](mockito/mockito#2651)
• Fixes #2648 : Add support for customising strictness via @​Mock annotation and MockSettings [(#2650)](mockito/mockito#2650)
• Any way to enable Strict Stubbing when using Mockito.mock() without using @​Mock? [(#2648)](mockito/mockito#2648)
• Reintroduce inheriting type annotations from interfaces if only one interface is mocked, including additional interfaces. [(#2645)](mockito/mockito#2645)
• Bump com.diffplug.spotless from 6.6.0 to 6.6.1 [(#2643)](mockito/mockito#2643)
• fix Reproducible Build issue [(#2642)](mockito/mockito#2642)
• Bump com.diffplug.spotless from 6.5.2 to 6.6.0 [(#2641)](mockito/mockito#2641)
• Mockito mock of interfaces lost annotation information [(#2640)](mockito/mockito#2640)
• Bump material from 1.5.0 to 1.6.0 [(#2637)](mockito/mockito#2637)
• Bump com.diffplug.spotless from 6.5.1 to 6.5.2 [(#2636)](mockito/mockito#2636)
• Bump versions.bytebuddy from 1.12.9 to 1.12.10 [(#2635)](mockito/mockito#2635)
• Bump com.diffplug.spotless from 6.5.0 to 6.5.1 [(#2632)](mockito/mockito#2632)
• Bump com.diffplug.spotless from 6.4.2 to 6.5.0 [(#2631)](mockito/mockito#2631)

v4.5.1

Changelog generated by Shipkit Changelog Gradle Plugin

4.5.1

• 2022-04-21 - 2 commit(s) by Jeremy Landis, dependabot[bot]
• Fixes #2623: Use zulu distribution and java 11 for release GHA job [(#2624)](mockito/mockito#2624)
• Missing errorprone module for 4.5.0 in central as release was done with jdk 8 [(#2623)](mockito/mockito#2623)
• Bump kotlinVersion from 1.6.20 to 1.6.21 [(#2622)](mockito/mockito#2622)

Missing net.bytebuddy.utility.GraalImageCode exception

If you encounter any issues with missing ByteBuddy classes, make sure you are using ByteBuddy 1.12 or higher.

v4.5.0

Changelog generated by Shipkit Changelog Gradle Plugin

4.5.0

... (truncated)

Commits

• ff98622 Restore behavior for mocks configured without strictness (#2659)
• 1fbef57 Bump groovy from 3.0.10 to 3.0.11 (#2660)
• c47c7ec Bump core-ktx from 1.7.0 to 1.8.0 (#2661)
• 2bbf796 Bump material from 1.6.0 to 1.6.1 (#2662)
• 4f41700 Bump assertj-core from 3.22.0 to 3.23.1 (#2658)
• e5a06c5 Fix typo (#2655)
• 93bba11 Bump shipkit-changelog from 1.1.15 to 1.2.0 (#2654)
• 70cf2d2 Add support for customizing strictness via @Mock annotation and `MockSettin...
• 6ce278b Bump versions.errorprone from 2.13.1 to 2.14.0 (#2653)
• 7d2e4cc Bump shipkit-auto-version from 1.1.20 to 1.2.0 (#2651)
• 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)

[flutter-dashboard]

It looks like this pull request may not have tests. Please make sure to add tests before merging. If you need an exemption to this rule, contact Hixie on the #hackers channel in Chat (don't just cc him here, he won't see it! He's on Discord!).

If you are not sure if you need tests, consider this rule of thumb: the purpose of a test is to make sure someone doesn't accidentally revert the fix. Ask yourself, is there anything in your PR that you feel it is important we not accidentally revert back to how it was before your fix?

Reviewers: Read the Tree Hygiene page and make sure this patch meets those guidelines before LGTMing.

[stuartmorgan-g]

@dependabot rebase

[stuartmorgan-g]

Looks like this will need some test updates for Mockito changes.

[Hixie]

test-exempt: dependency roll

[stuartmorgan-g]

LGTM with the version bump removed.

[stuartmorgan-g]

Since this only affects tests, which don't impact clients of the plugin, you can remove the version bump from the pubspec and just use NEXT here.

publishable may still flag it because of build.gradle, but since it's a testImplementation line that's a false positive that you can override with the label. (Currently it's not doing any line-level analysis of the diff, only looking at files. Eventually we should make it smarter.)

[camsim99]

Oh I understand now. Ok thanks!