Repository navigation
Update dependencies - #48
Merged
Merged
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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:
9.7.1→9.8.09.8.1v46.3.1→v46.3.7v46.3.83.2.0→3.3.00.14.1→0.14.20.9.9→0.9.11Release Notes
gradle/gradle (gradle)
v9.8.0: 9.8.0Compare Source
The Gradle team is excited to announce Gradle 9.8.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:
Aman Gautam,
Björn Kautler,
Eng Zer Jun,
Hashim Khan,
Julian Krannich,
KBS,
Labh R Jethe,
Mark Dodgson,
Maxim,
monkey,
nataphon-ktsystems,
Paul King,
Qiu Tian,
rg_sandesh,
Roberto Perez Alcolea,
Sean,
Zongle Wang.
Upgrade instructions
Switch your build to use Gradle 9.8.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.
renovatebot/github-action
v46.3.7Compare Source
Documentation
Miscellaneous Chores
Build System
Continuous Integration
v46.3.6Compare Source
Bug Fixes
Documentation
Miscellaneous Chores
Continuous Integration
v46.3.5Compare Source
Documentation
Miscellaneous Chores
Build System
Continuous Integration
v46.3.4Compare Source
Bug Fixes
renovate-imageto take a full digest-pinned image (#1082) (16deced)Miscellaneous Chores
Continuous Integration
v46.3.3Compare Source
Bug Fixes
Continuous Integration
v46.3.2Compare Source
Documentation
Miscellaneous Chores
Build System
Continuous Integration
uber/NullAway (com.uber.nullaway:nullaway)
v0.14.2This release adds
JSpecifyUnrecognizedAnnotationLocation, an opt-in check that reportsnullness annotations in locations JSpecify does not recognize. See further documentation
on the wiki: https://github.com/uber/NullAway/wiki/JSpecify-Support#jspecifyunrecognizedannotationlocation-checker
Not packaged in the release, but we have also added a script to remove unnecessary NullAway
suppressions to the repo: https://github.com/uber/NullAway/tree/master/scripts/nullaway-suppression-remover
We expect this to be a useful script to run after NullAway updates, to check if
NullAway improvements make some suppressions unnecessary.
Also of note, NullAway now more precisely detects whether the JDK used for the build properly
supports reading type use annotations from bytecode, particularly important for JSpecify
mode. This may lead NullAway to crash on certain build configurations that were
unsupported before but we were not detecting precisely.
Beyond the above, this release includes further fixes for JSpecify mode and
JSpecifyExperimental, especially for wildcard bounds and multi-dimensional arrays,
along with other bug fixes.
Finally, we have re-enabled pushing snapshot builds to the Sonatype snapshots repository,
which should ease testing NullAway versions between releases.
JSpecifyUnrecognizedAnnotationLocation, an opt-in check that reports nullness annotations in locations JSpecify does not recognize by @vlsi (#1787)RequireExplicitNullMarkingdiagnostics repeating the check name, so a report no longer begins with[RequireExplicitNullMarking] [RequireExplicitNullMarking]by @vlsi (#1815)nullin comparisons by @Beluomini (#1750)Assisted-by:commit trailer for AI-assisted work by @vlsi (#1811)Assisted-by:text to the PR template and CONTRIBUTING.md (#1838)getRawTypeAttributesinGenericsChecks(#1844)addSourceFilecalls in AndroidTest by @jabrailkhalil (#1839)Kotlin/kotlinx-kover (org.jetbrains.kotlinx:kover-gradle-plugin)
v0.9.11===================
Kover Gradle Plugin
Bugfixes
#831Reverted the fix of #827v0.9.10===================
Kover Gradle Plugin
Bugfixes
#822Fixed concurrency problem with Kover reporter#825Added check on duplicate project dependencies#827Added skip of test tasks without binary reportConfiguration
📅 Schedule: (UTC)
🚦 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 CLI.