-
Notifications
You must be signed in to change notification settings - Fork 28
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
chore(deps): update all dependencies #392
Open
renovate
wants to merge
1
commit into
master
Choose a base branch
from
renovate/all
base: master
Could not load branches
Branch not found: {{ refName }}
Could not load tags
Nothing to show
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.
Open
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/all
branch
4 times, most recently
from
June 7, 2023 23:22
3b75468
to
53b1df1
Compare
renovate
bot
force-pushed
the
renovate/all
branch
3 times, most recently
from
June 15, 2023 13:07
1b71ec2
to
3eff076
Compare
renovate
bot
force-pushed
the
renovate/all
branch
3 times, most recently
from
June 23, 2023 18:35
ebe1160
to
4f97dea
Compare
renovate
bot
force-pushed
the
renovate/all
branch
4 times, most recently
from
July 2, 2023 00:44
ed792a7
to
729f81e
Compare
renovate
bot
force-pushed
the
renovate/all
branch
2 times, most recently
from
July 10, 2023 16:14
c2b1c7b
to
c7e4bb8
Compare
renovate
bot
force-pushed
the
renovate/all
branch
from
July 18, 2023 02:06
c7e4bb8
to
62bb41e
Compare
renovate
bot
force-pushed
the
renovate/all
branch
4 times, most recently
from
August 1, 2023 17:00
10c5f0e
to
3db388d
Compare
renovate
bot
force-pushed
the
renovate/all
branch
4 times, most recently
from
August 9, 2023 21:09
0a48e01
to
facc396
Compare
renovate
bot
force-pushed
the
renovate/all
branch
3 times, most recently
from
August 21, 2023 10:29
8163e17
to
8231274
Compare
renovate
bot
force-pushed
the
renovate/all
branch
from
August 22, 2023 06:35
8231274
to
15500bc
Compare
renovate
bot
force-pushed
the
renovate/all
branch
2 times, most recently
from
March 27, 2024 12:51
8927db1
to
3d848d5
Compare
renovate
bot
force-pushed
the
renovate/all
branch
3 times, most recently
from
April 3, 2024 20:19
2cba2f5
to
29e78f9
Compare
renovate
bot
force-pushed
the
renovate/all
branch
6 times, most recently
from
April 14, 2024 11:00
78c338d
to
d2d4339
Compare
renovate
bot
force-pushed
the
renovate/all
branch
3 times, most recently
from
April 18, 2024 18:33
4f9de60
to
844d17e
Compare
renovate
bot
force-pushed
the
renovate/all
branch
4 times, most recently
from
May 7, 2024 11:01
bc89857
to
d3806b8
Compare
renovate
bot
force-pushed
the
renovate/all
branch
3 times, most recently
from
May 14, 2024 22:34
4293687
to
f0388e8
Compare
renovate
bot
force-pushed
the
renovate/all
branch
5 times, most recently
from
May 21, 2024 18:25
d7ce7c1
to
7f2d273
Compare
renovate
bot
force-pushed
the
renovate/all
branch
2 times, most recently
from
May 29, 2024 19:32
0ff7199
to
5ac2988
Compare
renovate
bot
force-pushed
the
renovate/all
branch
from
June 1, 2024 00:08
5ac2988
to
81e5fb0
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:
v3
->v4
v3
->v4
v2
->v3
8.0.2
->8.8
11.0.22+7
->21.0.3+9.0.LTS
6.16.0
->6.25.0
0.24.0
->0.28.0
7.4.2
->8.4.1
1.4.5
->1.5.6
2.0.6
->2.0.13
0.12.1
->1.1.0
4.9.2
->4.12.2
1.13.4
->1.13.11
1.8.0
->1.12.0
1.2.1
->1.3.2
1.6.1
->1.7.0
1.9.0
->1.13.1
3.1.1
->3.3.0
1.3.1
->1.6.7
1.3.1
->1.6.7
0.20.0
->0.24.0
2.1.3
->2.1.12
2.8.0
->2.9.0
2.8.0
->2.9.0
2.2.4
->2.3.11
2.2.4
->2.3.11
1.6.4
->1.8.1
1.6.4
->1.8.1
1.6.4
->1.8.1
1.3.3
->1.6.7
1.8.10
->2.0.0
1.8.10
->2.0.0
Release Notes
actions/checkout (actions/checkout)
v4
Compare Source
actions/setup-java (actions/setup-java)
v4
Compare Source
android-actions/setup-android (android-actions/setup-android)
v3
Compare Source
gradle/gradle (gradle)
v8.8
Compare Source
v8.7
Compare Source
v8.6
Compare Source
v8.5
: 8.5Compare Source
The Gradle team is excited to announce Gradle 8.5.
Read the Release Notes
We would like to thank the following community members for their contributions to this release of Gradle:
Ahmed Ehab,
Alex Landau,
Aurimas,
Björn Kautler,
bodhili,
Daniel Le Berre,
davidburstrom,
Franz Wimmer,
Jongwoo Han,
Ken,
Leonardo Silveira,
Martin Bonnin,
Matthew Von-Maszewski,
Nik Clayton,
noeppi_noeppi,
Philip Wedemann,
Philipp Schneider,
Tomas Bjerre
Upgrade instructions
Switch your build to use Gradle 8.5 by updating your wrapper:
See the Gradle 8.x upgrade guide to learn about deprecations, breaking changes and other considerations when upgrading.
For Java, Groovy, Kotlin and Android compatibility, see the full compatibility notes.
Reporting problems
If you find a problem with this release, please file a bug on GitHub Issues adhering to our issue guidelines.
If you're not sure you're encountering a bug, please use the forum.
We hope you will build happiness with Gradle, and we look forward to your feedback via Twitter or on GitHub.
v8.4
: 8.4Compare Source
The Gradle team is excited to announce Gradle 8.4.
Amongst other improvements, this release addresses two security vulnerabilities:
Read the Release Notes
We would like to thank the following community members for their contributions to this release of Gradle:
Ahmed Ehab,
Andrei Rybak,
Baptiste Decroix,
Björn Kautler,
Cesar de la Vega,
Ganavi Jayaram,
Gaurav Padam,
hwanseok,
J.T. McQuigg,
Jakub Chrzanowski,
Jendrik Johannes,
kackey0-1,
Konstantin Gribov,
Pratik Haldankar,
Qinglin,
Sebastian Schuberth,
Thad House,
valery1707,
Vladimir Sitnikov,
wuyangnju,
Yanming Zhou,
Yanshun Li,
Yusuke Uehara,
zeners
Upgrade instructions
Switch your build to use Gradle 8.4 by updating your wrapper:
Reporting problems
If you find a problem with this release, please file a bug on GitHub Issues adhering to our issue guidelines.
If you're not sure you're encountering a bug, please use the forum.
We hope you will build happiness with Gradle, and we look forward to your feedback via Twitter or on GitHub.
v8.3
: 8.3Compare Source
The Gradle team is excited to announce Gradle 8.3.
Read the Release Notes
We would like to thank the following community members for their contributions to this release of Gradle:
Adam,
Ahmed Ehab,
Aurimas,
Baptiste Decroix,
Björn Kautler,
Borewit,
Korov,
Mohammed Thavaf,
Patrick Brückner,
Philip Wedemann,
Róbert Papp,
Shi Chen,
Tony Robalik
Upgrade instructions
Switch your build to use Gradle 8.3 by updating your wrapper:
Reporting problems
If you find a problem with this release, please file a bug on GitHub Issues adhering to our issue guidelines.
If you're not sure you're encountering a bug, please use the forum.
We hope you will build happiness with Gradle, and we look forward to your feedback via Twitter or on GitHub.
v8.2.1
Compare Source
v8.2
: 8.2Compare Source
The Gradle team is excited to announce Gradle 8.2.
Amongst other improvements, this release addresses two security vulnerabilities:
Read the Release Notes
We would like to thank the following community contributors for their contributions to this release of Gradle:
Bruno Didot,
Eric Vantillard,
esfomeado,
Jendrik Johannes,
Jonathan Leitschuh,
Lee Euije,
Stefan Oehme,
Todor Dinev,
Yanshun Li
Upgrade instructions
Switch your build to use Gradle 8.2 by updating your wrapper:
./gradlew wrapper --gradle-version=8.2
Reporting problems
If you find a problem with this release, please file a bug on GitHub Issues adhering to our issue guidelines.
If you're not sure you're encountering a bug, please use the forum.
We hope you will build happiness with Gradle, and we look forward to your feedback via Twitter or on GitHub.
v8.1.1
: 8.1.1Compare Source
This is a patch release for Gradle 8.1. We recommend using 8.1.1 instead of 8.1.
It fixes the following issues:
Read the Release Notes
Upgrade Instructions
Switch your build to use Gradle 8.1.1 by updating your wrapper:
See the Gradle 8.x upgrade guide to learn about deprecations, breaking changes and other considerations when upgrading to Gradle 8.1.1.
Reporting Problems
If you find a problem with this release, please file a bug on GitHub Issues adhering to our issue guidelines.
If you're not sure you're encountering a bug, please use the forum.
v8.1
: 8.1Compare Source
The Gradle team is excited to announce Gradle 8.1.
Read the Release Notes
We would like to thank the following community contributors for their contributions to this release of Gradle:
André Sousa,
Attila Király,
Aurimas,
Björn Kautler,
Christoph Dreis,
David Morris,
DJtheRedstoner,
Gabriel Feo,
J.T. McQuigg,
JavierSegoviaCordoba,
JayaKrishnan Nair K,
Jeff Widman,
kackey0-1,
Martin Bonnin,
Martin Kealey,
modmuss50,
pan93412,
Sebastian Schuberth,
Simon Marquis,
TheDadda,
Thrillpool,
valery1707,
Xin Wang,
Yanshun Li
Upgrade instructions
Switch your build to use Gradle 8.1 by updating your wrapper:
./gradlew wrapper --gradle-version=8.1
Reporting problems
If you find a problem with this release, please file a bug on GitHub Issues adhering to our issue guidelines.
If you're not sure you're encountering a bug, please use the forum.
We hope you will build happiness with Gradle, and we look forward to your feedback via Twitter or on GitHub.
vanniktech/gradle-maven-publish-plugin (com.vanniktech.maven.publish)
v0.28.0
Compare Source
this use the
CENTRAL_PORTAL
option when specifying the Sonatype host.release
variant if the project has an Android target and no variant was explicitlyspecified through the Kotlin Gradle DSL.
KotlinMultiplatform(...)
.closeAndReleaseRepository
task. UsereleaseRepository
, whichis functionally equivalent, instead.
Minimum supported versions
Compatibility tested up to
Configuration cache status
Configuration cache is generally supported, except for:
v0.27.0
Compare Source
releaseRepository
releases a staging repository at the end of the buildand can be executed in the same build as the publishing task. This allows
having automatic releases without permanently enabling them.
publishToMavenCentral
as alias for runningpublishAllPublicationsToMavenCentralRepository
.publishAndReleaseToMavenCentral
as alias for running both of the above.coordinates(...)
and leave the others at their default value.Thanks to @sschuberth for the contribution.
java-test-fixture
projects being broken with Gradle 8.6.closeAndReleaseRepository
in favor ofreleaseRepository
.Minimum supported versions
Compatibility tested up to
Configuration cache status
When using Gradle 8.1 or newer configuration cache is generally supported.
Exceptions to that are:
v0.26.0
Compare Source
configure(Platform)
from the main plugin to modifywhat is getting published. Check out the docs for more details
configureBasedOnAppliedPlugins
DSL method toallow applying the default
configure
logic of the main plugin.configure(Platform)
now validates that the required plugins areapplied (e.g. Android Gradle Plugin for Android projects).
times for Gradle plugin projects with more than one publication. Thanks to
@autonomousapps for the fix.
next release, because the Kotlin/JS plugin has been deprecated.
from
simpleJavadocJar
toplainJavadocJar
. Thanks to @sschuberth.Minimum supported versions
Compatibility tested up to
Configuration cache status
When using Gradle 8.1 or newer configuration cache is generally supported.
Exceptions to that are:
v0.25.3
Compare Source
java-test-fixtures
plugin.v0.25.2
Compare Source
v0.25.1
Compare Source
v0.25.0
Compare Source
createStagingRepository
task now uses the worker API which allows the project to builtin parallel to the creation of the staging repository.
care of creating the sources jar on its own. Because of this the base plugin won't allow disabling
sources jar creation for Kotlin/JS projects anymore starting with 1.8.20. The
KotlinJs
constructorwith a
sourcesJar
parameter has been deprecated.java-test-fixtures
projectscom.gradle.plugin-publish
1.0.0 and 1.1.0com.gradle.plugin-publish
1.0.0common
sources jar for multiplatform projects will only containthe sources of the common source set instead of containing the sources from all source sets.
Configuration cache status
Configuration cache is supported starting with Gradle 7.6+ except for:
qos-ch/slf4j (org.slf4j:slf4j-api)
v2.0.13
v2.0.12
v2.0.11
v2.0.10
v2.0.9
v2.0.8
v2.0.7
cashapp/turbine (app.cash.turbine:turbine)
v1.1.0
Compare Source
Changed
wasmJs
target, removeiosArm32
andwatchosX86
targets.v1.0.0
Compare Source
Added
turbineScope
DSL function which is now required for usingtestIn
. This ensures that exceptions which occur within the test are no longer potentially lost.Changed
Turbine
s which occur while testing aFlow
(usingtest { }
) will now have their failures eagerly reported.v0.13.0
Compare Source
Added
androidNativeArm32
androidNativeArm64
androidNativeX86
androidNativeX64
linuxArm64
watchosDeviceArm64
Changed
Note: This version has a transitive dependency on kotlinx.coroutines 1.7.0. If you are an Android user, you should be depending on kotlinx.coroutines 1.7.1 which graciously fixes a binary incompatibility with a Compose testing artifact (because they failed to heed its opt-in annotation which indicated that it was not a stable API).
v0.12.3
Compare Source
Fixed
v0.12.2
Compare Source
Changed
Fixed
expectNoEvents()
fails if a completion or exception event occurred.awaitError()
).mockk/mockk (io.mockk:mockk)
v1.13.11
Compare Source
What's Changed
verifyCount
DSL by @T45K in https://github.com/mockk/mockk/pull/1234clearStaticMockk
for KFunction and KProperty by @krocard in https://github.com/mockk/mockk/pull/1239gradle check
before opening a PR by @krocard in https://github.com/mockk/mockk/pull/1240New Contributors
Full Changelog: mockk/mockk@1.13.10...1.13.11
v1.13.10
Compare Source
What's Changed
New Contributors
Full Changelog: mockk/mockk@1.13.9...1.13.10
v1.13.9
Compare Source
What's Changed
slf4jOrJulLogging()
by @SimonMarquis in https://github.com/mockk/mockk/pull/1166android.namespace
to resolve warnings by @kubode in https://github.com/mockk/mockk/pull/1181Configuration
📅 Schedule: Branch creation - "before 3am on the first day of the month" (UTC), 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.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Mend Renovate. View repository job log here.