fix(deps): update dependency org.mockito:mockito-core to v5 #181
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
2 times, most recently
from
7fb5574 to
d3a72ae
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
from
d3a72ae to
c1e0a6f
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
from
c1e0a6f to
1b35c9b
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
from
1b35c9b to
7a691e8
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
from
7a691e8 to
b3e330e
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
from
b3e330e to
deb6674
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
from
deb6674 to
345974b
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
from
345974b to
e509d3f
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
from
e509d3f to
e238759
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
from
e238759 to
acb44c0
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
from
acb44c0 to
4f7c1d7
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
from
4f7c1d7 to
6d8bf14
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
from
6d8bf14 to
d3b7264
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
from
d3b7264 to
1f73c64
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
2 times, most recently
from
33c3bdd to
10cf7f3
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
from
10cf7f3 to
61f8d90
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
2 times, most recently
from
85d7d26 to
b14a556
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
from
b14a556 to
3c842f4
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
4.11.0->5.14.2Release Notes
mockito/mockito (org.mockito:mockito-core)
v5.14.2Changelog generated by Shipkit Changelog Gradle Plugin
5.14.2
mockito-prefix (#3460)v5.14.1Changelog generated by Shipkit Changelog Gradle Plugin
5.14.1
v5.14.0Changelog generated by Shipkit Changelog Gradle Plugin
5.14.0
v5.13.0Compare Source
Changelog generated by Shipkit Changelog Gradle Plugin
5.13.0
Only.verifythrowsNullPointerException(#3237)v5.12.0Compare Source
Changelog generated by Shipkit Changelog Gradle Plugin
5.12.0
AdditionalMatchers.and()andAdditionalMatchers.or()not to swap the order of matchers (#3335)v5.11.0Compare Source
Changelog generated by Shipkit Changelog Gradle Plugin
5.11.0
@Captortest parameters don't work with primitive type arguments (#3229)v5.10.0Compare Source
Changelog generated by Shipkit Changelog Gradle Plugin
5.10.0
v5.9.0Compare Source
What's Changed
New Contributors
Full Changelog: mockito/mockito@v5.8.0...v5.9.0
v5.8.0Compare Source
Changelog generated by Shipkit Changelog Gradle Plugin
5.8.0
v5.7.0Compare Source
Changelog generated by Shipkit Changelog Gradle Plugin
5.7.0
0.8.11(#3147)v5.6.0Compare Source
Changelog generated by Shipkit Changelog Gradle Plugin
5.6.0
Optionalis notemptywhen usingRETURN_DEEP_STUBS(#2865)v5.5.0Compare Source
Changelog generated by Shipkit Changelog Gradle Plugin
5.5.0
v5.4.0Changelog generated by Shipkit Changelog Gradle Plugin
5.4.0
@Mock(serializable = true)for parameterized types. (#3007)ArgumentMatchers#any()JavaDoc(#3003)
@Mock(serializable = true)no longer works with parameterized types (#2979)v5.3.1Changelog generated by Shipkit Changelog Gradle Plugin
5.3.1
v5.3.0Changelog generated by Shipkit Changelog Gradle Plugin
5.3.0
withoutAnnotationsparameter to@Mock(#2965)ArgumentMatchers#assertArgmethod. (#2949)v5.2.0Changelog generated by Shipkit Changelog Gradle Plugin
5.2.0
v5.1.1Changelog generated by Shipkit Changelog Gradle Plugin
5.1.1
v5.1.0Changelog generated by Shipkit Changelog Gradle Plugin
5.1.0
CONTRIBUTING.md(#2870)CONTRIBUTING.md(#2868)Mockito#{mock,spy}(T... reified)with@SafeVarargs(#2866)v5.0.0Compare Source
Mockito 5: prepare for future JDK versions
For a while now, we have seen an increase in problems/incompatibilities with recent versions of the JDK due to our usage of JVM-internal API.
Most notably, JDK 17 made some changes which are incompatible with the current subclass mockmaker.
Therefore, to prepare for the future of JDK, we are making some core changes to ensure Mockito keeps on working.
Switch the default mockmaker to
mockito-inlineBack in Mockito 2.7.6, we published a new mockmaker based on the "inline bytecode" principle.
This mockmaker creates mocks manipulating bytecode equivalent within the original class such that its method implementations hook into the normal Mockito machinery.
As a comparison, the subclass mockmaker generates "real" subclasses for mocks, to mimic the same behavior.
While the approaches are similar, the inline mockmaker avoids certain restrictions that the JDK imposes.
For example, it does not violate module boundaries (introduced in JDK 9, but more heavily used in JDK 17) and avoids the leaking of the creation of the subclass.
Massive thanks to community member @reta who implemented this change.
Note: this does not affect
mockito-androidnor testing on Android.When should I still be using the subclass mockmaker?
There are legitimate remaining use cases for the subclass mockmaker.
For example, on the Graal VM's native image, the inline mockmaker will not work and the subclass mockmaker is the appropriate choice.
Additionally, if you would like to avoid mocking final classes, using the subclass mockmaker is a possibibility.
Note however that if you solely want to use the subclass mockmaker to avoid mocking final, you will run into the above mentioned issues on JDK 17+.
We want to leave this choice up to our users, which is why we will keep on supporting the subclass mockmaker.
If you want to use the subclass mockmaker instead, you can use the new
mockito-subclassartifact (published on Maven Central along with all our other artifacts).Update the minimum supported Java version to 11
Mockito 4 supports Java 8 and above.
Similar to other open source projects, we are moving away from JDK 8 and to newer versions.
The primary reason for moving away from JDK 8 is the increasing maintenance costs with keeping our own infrastructure working.
Lately we have been running into more and more JDK 8 breakages.
Additionally, while we want to support the newest JDK API's, our current solution to support both JDK 8 and newer versions causes issues with the
SecurityManager.Since we want Mockito to work on the newest version and more and more businesses adopting JDK 11, we have decided to make the switch as well.
Massive thanks to community member @reta who implemented this change.
What should I do if I still run JDK 8?
For JDK 8 and below, you can keep on using Mockito 4.
This is similar to if you are using JDK 6, for which you can keep on using Mockito 2.
The changes in Mockito 5 (for now) are primarily focused on the latest JDK versions, which means the API differences between Mockito 4 and 5 are minimal.
However, over time this will most likely widen, so we do recommend adopting JDK 11 in the future.
New
type()method onArgumentMatcherOne of our most used public API's for customizing Mockito is the
ArgumentMatcherinterface.The interface allows you to define a custom matcher, whi
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.
This PR was generated by Mend Renovate. View the repository job log.