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:
v4.7.3→v4.8.0v5.4.3→v5.5.29.0.0→9.3.00.19.3→0.21.10.9.1→0.9.42.0.0→2.1.00.34.0→0.36.08.0.0→8.2.02.2.0→2.3.0Release Notes
JamesIves/github-pages-deploy-action (JamesIves/github-pages-deploy-action)
v4.8.0Compare Source
What's Changed
Build 🔧
Full Changelog: JamesIves/github-pages-deploy-action@v4...v4.8.0
v4.7.6Compare Source
What's Changed
Build 🔧
Full Changelog: JamesIves/github-pages-deploy-action@v4...v4.7.6
v4.7.5Compare Source
What's Changed
Bug Fixes 🐛
Build 🔧
Full Changelog: JamesIves/github-pages-deploy-action@v4...v4.7.5
v4.7.4Compare Source
What's Changed
Bug Fixes 🐛
Build 🔧
Other Changes
Full Changelog: JamesIves/github-pages-deploy-action@v4...v4.7.4
codecov/codecov-action (codecov/codecov-action)
v5.5.2Compare Source
What's Changed
Full Changelog: https://github.com/codecov/codecov-action/compare/v5.5.1..v5.5.2
v5.5.1Compare Source
What's Changed
codecov-cliversion reference example by @webknjaz in #1774Full Changelog: https://github.com/codecov/codecov-action/compare/v5.5.0..v5.5.1
v5.5.0Compare Source
What's Changed
Full Changelog: https://github.com/codecov/codecov-action/compare/v5.4.3..v5.5.0
gradle/gradle (gradle)
v9.3.0Compare Source
v9.2.1: 9.2.1Compare Source
The Gradle team is excited to announce Gradle 9.2.1.
Here are the highlights of this release:
Read the Release Notes
We would like to thank the following community members for their contributions to this release of Gradle:
Adam,
Björn Kautler,
hasunzo,
HYEON,
Hyunjoon Park,
HYUNJUN SON,
Jendrik Johannes,
Kirill Gavrilov,
Madalin Valceleanu,
Martin Bonnin,
Matthew Haughton,
Mikhail Polivakha,
Na Minhyeok,
Philip Wedemann,
Philipp Schneider,
Róbert Papp,
Simon Marquis,
TheGoesen,
Vincent Potucek,
Xin Wang.
Upgrade instructions
Switch your build to use Gradle 9.2.1 by updating your wrapper:
See the Gradle 9.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.
v9.2.0Compare Source
v9.1.0: 9.1.0Compare Source
The Gradle team is excited to announce Gradle 9.1.0.
Here are the highlights of this release:
Read the Release Notes
We would like to thank the following community members for their contributions to this release of Gradle:
Eng Zer Jun,
EunHyunsu,
Gaëtan Muller,
HeeChul Yang,
Jendrik Johannes,
Johnny Lim,
Junho Lee,
Kirill Gavrilov,
Matthew Haughton,
Na Minhyeok,
Philip Wedemann,
Philipp Schneider,
Pradyumna C,
r-a-sattarov,
Ryszard Perkowski,
Sebastian Schuberth,
SebastianHeil,
Staffan Al-Kadhimi,
winfriedgerlach,
Xin Wang.
Upgrade instructions
Switch your build to use Gradle 9.1.0 by updating your wrapper:
See the Gradle 9.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.
drewhamilton/Poko (dev.drewhamilton.poko)
v0.21.1Compare Source
2026-01-08
Fix Gradle plugin compatibility with Gradle isolated projects.
Add forward compatibility with Kotlin 2.3.20-Beta1.
v0.21.0Compare Source
2025-12-16
Update compiler plugin ID to "dev.drewhamilton.poko" (was previously "poko-compiler-plugin").
Deprecate
@SkipSupportannotation and stop requiring it for using@Poko.Skipannotation. Updatedeprecation level of
@ArrayContentSupportand@ArrayContentBasedtoERROR.Compile with Kotlin 2.3.0. Compile with Java 25, except for the Gradle plugin, which is compiled
with Java 24.
Drop support for Kotlin 2.2 due to incompatibility. Increase the minimum supported Gradle version to
9.0.0.
v0.20.2Compare Source
2025-11-19
Compile with Kotlin 2.2.21. Add forward compatibility with Kotlin 2.3.0-RC.
v0.20.1Compare Source
2025-10-16
Add ability to generate a subset of Poko functions with
@Poko.EqualsAndHashCodeand@Poko.ToString. Apply one of these to a class instead of the standard@Pokoannotation, and onlythe respective function(s) will be generated by the Poko plugin. This feature is experimental and
requires opt-in via
@IndependentFunctionsSupport.Add forward compatibility with Kotlin 2.3.0-Beta1.
Target Gradle 9.1.0, and add backward compatibility with Gradle 8.11.
v0.20.0Compare Source
2025-09-11
Compile with Kotlin 2.2.20.
Drop support for Kotlin 2.2.0 and 2.2.10 due to incompatibility.
vanniktech/gradle-maven-publish-plugin (com.vanniktech.maven.publish)
v0.36.0Compare Source
BREAKING
DirectorySignatureTypeinternal.Behavior changes
validateDeploymentnow has theDeploymentValidationenum as type instead of being a boolean. The defaultis now to just wait for the
VALIDATEDstate. The previous behavior can be achieved by setting it toPUBLISHED.NONEcan be used for disabling the validation completely.configure(...)manually to configure what to publish and not passingjavadocJarexplicity,the plugin now defaults to publishing an empty javadoc jar.
Features
when using the default options and the Dokka plugin is applied to the project.
JavadocJarandSourcesJaroptions toconfigureBasedOnAppliedPluginsand to allapplicable project types that can be passed to
configure. The previousBooleanbased versions havebeen deprecated.
mavenCentralDeploymentValidationandmavenCentralAutomaticPublishingare used for the default values of the 2 parameters when they are not passedexplicitly. This allows to more easily override them in certain environments.
gradle.propertiesfiles are now considered inthe same way they are when isolated projects is disabled.
Improvements
Minimum supported versions
Compatibility tested up to
v0.35.0Compare Source
com.android.kotlin.multiplatform.library.SONATYPE_HOSTis not set toCENTRAL_PORTAL.Thanks to @joshfriend, @Flowdalic and @Goooler for their contributions to this release.
Minimum supported versions
Compatibility tested up to
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ 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 was generated by Mend Renovate. View the repository job log.