Repository navigation
Update all dependencies - #1147
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
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #1147 +/- ##
==========================================
- Coverage 9.59% 8.53% -1.06%
+ Complexity 2099 1666 -433
==========================================
Files 8645 8645
Lines 83245 83245
Branches 381 381
==========================================
- Hits 7985 7108 -877
- Misses 75065 75966 +901
+ Partials 195 171 -24 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
renovate
Bot
force-pushed
the
renovate/all
branch
6 times, most recently
from
September 7, 2026 10:20
8636ce4 to
96acf85
Compare
renovate
Bot
force-pushed
the
renovate/all
branch
10 times, most recently
from
October 5, 2026 08:52
eb214b3 to
aca952d
Compare
renovate
Bot
force-pushed
the
renovate/all
branch
11 times, most recently
from
October 12, 2026 10:06
154b02f to
b5bd5f8
Compare
renovate
Bot
force-pushed
the
renovate/all
branch
from
October 12, 2026 13:21
b5bd5f8 to
2738544
Compare
renovate
Bot
force-pushed
the
renovate/all
branch
from
October 13, 2026 11:18
2738544 to
e6731a6
Compare
This branch has not been deployed
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:
v7.0.0→v7.1.1v4.37.8→v4.38.39.7.1→9.8.1v6.3.0→v6.4.017.3.0→17.6.04.18.0→4.18.133.7.1-jre→33.7.2-jre1.2026.6→1.2026.88.6.0→8.7.04.2.17.Final→4.2.19.Final4.2.17.Final→4.2.19.Final5.23.0→5.24.04.2.17.Final→4.2.19.Final2.0.18→2.0.204.2.17.Final→4.2.19.Final3.20.0→3.21.03.18.1→3.18.24.2.17.Final→4.2.19.Final2.59.0→2.61.09.4.0→9.5.01.65.0→1.67.05.6.4→5.6.58.6.0→8.7.02.4.10→2.4.21Release Notes
codecov/codecov-action
v7.1.1Compare Source
What's Changed
Full Changelog: codecov/codecov-action@v7.1.0...v7.1.1
v7.1.0Compare Source
What's Changed
Full Changelog: codecov/codecov-action@v7.0.0...v7.1.0
github/codeql-action
v4.38.3Compare Source
v4.38.2Compare Source
v4.38.1Compare Source
v4.38.0Compare Source
linux-arm64CodeQL bundle when available. #4072v4.37.9Compare Source
gradle/gradle (gradle)
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 by
setup-gradleanddependency-submissionnow carry a top-level headingnaming the action, so the block stays attributable when another action's summary content lands in the
same job (#1058).
Updated defaults
wrapper-validation(368 → 373 entries)What's Changed
:wrappertask by @cobexer in #1064New Contributors
Full Changelog: gradle/actions@v6.3.0...v6.4.0
lint-staged/lint-staged (lint-staged)
v17.6.0Compare Source
Minor Changes
#1850
938d3f4- Task functions like{ title, task }can now use a logger functionlog()to emit output while the task runs. By default, the output will only be visible if the task fails, unless the--verboseoption was used. Additionally, when the task rejects, the error will be shown in the output.#1854
30562bc- lint-staged now stages changes to all tracked files modified by tasks, including files that weren’t originally staged or didn’t match the configured globs. This can happen when your task has side-effects, or it's a function that ignores the staged files like() => "prettier --write .".If you have unstaged changes in a file and the task also edits that file, your unstaged changes will be staged too. Use
--hide-unstagedto hide your changes while tasks run.Patch Changes
#1860
4296532- The assignment of staged files to lint-staged configuration files (when using multiple, for example in a monorepo) has been rewritten to be more efficient. As a reminder, each staged file is assigned to exactly one configuration (the closest one), even if that config doesn't match the file in its globs.#1861
c45f28a- Fix running parallel tasks for a single glob, when tasks are created by a function. Nesting one level of arrays inside an array of tasks will result in the inner tasks running in parallel. This behavior should now be consistent when creating tasks using functions. In the following exampleeslintandprettierwill run in parallel (for all files, when any JS files are staged):#1859
f0ea69d- Various performance improvements from skipping redundant internal Git calls.#1856
69d7d17- Partially staged changes are hidden in a uniquely-named patch file to avoid multiple invocations of lint-staged overwriting it. This makes it safer to run lint-staged in multiple worktrees at the same time.v17.5.1Compare Source
Patch Changes
#1852
bfcca94- Fix TypeScript issueTS1254fromdefineConfig()by changing the signature fromconstto afunction:v17.5.0Compare Source
Minor Changes
f9063b7- Lint-staged now refuses to run when files were staged with--intent-to-add, because Git stash doesn't support them. Previously this was an unhandled error.Patch Changes
#1848
d718ccc- Lint-staged now handles color support better in non-TTY streams, and honors theFORCE_COLORenvironment variable.#1845
7e5ece8- Updatetinyexec@1.3.1so that local binaries fromnode_modules/.binare resolved starting from the directory of each lint-staged configuration file (in monorepo setups). This behavior was broken inlint-staged@16.3.0where they were only resolved from the current working directory and up.#1845
eb8a4e3- Do not try to restore untracked files when using--hide-alland there is no initial commit yet.v17.4.1Compare Source
Patch Changes
efe5b63- This is a version-bump-only release because the previous version17.4.0was not published to npmjs.com due to problems with GitHub Actions and Changesets.Netflix/dgs-codegen (com.netflix.graphql.dgs.codegen:graphql-dgs-codegen-shared-core)
v8.7.0What's Changed
⭐ Improvements
🔨 Dependency Upgrades
mockito/mockito (org.mockito:mockito-junit-jupiter)
v5.24.0Compare Source
Changelog generated by Shipkit Changelog Gradle Plugin
5.24.0
toString()is not implemented (#3844)@Spyannotation (#3835)@Spy(#2740)lysine-dev/okio (com.squareup.okio:okio)
v3.18.22026-09-04
base64 strings to be encoded without padding, even though the previous and expected behavior is
to encode such strings with padding (
=characters). The bug impacts callers who compiledagainst Okio releases
< 3.18.0, and executed on Okio releases>= 3.18.DataDog/datadog-api-client-java (com.datadoghq:datadog-api-client)
v2.61.0Added
/api/v2/on-call/schedulesto a public ListOnCallSchedules operation #4302sensitive_dataandserverless_function_code_vulnerabilityto security finding notification API spec #4283Removed
Fixed
Changed
Deprecated
v2.60.0Added
Changed
Configuration
📅 Schedule: (UTC)
* 0-3 * * 1)🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, 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.