Repository navigation
FINERACT-2684: Update all non-major dependencies - #6687
Open
renovate-bot wants to merge 1 commit into
Open
renovate-bot wants to merge 1 commit into
renovate-bot wants to merge 1 commit into
Conversation
galovics
reviewed
Oct 19, 2026
galovics
left a comment
Contributor
There was a problem hiding this comment.
Mostly mechanical, but a few bumps I'd like a second look at before this goes in:
apache/kafka:4.4.0-rc2indocker-compose-postgresql-kafka.yml: why an-rcimage, and a two-minor jump (4.2 to 4.4)? Can we pin a GA tag, or leave it out of this PR?- netty 4.1.138 to 4.2.19 is a different Netty line even though it is labelled non-major. Which of Kafka, the AWS SDK, Tomcat or Jersey in our tree was built against 4.2? Did the integration and messaging suites run on this? (Also: 16 hand-pinned netty artifacts where
netty-bomexists, a follow-up.) - logback 1.5.38 to 1.6.5: compatible with our slf4j / Spring Boot versions, anything in the logback XML config deprecated in 1.6?
localstack/localstack2.1 to 2.3: do the S3/SQS behaviours our tests rely on stay the same?lz4-javasubstitution is pinned in two files, keep them in sync.
Let's hold for green CI.
renovate-bot
force-pushed
the
renovate/all-minor-patch
branch
from
October 19, 2026 21:03
b30537c to
d80e79d
Compare
Contributor
|
As part of the 1.16.0 release, all stories were closed, including FINERACT-2684. We won't accept any more PRs against them. Please use the new "minor bugfixes" story, FINERACT-2968, instead: change the PR title and the commit message prefix from |
renovate-bot
force-pushed
the
renovate/all-minor-patch
branch
from
October 20, 2026 23:33
d80e79d to
0451445
Compare
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
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.
Note
This PR body was truncated due to platform limits.
This PR contains the following updates:
v8.0.1→v8.0.2v6.0.1→v6.1.04.2.0-rc2→4.4.0-rc29.7.1→9.8.2v6.3.0→v6.4.02.1→2.312.2→12.318.3→18.610.1.59-jdk25-temurin→10.1.61-jdk25-temurinv0.6.4→v0.7.11.11.4→1.12.04.1.138.Final→4.2.19.Final4.1.138.Final→4.2.19.Final4.1.138.Final→4.2.19.Final4.1.138.Final→4.2.19.Final4.1.138.Final→4.2.19.Final4.1.138.Final→4.2.19.Final4.1.138.Final→4.2.19.Final4.1.138.Final→4.2.19.Final4.1.138.Final→4.2.19.Final4.1.138.Final→4.2.19.Final4.1.138.Final→4.2.19.Final4.1.138.Final→4.2.19.Final4.1.138.Final→4.2.19.Final4.1.138.Final→4.2.19.Final4.1.138.Final→4.2.19.Final4.1.138.Final→4.2.19.Final10.9→10.103.20.0→3.21.07.34.3→7.34.97.34.3→7.34.97.34.3→7.34.97.34.3→7.34.92.17.1→2.20.02.17.1→2.20.042.7.13→42.7.141.12.1→1.12.26.0.1→6.2.06.0.1→6.2.06.0.1→6.2.09.1.3.Final→9.1.5.Final2.2.49→2.2.552.2.49→2.2.552.2.49→2.2.556.2.5→6.3.23.0.3→3.1.13.9.16→3.10.07.6.0.202603022253-r→7.8.0.202609011348-r7.6.0.202603022253-r→7.8.0.202609011348-r7.6.0.202603022253-r→7.8.0.202609011348-r1.84→1.861.84→1.861.84→1.861.84→1.861.18.46→1.18.481.22.0→1.23.05.14.0→5.15.04.9.8→4.10.54.8.184→4.8.1992.14.2→2.15.03.3.0→3.3.33.4.1→3.5.19.4.1→9.6.17.22.0→7.26.03.3.0→3.3.36.5.4→6.5.131.13.0→1.15.02.2.49→2.2.551.2.2→1.2.30.8.1→0.11.03.3.0→3.3.38.10.2→8.10.43.0.2→3.1.03.3.0→3.3.33.0.4→3.0.52.3.6→2.3.94.5.0→4.6.01.35.0→1.37.033.6.0-jre→33.7.2-jre1.5.38→1.6.51.5.38→1.6.54.0.2→4.0.32.44.4→2.57.15.23.0→5.24.07.34.3→7.34.92.22.3→2.22.46.0.3→6.1.32.3.21→2.4.211.62.0→1.67.04.0.2→4.2.01.16.5→1.17.12.0.17→2.0.204.1.0→4.3.0Release Notes
actions/download-artifact
v8.0.2Compare Source
What's Changed
New Contributors
Full Changelog: actions/download-artifact@v8.0.1...v8.0.2
actions/setup-java
v6.1.0Compare Source
What's Changed
New Contributors
Full Changelog: actions/setup-java@v6.0.1...v6.1.0
apache/kafka
v4.3.1Compare Source
v4.3.0Compare Source
gradle/gradle (gradle)
v9.8.2: 9.8.2Compare Source
The Gradle team is excited to announce Gradle 9.8.2.
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.2 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.8.1: 9.8.1Compare Source
This is a patch release for Gradle 9.8.0. We recommend using 9.8.1 instead of 9.8.0.
This release addresses three high rated vulnerabilities:
The following issues were resolved:
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.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.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.
gradle/actions
v6.4.0Compare Source
Highlights
Gradle version support status in the Job Summary
The actions now report the support status of every Gradle version used in a workflow, as job
annotations and in the Job Summary (#1057). Thanks to @ov7a for the contribution.
Deliberately not reported: patch releases (being on
9.7.0when9.7.1exists is not flagged) andpre-releases (release candidates, milestones and snapshots never produce annotations). The latest
Gradle release is determined from the wrapper checksum data already bundled with the action, so no
network access is required.
Note that these annotations are emitted independently of the
add-job-summarysetting: settingadd-job-summary: 'never'suppresses the Job Summary itself, but the warning and notice annotationsremain.
Gradle itself is now reported in the dependency graph
The
dependency-submissionaction now applies v1.5.0 of theGitHub Dependency Graph Gradle Plugin
(up from v1.4.2) (#1069).
The headline change is that the Gradle Build Tool running the build is now reported as an
org.gradle:gradle-coredependency, so that GitHub can surface known vulnerabilities in the versionof Gradle used to run your build. These are the coordinates that GitHub advisories for the Gradle
Build Tool are published against.
Details worth knowing:
that filter aggressively.
A new Gradle signing key, if you use dependency verification
github-dependency-graph-gradle-plugin1.5.0is signed with a new Gradle signing subkey, and thekey previously documented in our setup guide has been revoked upstream:
org.gradle:github-dependency-graph-gradle-plugin1.5.0and laterE2879931BCA1A42E55F2D64DD9B2DFBD9F3298BA(new)org.gradleplugin versions before the rotation7B79ADD11F8A779FE90FD3D0893A028475557671(old, revoked)com.gradleDevelocity Gradle plugin, including4.5.07B79ADD11F8A779FE90FD3D0893A028475557671(old, revoked)Because the Develocity Gradle plugin is still signed with the old key, you should trust both keys
rather than swapping one for the other — replacing the old key outright will break Develocity
injection. The documented snippet in
docs/setup-gradle.md
has been updated accordingly (#1071):
cache-provider: externalfor externally managed Gradle User HomeBuilds that save and restore Gradle User Home by some other mechanism (Develocity Artifact Cache, for
example) previously had to set
cache-disabled: true, which was misleading: caching wasn't disabled,it just wasn't managed by this action, and the Job Summary reported it as "Disabled".
cache-provider: externalskips Gradle User Home restore/save exactly ascache-disableddoes, butreports a distinct External status in the Job Summary explaining that caching is handled by
another provider (#1059).
Develocity access keys containing OIDC tokens now work
Short-lived-token handling validated the
server=key[;server=key]*access key format with a regexwhose
keyportion was too strict, so an access key holding an OIDC token value was rejectedoutright. Worse, had it passed the regex, parsing split each entry on
=and kept only the secondfield — silently truncating any key containing
=(as JWT padding does) and sending the mangledkey to the server. Both problems are fixed (#1061).
Job Summary attribution
Job summaries produced
Configuration
📅 Schedule: (UTC)
* 0-3 * * 1)🚦 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 was generated by Mend Renovate. View the repository job log.