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.4.2
->v4.4.3
v3
->v4
8.2
->8.4
v2.5.1
->v2.9.0
6.19.0
->6.22.0
4.2.1.3168
->4.4.1.3373
32.1.1-jre
->32.1.3-jre
5.9.3
->5.10.0
2.1.16
->2.1.18
2.2.15
->2.2.18
1.8.20
->1.9.10
1.8.20
->1.9.10
1.9.0
->1.9.10
1.9.0
->1.9.10
1.9.0
->1.9.10
Warning
Some dependencies could not be looked up. Check the warning logs for more information.
Release Notes
JamesIves/github-pages-deploy-action (JamesIves/github-pages-deploy-action)
v4.4.3
Compare Source
What's Changed
Full Changelog: JamesIves/github-pages-deploy-action@v4...v4.4.3
actions/checkout (actions/checkout)
v4
Compare Source
gradle/gradle (gradle)
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
gradle/gradle-build-action (gradle/gradle-build-action)
v2.9.0
Compare Source
The GitHub dependency-review-action helps you understand dependency changes (and the security impact of these changes) for a pull request. This release updates the GItHub Dependency Graph support to be compatible with the
dependency-review-action
.See the documentation for detailed examples.
Changelog
pull-request
events #882dependency-review-action
#879Full-changelog: gradle/gradle-build-action@v2.8.1...v2.9.0
v2.8.1
Compare Source
Fixes an issue that prevented Dependency Graph submission when running on GitHub Enterprise Server.
Fixes
Changelog
v2.8.0
Compare Source
The
v2.8.0
release of thegradle-build-action
introduces an easy mechanism to connect to Gradle Enterprise, as well improved support for self-hosted GitHub Actions runners.Automatic injection of Gradle Enterprise connectivity
It is now possible to connect a Gradle build to Gradle Enterprise without changing any of the Gradle project sources. This is achieved through Gradle Enterprise injection, where an init-script will apply the Gradle Enterprise plugin and associated configuration.
This feature can be useful to easily trial Gradle Enterprise on a project, or to centralize Gradle Enterprise configuration for all GitHub Actions workflows in an organization.
See Gradle Enterprise injection in the README for more info.
Restore Gradle User Home when directory already exists
Previously, the Gradle User Home would not be restored if the directory already exists. This wasn't normally an issue with GitHub-hosted runners, but limited the usefulness of the action for persistent, self-hosted runners.
This behaviour has been improved in this release:
Changes
Issues fixed: https://github.com/gradle/gradle-build-action/issues?q=milestone%3A2.8.0+is%3Aclosed
Full changelog: gradle/gradle-build-action@v2.7.1...v2.8.0
v2.7.1
Compare Source
This release contains no code changes, only dependency updates and documentation improvements.
Changelog
v2.7.0
Compare Source
GitHub Dependency Graph support
In this release, the GitHub Dependency Graph support is no longer considered "experimental", and should be considered ready for production use. You can read more about the Dependency Graph support in the README chapter.
Changes
[email protected]
dependency-graph-file
output to any step that generates a Dependency Graph fileChangelog
v2.6.1
Compare Source
Dependency Graph support
This patch release fixes and improves a couple of aspects of the experimental Dependency Graph support:
job.correlator
value for each Gradle invocation within a Job. This permits multiple Gradle invocations in a single job to generate and submit a separate dependency graph.[email protected]
, which brings a number of improvements to the generated dependency graph:v2.6.0
Compare Source
GitHub Dependency Graph support (Experimental)
This release brings experimental support for submitting a GitHub Dependency Graph snapshot via the GitHub Dependency Submission API.
The dependency graph snapshot is generated via integration with the GitHub Dependency Graph Gradle Plugin, and saved as a workflow artifact. The generated snapshot files can be submitted either in the same job, or in a subsequent job (in the same or a dependent workflow).
The generated dependency graph snapshot reports all of the dependencies that were resolved during a bulid execution, and is used by GitHub to generate Dependabot Alerts for vulnerable dependencies, as well as to populate the Dependency Graph insights view.
Check out the README chapter for more details on how this works and how to configure a workflow that submits a dependency graph.
Changelog
swagger-api/swagger-parser (io.swagger.parser.v3:swagger-parser)
v2.1.18
: Swagger-parser 2.1.18 released!Compare Source
v2.1.17
: Errored release (compiler release = 11) - use v2.1.18Compare Source
Faulty release because of compile release set to 11 instead of 8. Use v2.1.18 which corrects the issue
swagger-api/swagger-core (io.swagger.core.v3:swagger-models)
v2.2.18
: Swagger-core 2.2.18 released!v2.2.17
: Swagger-core 2.2.17 released!Compare Source
v2.2.16
: Swagger-core 2.2.16 released!Compare Source
Kotlin/dokka (org.jetbrains.dokka:versioning-plugin)
v1.9.10
: 1.9.10 BetaGeneral
HTML format
Gradle
Java
v1.9.0
: 1.9.0 BetaGeneral improvements
HTML format
This release is packed with enhancements and bugfixes that make your API reference docs mobile-friendly!
You may find it a weird direction for improvement — we were just as surprised to find that almost 1/4 of Standard Library's API reference traffic is coming from mobile devices. Thanks to the Kotlin Website team, who contributed these improvements, Dokka now provides a solid experience to such visitors.
Improvements:
Bugfixes
Java interoperability
Javadoc format
@author
,@since
and@return
tags (https://github.com/Kotlin/dokka/issues/1770). Thanks to @irina-turova!Other
Known problems
Some Multiplatform Gradle 8 projects might experience build failures when resolving native/platform dependencies. Please, see https://github.com/Kotlin/dokka/issues/3153 for more details and workarounds.
Breaking changes
This release introduces some breaking changes that are expected to affect only a fraction of Dokka users.
HTML
Note: this section only applies to those customizing Dokka's HTML format by overriding styles or HTML templates. If you are not doing any customizations, you may skip this section.
To lay a solid foundation to making the HTML format responsive, some page layouts and many styles had to be changed in a backward-incompatible manner.
If you are overriding
logo-styles.css
to provide your own header logo, please update it to be in line with the new styles - there is significantly less position hardcoding now. See this example for how it can be done.If you are overriding
styles.css
with your own file, please update the baseline styles to the latest, and see if anything is broken. If you get stuck with adapting your styles to the changes, the diff might help.If you are overriding
base.ftl
orheader.ftl
templates, please update them to the latest, and adapt your changes.CLI runner
Due to the analysis refactoring needed for the migration to K2 (#3099), the JARs required to run Dokka have slightly changed.
The following JARs are no longer supported or published:
Please, replace them with a single JAR:
Plugin API
An internal refactoring of Dokka's analysis API was much needed for the migration to K2, leading to breaking changes in some cases.
If your Dokka plugin compiles without any problems — you may ignore this information, you are likely not affected.
If something doesn't compile or doesn't work anymore, please see #3099 for more details.
JetBrains/kotlin (org.jetbrains.kotlin:kotlin-test)
v1.9.10
: Kotlin 1.9.10Compare Source
Changelog
Compiler
KT-60769
Partially revert KT-58371KT-60659
Incorrect 'unresolved reference: addFirst' error with JDK 21KT-60371
Native custom allocator link errorKT-60986
Native: static caches with custom runtime options are broken on LinuxKT-60770
Fix false-positive ABSTRACT_MEMBER_NOT_IMPLEMENTED on toArray with JDK 21KT-60231
NoClassDefFoundError: $$$$$NON_LOCAL_RETURN$$$$$ after upgrade to Kotlin 1.9.0JavaScript
KT-60785
KJS: Destructured value class in suspend function fails with Uncaught TypeError: can't convert to primitive type errorKT-60852
Kotlin JS(IR): IllegalArgumentException: Cross module dependency resolution failed when updating to Kotlin 1.9.0KT-57509
KJS: Compiler generates native JS operator == for comparing values with Any typeNative
KT-60230
Native: "unknown options: -ios_simulator_version_min -sdk_version" with Xcode 15 beta 3KT-60758
Native: Building for 'iOS-simulator', but linking in dylib built for 'iOS' in Xcode 15 beta 4Native. C and ObjC Import
KT-59167
Native: cinterop is unable to build interop libraries against the Xcode 15 Beta 1Tools. Gradle
KT-61147
Kotlin Compiler 1.9.0 bundles a stripped unshadowed version of GsonKT-60543
NoClassDefFoundError for com/gradle/scan/plugin/BuildScanExtensionChecksums
Configuration
📅 Schedule: Branch creation - "on saturday" (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.