-
Notifications
You must be signed in to change notification settings - Fork 0
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
Update mockito monorepo to v5 (major) #18
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
2 times, most recently
from
January 31, 2023 00:12
4af3afb
to
021d712
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
from
February 20, 2023 10:27
021d712
to
39113bc
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
from
March 9, 2023 21:49
39113bc
to
b3d4364
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
from
April 11, 2023 19:57
b3d4364
to
aaed055
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
from
April 21, 2023 19:51
aaed055
to
f650f5a
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
from
May 3, 2023 08:49
f650f5a
to
ffd525f
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
from
May 28, 2023 08:47
ffd525f
to
4bdf410
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
from
June 18, 2023 11:15
4bdf410
to
fe0a3e3
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
from
August 22, 2023 09:30
fe0a3e3
to
0c85d34
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
from
October 6, 2023 16:15
0c85d34
to
ce65bb7
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
from
November 2, 2023 21:26
ce65bb7
to
bdb6852
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
from
November 16, 2023 13:40
bdb6852
to
7aca0af
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
from
December 1, 2023 22:04
7aca0af
to
ec5528d
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
from
January 14, 2024 15:29
ec5528d
to
c13ae83
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
2 times, most recently
from
January 24, 2024 22:12
87a4ec4
to
b9cc0b3
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
from
March 2, 2024 20:05
b9cc0b3
to
f358efe
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
from
May 11, 2024 10:49
f358efe
to
345c938
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
from
August 27, 2024 20:00
345c938
to
c9636f4
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
2 times, most recently
from
September 30, 2024 12:43
e9e3542
to
52e757c
Compare
renovate
bot
force-pushed
the
renovate/major-mockito-monorepo
branch
from
October 15, 2024 18:17
52e757c
to
dfd3d63
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:
4.11.0
->5.14.2
4.11.0
->5.14.2
Release Notes
mockito/mockito (org.mockito:mockito-junit-jupiter)
v5.14.2
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
Compare 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.0
Compare Source
Changelog generated by Shipkit Changelog Gradle Plugin
5.11.0
@Captor
test parameters don't work with primitive type arguments (#3229)v5.10.0
Compare Source
Changelog generated by Shipkit Changelog Gradle Plugin
5.10.0
v5.9.0
Compare Source
What's Changed
New Contributors
Full Changelog: mockito/mockito@v5.8.0...v5.9.0
v5.8.0
Compare Source
Changelog generated by Shipkit Changelog Gradle Plugin
5.8.0
v5.7.0
Changelog generated by Shipkit Changelog Gradle Plugin
5.7.0
0.8.11
(#3147)v5.6.0
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
Compare Source
Changelog generated by Shipkit Changelog Gradle Plugin
5.2.0
v5.1.1
Compare Source
Changelog generated by Shipkit Changelog Gradle Plugin
5.1.1
v5.1.0
Compare Source
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
Compare 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-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 w
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 becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR was generated by Mend Renovate. View the repository job log.