-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(deps): update dependency org.mockito:mockito-core to v5 #186
Open
renovate
wants to merge
1
commit into
master
Choose a base branch
from
renovate/major-mockito-monorepo
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
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
force-pushed
the
renovate/major-mockito-monorepo
branch
from
October 28, 2021 12:49
87e9df8
to
2173563
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
from
November 11, 2021 18:39
2173563
to
3d017d7
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
from
November 19, 2021 17:39
3d017d7
to
6802434
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
from
December 16, 2021 15:06
6802434
to
79e72ac
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
from
March 7, 2022 15:03
79e72ac
to
48acd05
Compare
renovate
bot
changed the title
chore(deps): update dependency org.mockito:mockito-core to v4
fix(deps): update dependency org.mockito:mockito-core to v4
Mar 7, 2022
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
3 times, most recently
from
March 29, 2022 16:57
45a0401
to
df7fc0b
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
2 times, most recently
from
April 21, 2022 14:11
fd0aac5
to
59a5f8c
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
3 times, most recently
from
May 27, 2022 21:23
212e71f
to
fa175e5
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
from
June 2, 2022 19:41
fa175e5
to
87e7a47
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
2 times, most recently
from
July 14, 2022 16:55
b2ff8ae
to
43a4902
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
from
August 13, 2022 12:37
43a4902
to
012a268
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
4 times, most recently
from
September 10, 2022 00:08
66b192e
to
7f9566e
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
from
September 12, 2022 22:31
7f9566e
to
6129520
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
3 times, most recently
from
September 21, 2022 21:34
88ca1ee
to
2f93aa7
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
from
October 5, 2022 19:52
2f93aa7
to
e3b17bb
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
3 times, most recently
from
October 23, 2022 21:56
6a95d51
to
ad94954
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
2 times, most recently
from
June 20, 2023 00:26
709f88e
to
3a4d866
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
from
August 22, 2023 11:54
3a4d866
to
a367362
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
from
October 6, 2023 16:24
a367362
to
fb25254
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
from
November 2, 2023 21:12
fb25254
to
11483d1
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
from
December 1, 2023 21:59
11483d1
to
19424ba
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
from
January 14, 2024 16:20
19424ba
to
cdbd9d2
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
from
January 24, 2024 21:32
cdbd9d2
to
7b04edb
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
from
March 1, 2024 11:23
7b04edb
to
024b66d
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
from
May 11, 2024 12:03
024b66d
to
e6f6b50
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
5 times, most recently
from
July 25, 2024 15:54
adf51c9
to
c79ed0d
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
3 times, most recently
from
August 29, 2024 20:57
bc595ef
to
1fb8058
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
from
September 17, 2024 17:02
1fb8058
to
f84b99a
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
2 times, most recently
from
September 30, 2024 13:53
e89b87b
to
b756822
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
from
October 15, 2024 14:49
b756822
to
6e530dc
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
3 times, most recently
from
October 23, 2024 01:17
027795b
to
3a8fc33
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
from
January 2, 2025 18:59
3a8fc33
to
660f391
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
2 times, most recently
from
January 30, 2025 22:31
d77f4cc
to
52534c6
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
from
January 31, 2025 23:05
52534c6
to
7dff38f
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 participants
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:
3.12.4
->5.15.2
Release Notes
mockito/mockito (org.mockito:mockito-core)
v5.15.2
Compare Source
Changelog generated by Shipkit Changelog Gradle Plugin
5.15.2
v5.14.2
Compare Source
Changelog generated by Shipkit Changelog Gradle Plugin
5.14.2
mockito-
prefix (#3460)v5.14.1
Changelog generated by Shipkit Changelog Gradle Plugin
5.14.1
v5.14.0
Changelog generated by Shipkit Changelog Gradle Plugin
5.14.0
v5.13.0
Changelog generated by Shipkit Changelog Gradle Plugin
5.13.0
Only.verify
throwsNullPointerException
(#3237)v5.12.0
Changelog generated by Shipkit Changelog Gradle Plugin
5.12.0
AdditionalMatchers.and()
andAdditionalMatchers.or()
not to swap the order of matchers (#3335)v5.11.0
Changelog generated by Shipkit Changelog Gradle Plugin
5.11.0
@Captor
test parameters don't work with primitive type arguments (#3229)v5.10.0
Changelog generated by Shipkit Changelog Gradle Plugin
5.10.0
v5.9.0
What's Changed
New Contributors
Full Changelog: mockito/mockito@v5.8.0...v5.9.0
v5.8.0
Changelog generated by Shipkit Changelog Gradle Plugin
5.8.0
v5.7.0
Compare Source
Changelog generated by Shipkit Changelog Gradle Plugin
5.7.0
0.8.11
(#3147)v5.6.0
Compare Source
Changelog generated by Shipkit Changelog Gradle Plugin
5.6.0
Optional
is notempty
when usingRETURN_DEEP_STUBS
(#2865)v5.5.0
Compare Source
Changelog generated by Shipkit Changelog Gradle Plugin
5.5.0
v5.4.0
Compare Source
Changelog 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.1
Compare Source
Changelog generated by Shipkit Changelog Gradle Plugin
5.3.1
v5.3.0
Compare Source
Changelog generated by Shipkit Changelog Gradle Plugin
5.3.0
withoutAnnotations
parameter to@Mock
(#2965)ArgumentMatchers#assertArg
method. (#2949)v5.2.0
Changelog generated by Shipkit Changelog Gradle Plugin
5.2.0
v5.1.1
Changelog generated by Shipkit Changelog Gradle Plugin
5.1.1
v5.1.0
Changelog 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.0
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-inline
Back 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-android
nor 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-subclass
artifact (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.
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.