-
Notifications
You must be signed in to change notification settings - Fork 23
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 #393
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
from
March 4, 2023 06:07
ffda5c9
to
6075f9e
Compare
renovate
bot
force-pushed
the
renovate/all
branch
from
March 13, 2023 10:31
6075f9e
to
ed14f62
Compare
renovate
bot
force-pushed
the
renovate/all
branch
3 times, most recently
from
March 30, 2023 10:53
69fa895
to
50cd3bf
Compare
renovate
bot
force-pushed
the
renovate/all
branch
from
April 6, 2023 07:02
50cd3bf
to
fcfcde3
Compare
renovate
bot
force-pushed
the
renovate/all
branch
2 times, most recently
from
April 19, 2023 07:45
50d1488
to
c71d609
Compare
renovate
bot
force-pushed
the
renovate/all
branch
3 times, most recently
from
June 3, 2023 22:22
d082a18
to
43293e7
Compare
renovate
bot
force-pushed
the
renovate/all
branch
from
June 7, 2023 20:04
43293e7
to
0e86690
Compare
renovate
bot
force-pushed
the
renovate/all
branch
4 times, most recently
from
July 1, 2023 22:53
bf2c582
to
cbe2554
Compare
renovate
bot
force-pushed
the
renovate/all
branch
2 times, most recently
from
July 10, 2023 13:52
1f53069
to
fd49e85
Compare
renovate
bot
force-pushed
the
renovate/all
branch
from
July 17, 2023 22:44
fd49e85
to
6f22221
Compare
renovate
bot
force-pushed
the
renovate/all
branch
2 times, most recently
from
August 1, 2023 17:12
b81ac6a
to
e0a609e
Compare
renovate
bot
force-pushed
the
renovate/all
branch
4 times, most recently
from
August 23, 2023 12:47
7807681
to
183babb
Compare
renovate
bot
force-pushed
the
renovate/all
branch
3 times, most recently
from
September 4, 2023 16:40
5570078
to
47c47d0
Compare
renovate
bot
force-pushed
the
renovate/all
branch
from
September 29, 2023 02:24
47c47d0
to
39e6d85
Compare
renovate
bot
force-pushed
the
renovate/all
branch
11 times, most recently
from
February 4, 2024 11:32
fa7650d
to
f482c27
Compare
renovate
bot
force-pushed
the
renovate/all
branch
2 times, most recently
from
February 16, 2024 22:47
0242653
to
7de9799
Compare
renovate
bot
force-pushed
the
renovate/all
branch
2 times, most recently
from
March 7, 2024 07:54
389c0e1
to
b831933
Compare
renovate
bot
force-pushed
the
renovate/all
branch
from
March 12, 2024 20:20
b831933
to
2180787
Compare
renovate
bot
force-pushed
the
renovate/all
branch
2 times, most recently
from
March 22, 2024 18:35
bbb0e79
to
46384d6
Compare
renovate
bot
force-pushed
the
renovate/all
branch
2 times, most recently
from
April 14, 2024 09:18
05fad5c
to
03a9ce1
Compare
renovate
bot
force-pushed
the
renovate/all
branch
from
April 18, 2024 19:53
03a9ce1
to
95d22dd
Compare
renovate
bot
force-pushed
the
renovate/all
branch
3 times, most recently
from
May 10, 2024 11:14
be637c0
to
294597b
Compare
renovate
bot
force-pushed
the
renovate/all
branch
from
May 21, 2024 07:59
294597b
to
6bf9e8a
Compare
renovate
bot
force-pushed
the
renovate/all
branch
3 times, most recently
from
May 31, 2024 23:06
b25bd7b
to
f5c1831
Compare
renovate
bot
force-pushed
the
renovate/all
branch
from
June 6, 2024 15:59
f5c1831
to
603cfa7
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:
v3
->v4
v3
->v4
8.7
->8.8
11.0.22+7
->21.0.3+9.0.LTS
6.14.0
->6.25.0
0.24.0
->0.28.0
0.12.1
->0.14.0
1.6.4
->1.8.1
1.5.1
->1.7.0
2.2.3
->2.3.11
2.2.3
->2.3.11
2.2.3
->2.3.11
2.2.3
->2.3.11
2.2.3
->2.3.11
2.2.3
->2.3.11
2.2.3
->2.3.11
2.2.3
->2.3.11
2.2.3
->2.3.11
2.2.3
->2.3.11
2.2.3
->2.3.11
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
gradle/gradle (gradle)
v8.8
: 8.8Compare Source
The Gradle team is excited to announce Gradle 8.8.
Read the Release Notes
We would like to thank the following community members for their contributions to this release of Gradle:
Björn Kautler,
Denes Daniel,
Fabian Windheuser,
Hélio Fernandes Sebastião,
Jay Wei,
jhrom,
jwp345,
Jörgen Andersson,
Kirill Gavrilov,
MajesticMagikarpKing,
Maksim Lazeba,
Philip Wedemann,
Robert Elliot,
Róbert Papp,
Stefan M.,
Tibor Vyletel,
Tony Robalik,
Valentin Kulesh,
Yanming Zhou,
김용후
Upgrade instructions
Switch your build to use Gradle 8.8 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.
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:
Kotlin/binary-compatibility-validator (org.jetbrains.kotlinx.binary-compatibility-validator)
v0.14.0
Compare Source
The release contains changes potentially affecting dump's content (#144, #162, #161, #175).
What changed:
$EntriesMappings
classes backing Kotlin's 1.9Enum.entries
are now filtered out (#144)DefaultImpls
class (#161)api/
) is added (#170)package-info
classes could be now filtered from the dump by adding these annotations tononPublicMarkers
(#175)ignoredClasses
behavior to avoid exclusion of classes whose name is a prefix of some ignoredClasses values (#136)Thanks to @qwwdfsad, @bryanlogan, @aSemy, @xtrm-en and @Goooler for contributions!
v0.13.2
Compare Source
kotlinx-metadata
is updated to 0.6.2 with the support of LV 2.0v0.13.1
Compare Source
v0.13.0
Compare Source
Kotlin/kotlinx.coroutines (org.jetbrains.kotlinx:kotlinx-coroutines-test)
v1.8.1
Compare Source
@ExperimentalTime
annotation from usages ofTimeSource
(#4046). Thanks, @hfhbd!NullPointerException
when setting theStateFlow
value on old Android devices (#3820).kotlin.random.Random
as part ofDispatchers.Default
andDispatchers.IO
initialization (#4051).Flow.timeout
throws the exception with which the channel was closed (#4071).Changelog relative to version 1.8.1-Beta
Flow.timeout
throws the exception with which the channel was closed (#4071).v1.8.0
Compare Source
Dispatchers.Main != Dispatchers.Main.immediate
(#3545, #3963).Flow
operators that limit cancel the upstream flow to forget that they were already finished if there is another such operator upstream (#4035, #4038)kotlinx-coroutines-debug
is published with the correct Java 9 module info (#3944).kotlinx-coroutines-debug
no longer requires manually settingDebugProbes.enableCoroutineCreationStackTraces
tofalse
, it's the default (#3783).kotlinx-coroutines-test
: set the default timeout ofrunTest
to 60 seconds, added the ability to configure it on the JVM with thekotlinx.coroutines.test.default_timeout=10s
(#3800).kotlinx-coroutines-test
: fixed a bug that could lead to not all uncaught exceptions being reported after some tests failed (#3800).delay(Duration)
rounds nanoseconds up to whole milliseconds and not down (#3920). Thanks @kevincianfarini!Dispatchers.Default
and the default thread for background work are guaranteed to use the same context classloader as the object containing it them (#3832).SharedFlow.collect
suspends for the first time, it's registered as a subscriber for thatSharedFlow
(#3885). Before, it was also true, but not documented.withLock
on JS (#3881). Thanks @CLOVIS-AI!Changelog relative to version 1.8.0-RC2
kotlinx-coroutines-debug
no longer requires manually settingDebugProbes.enableCoroutineCreationStackTraces
tofalse
, it's the default (#3783).Flow
operators that limit cancel the upstream flow to forget that they were already finished if there is another such operator upstream (#4035, #4038)v1.7.3
Compare Source
v1.7.2
Compare Source
Bug fixes and improvements
CopyableThreadContextElement
now properly copies an element when crossing the coroutine boundary inflowOn
(#3787). Thanks @wanyingd1996!newSingleThreadContext
from closing (#3768).Mutex
duringtryLock
/unlock
sequence with owners is fixed (#3745).v1.7.1
Compare Source
Bug fixes and improvements
runTest
is restored (#3673)onUndeliveredElement
now allocate less memory (#3646)v1.7.0
Compare Source
Core API significant improvements
Channel
implementation with significant performance improvements across the API (#3621).select
operator implementation: faster, more lightweight, and more robust (#3020).Mutex
andSemaphore
now share the same underlying data structure (#3020).Dispatchers.IO
is added to K/N (#3205)newFixedThreadPool
andDispatchers.Default
implementations on K/N were wholly rewritten to support graceful growth under load (#3595).kotlinx-coroutines-test
rework:timeout
parameter torunTest
for the whole-test timeout, 10 seconds by default (#3270). This replaces the configuration of quiescence timeouts, which is now deprecated (#3603).withTimeout
exception messages indicate if the timeout used the virtual time (#3588).TestCoroutineScheduler
,runTest
, andTestScope
API are promoted to stable (#3622).runTest
now also fails if there were uncaught exceptions in coroutines not inherited from the test coroutine (#1205).Breaking changes
kotlinx-coroutines-core
andkotlinx-coroutines-jdk8
artifacts were merged into a single artifact (#3268).\b
symbol and are now navigable in IDE and supplied with proper documentation (#2291).CoroutineContext.isActive
returnstrue
for contexts without any job in them (#3300).Bug fixes and improvements
JavaFx
version is updated to 17.0.2 inkotlinx-coroutines-javafx
(#3671)..BroadcastChannel
and all the corresponding API are deprecated (#2680).Dispatchers.Default
is backed by the number of threads equal to the number of available cores (#3366).Job.parent
API (#3201).TestScheduler
leaked cancelled jobs (#3398).TestScope.timeSource
now provides comparable time marks (#3617). Thanks @hfhbd!withTimeout
handles were preserved in JS runtime (#3440).awaitFrame
only awaits a single frame when used from the main looper (#3432). Thanks @pablobaxter!Class-Path
attribute was removed fromkotlinx-coroutines-debug.jar
manifest (#3361).updateThreadContext
operated on the parent context (#3411).Flow.filterIsInstance
extension (#3240).Dispatchers.Default
thread name prefixes are now configurable with system property (#3231).Flow.timeout
operator as@FlowPreview
(#2624). Thanks @pablobaxter!future
builder in case of exceptions (#3475). Thanks @He-Pin!Mono.awaitSingleOrNull
now waits for theonComplete
signal (#3487).Channel.isClosedForSend
andChannel.isClosedForReceive
are promoted from experimental to delicate (#3448).EventLoop
(#3547).Dispatchers.IO.limitedParallelism(valueLargerThanIOSize)
no longer creates an additional wrapper (#3442). Thanks @dovchinnikov!@FlowPreview
and@ExperimentalCoroutinesApi
are promoted to experimental and stable respectively (#3542, #3097, #3548).Dispatchers.Default
andDispatchers.IO
(#3416, #3418).suspendCancellableCoroutineReusable
might have hanged (#3613).CoroutineExceptionHandler
is no longer invoked in case of unprocessedfuture
failure (#3452).withContext
operator (#3592).DebugProbes
(#3527).CoroutineDispatcher.asExecutor()
runs tasks without dispatching if the dispatcher is unconfined (#3683). Thanks @odedniv!SharedFlow.toMutableList
andSharedFlow.toSet
lints are introduced (#3706).Channel.invokeOnClose
is promoted to stable API (#3358).Dispatchers.Default
andDispatchers.IO
during the startup phase (#3652).Dispatchers.Default
(#3642).limitedParallelism
to perform dispatches even after the underlying dispatcher was closed (#3672).cause
was selected (#3714).Changelog for previous versions may be found in CHANGES_UP_TO_1.7.md
Kotlin/kotlinx.serialization (org.jetbrains.kotlinx:kotlinx-serialization-json)
v1.7.0
==================
This release contains all of the changes from 1.7.0-RC and is compatible with Kotlin 2.0.
Please note that for reasons explained in the 1.7.0-RC changelog, it may not be possible to use it with the Kotlin 1.9.x
compiler plugin. Yet, it is still fully backwards compatible with previous versions.
The only difference with 1.7.0-RC is that
classDiscriminatorMode
property inJsonBuilder
is marked as experimental,as it should have been when it was introduced (#2680).
v1.6.3
==================
This release provides a couple of new features and uses Kotlin 1.9.22 as default.
Class discriminator output mode
Class discriminator provides information for serializing and deserializing polymorphic class hierarchies.
In case you want to encode more or less information for various third party APIs about types in the output, it is possible to control
addition of the class discriminator with the
JsonBuilder.classDiscriminatorMode
property.For example,
ClassDiscriminatorMode.NONE
does not add class discriminator at all, in case the receiving party is not interested in Kotlin types.You can learn more about this feature in the documentation and corresponding PR.
Other features
Bugfixes and improvements
v1.6.2
v1.6.1
==================
This release uses Kotlin 1.9.20 by default, while upcoming 1.9.21 is also supported.
Trailing commas in Json
Trailing commas are one of the most popular non-spec Json variations.
A new configuration flag,
allowTrailingComma
, makes Json parser accept them instead of throwing an exception.Note that it does not affect encoding, so kotlinx.serialization always produces Json without trailing commas.
See details in the corresponding PR
Support of WasmJs target
Kotlin/Wasm has been experimental for some time and gained enough maturity to be added to the kotlinx libraries.
Starting with 1.6.1, kotlinx.serialization provides a wasm-js flavor, so your projects with Kotlin/Wasm can have even more
functionality.
As usual, just add serialization dependencies to your build
and declare wasmJs target.
Please remember that Kotlin/Wasm is still experimental, so changes are expected.
Bugfixes and improvements
v1.6.0
==================
This release contains all features and bugfixes from 1.6.0-RC plus some bugfixes on its own (see below).
Kotlin 1.9.0 is used as a default, while 1.9.10 is also supported.
Bugfixes
ktorio/ktor (io.ktor:ktor-client-okhttp)
v2.3.11
Compare Source
Bugfixes
v2.3.10
Compare Source
Bugfixes
NumberFormatException
when uploading file larger than INT_MAX bytes (~2.1 GiB) since 2.3.0 (KTOR-6851)Improvements
Configuration
📅 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.