chore(deps): update all non-major dependencies#223
Merged
Conversation
![renovate-approve-2[bot]](https://avatars.githubusercontent.com/in/62175?s=60&v=4){kind=small}
![renovate-approve[bot]](https://avatars.githubusercontent.com/in/7394?s=60&v=4){kind=small}
Contributor
✅MegaLinter analysis: Success
See detailed reports in MegaLinter artifacts Your project could benefit from a custom flavor, which would allow you to run only the linters you need, and thus improve runtime performances. (Skip this info by defining
|
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
6 times, most recently
from
0e0c79f to
65d7417
Compare
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
65d7417 to
5915731
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
5915731 to
ec6d1e2
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
ec6d1e2 to
1bb901b
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
7 times, most recently
from
44bc803 to
e9d8646
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
e9d8646 to
e429458
Compare
Contributor
Author
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. |
Contributor
Trivy image scan report
|
| Package | ID | Severity | Installed Version | Fixed Version |
|---|---|---|---|---|
dpkg |
CVE-2026-2219 | UNKNOWN | 1.22.21 | 1.22.22 |
libc-bin |
CVE-2026-0861 | HIGH | 2.41-12+deb13u1 | 2.41-12+deb13u2 |
libc-bin |
CVE-2025-15281 | MEDIUM | 2.41-12+deb13u1 | 2.41-12+deb13u2 |
libc-bin |
CVE-2026-0915 | MEDIUM | 2.41-12+deb13u1 | 2.41-12+deb13u2 |
libc6 |
CVE-2026-0861 | HIGH | 2.41-12+deb13u1 | 2.41-12+deb13u2 |
libc6 |
CVE-2025-15281 | MEDIUM | 2.41-12+deb13u1 | 2.41-12+deb13u2 |
libc6 |
CVE-2026-0915 | MEDIUM | 2.41-12+deb13u1 | 2.41-12+deb13u2 |
libsqlite3-0 |
CVE-2025-7709 | MEDIUM | 3.46.1-7 | 3.46.1-7+deb13u1 |
No Misconfigurations found
Python
1 known vulnerabilities found (CRITICAL: 0 HIGH: 0 MEDIUM: 0 LOW: 1)
Show detailed table of vulnerabilities
| Package | ID | Severity | Installed Version | Fixed Version |
|---|---|---|---|---|
pip |
CVE-2026-1703 | LOW | 25.3 | 26.0 |
No Misconfigurations found
Contributor
Trivy image scan report
|
| Package | ID | Severity | Installed Version | Fixed Version |
|---|---|---|---|---|
dpkg |
CVE-2026-2219 | UNKNOWN | 1.22.21 | 1.22.22 |
libc-bin |
CVE-2026-0861 | HIGH | 2.41-12+deb13u1 | 2.41-12+deb13u2 |
libc-bin |
CVE-2025-15281 | MEDIUM | 2.41-12+deb13u1 | 2.41-12+deb13u2 |
libc-bin |
CVE-2026-0915 | MEDIUM | 2.41-12+deb13u1 | 2.41-12+deb13u2 |
libc6 |
CVE-2026-0861 | HIGH | 2.41-12+deb13u1 | 2.41-12+deb13u2 |
libc6 |
CVE-2025-15281 | MEDIUM | 2.41-12+deb13u1 | 2.41-12+deb13u2 |
libc6 |
CVE-2026-0915 | MEDIUM | 2.41-12+deb13u1 | 2.41-12+deb13u2 |
libsqlite3-0 |
CVE-2025-7709 | MEDIUM | 3.46.1-7 | 3.46.1-7+deb13u1 |
No Misconfigurations found
Python
1 known vulnerabilities found (MEDIUM: 0 LOW: 1 CRITICAL: 0 HIGH: 0)
Show detailed table of vulnerabilities
| Package | ID | Severity | Installed Version | Fixed Version |
|---|---|---|---|---|
pip |
CVE-2026-1703 | LOW | 25.3 | 26.0 |
No Misconfigurations found
Contributor
Trivy image scan report
|
| Package | ID | Severity | Installed Version | Fixed Version |
|---|---|---|---|---|
dpkg |
CVE-2026-2219 | UNKNOWN | 1.22.21 | 1.22.22 |
libc-bin |
CVE-2026-0861 | HIGH | 2.41-12+deb13u1 | 2.41-12+deb13u2 |
libc-bin |
CVE-2025-15281 | MEDIUM | 2.41-12+deb13u1 | 2.41-12+deb13u2 |
libc-bin |
CVE-2026-0915 | MEDIUM | 2.41-12+deb13u1 | 2.41-12+deb13u2 |
libc6 |
CVE-2026-0861 | HIGH | 2.41-12+deb13u1 | 2.41-12+deb13u2 |
libc6 |
CVE-2025-15281 | MEDIUM | 2.41-12+deb13u1 | 2.41-12+deb13u2 |
libc6 |
CVE-2026-0915 | MEDIUM | 2.41-12+deb13u1 | 2.41-12+deb13u2 |
libsqlite3-0 |
CVE-2025-7709 | MEDIUM | 3.46.1-7 | 3.46.1-7+deb13u1 |
No Misconfigurations found
Python
1 known vulnerabilities found (CRITICAL: 0 HIGH: 0 MEDIUM: 0 LOW: 1)
Show detailed table of vulnerabilities
| Package | ID | Severity | Installed Version | Fixed Version |
|---|---|---|---|---|
pip |
CVE-2026-1703 | LOW | 25.3 | 26.0 |
No Misconfigurations found
Contributor
|
🎉 This PR is included in version 1.11.18 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
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
2 participants
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:
v8.0.0→v8.0.1v7.3.1→v7.6.0v4.32.6→v4.34.1v4.0.0→v4.1.0v2.5.0→v2.6.1v2.15.1→v2.16.01.22.0→1.23.1Release Notes
actions/download-artifact (actions/download-artifact)
v8.0.1Compare Source
What's Changed
Full Changelog: actions/download-artifact@v8...v8.0.1
astral-sh/setup-uv (astral-sh/setup-uv)
v7.6.0: 🌈 Fetch uv from Astral's mirror by defaultCompare Source
Changes
We now default to download uv from
releases.astral.sh.This means by default we don't hit the GitHub API at all and shouldn't see any rate limits and timeouts any more.
🚀 Enhancements
🧰 Maintenance
⬆️ Dependency updates
v7.5.0: 🌈 Use `astral-sh/versions` as version providerCompare Source
No more rate-limits
This release addresses a long-standing source of timeouts and rate-limit failures in setup-uv.
Previously, the action resolved version identifiers like 0.5.x by iterating over available uv releases via the GitHub API to find the best match. In contrast, latest and exact versions such as 0.5.0 skipped version resolution entirely and downloaded uv directly.
The
manifest-fileinput was an earlier attempt to improve this. It allows providing an url to a file that lists available versions, checksums, and even custom download URLs. The action also shipped with such a manifest.However, because that bundled file could become outdated whenever new uv releases were published, the action still had to fall back to the GitHub API in many cases.
This release solves the problem by sourcing version data from Astral’s versions repository via the raw content endpoint:
https://raw.githubusercontent.com/astral-sh/versions/refs/heads/main/v1/uv.ndjson
By using the raw endpoint instead of the GitHub API, version resolution no longer depends on API authentication and is much less likely to run into rate limits or timeouts.
The
manifest-fileinput lets you override that source with your own URL, for example to test custom uv builds or alternate download locations.The manifest file must be in NDJSON format, where each line is a JSON object representing a version and its artifacts. For example:
{"version":"0.10.7","artifacts":[{"platform":"x86_64-unknown-linux-gnu","variant":"default","url":"https://example.com/uv-x86_64-unknown-linux-gnu.tar.gz","archive_format":"tar.gz","sha256":"..."}]} {"version":"0.10.6","artifacts":[{"platform":"x86_64-unknown-linux-gnu","variant":"default","url":"https://example.com/uv-x86_64-unknown-linux-gnu.tar.gz","archive_format":"tar.gz","sha256":"..."}]}Changes
🚀 Enhancements
📚 Documentation
v7.4.0: 🌈 Add riscv64 architecture support to platform detectionCompare Source
Changes
Thank you @luhenry for adding support for riscv64 arch
🚀 Enhancements
🧰 Maintenance
⬆️ Dependency updates
github/codeql-action (github/codeql-action)
v4.34.1Compare Source
v4.34.0Compare Source
none. We expect this rollout to be complete by the end of April 2026. #3584v4.33.0Compare Source
Upcoming change: Starting April 2026, the CodeQL Action will skip collecting file coverage information on pull requests to improve analysis performance. File coverage information will still be computed on non-PR analyses. Pull request analyses will log a warning about this upcoming change. #3562
To opt out of this change:
github-codeql-file-coverage-on-prsand the type "True/false", then set this property totruein the repository's settings. For more information, see Managing custom properties for repositories in your organization. Alternatively, if you are using an advanced setup workflow, you can set theCODEQL_ACTION_FILE_COVERAGE_ON_PRSenvironment variable totruein your workflow.CODEQL_ACTION_FILE_COVERAGE_ON_PRSenvironment variable totruein your workflow.CODEQL_ACTION_FILE_COVERAGE_ON_PRSenvironment variable totruein your workflow.Fixed a bug which caused the CodeQL Action to fail loading repository properties if a "Multi select" repository property was configured for the repository. #3557
The CodeQL Action now loads custom repository properties on GitHub Enterprise Server, enabling the customization of features such as
github-codeql-disable-overlaythat was previously only available on GitHub.com. #3559Once private package registries can be configured with OIDC-based authentication for organizations, the CodeQL Action will now be able to accept such configurations. #3563
Fixed the retry mechanism for database uploads. Previously this would fail with the error "Response body object should not be disturbed or locked". #3564
A warning is now emitted if the CodeQL Action detects a repository property whose name suggests that it relates to the CodeQL Action, but which is not one of the properties recognised by the current version of the CodeQL Action. #3570
sigstore/cosign-installer (sigstore/cosign-installer)
v4.1.0Compare Source
What's Changed
We recommend updating as soon as possible as this includes bug fixes for Cosign. We also recommend removing
with: cosign-releaseand strongly discourage usingcosign-releaseunless you have a specific reason to use an older version of Cosign.Full Changelog: sigstore/cosign-installer@v4.0.0...v4.1.0
softprops/action-gh-release (softprops/action-gh-release)
v2.6.1Compare Source
2.6.1is a patch release focused on restoring linked discussion thread creation whendiscussion_category_nameis set. It fixes#764, where the draft-first publish flowstopped carrying the discussion category through the final publish step.
If you still hit an issue after upgrading, please open a report with the bug template and include a minimal repro or sanitized workflow snippet where possible.
What's Changed
Bug fixes 🐛
v2.6.0Compare Source
2.6.0is a minor release centered onprevious_tagsupport forgenerate_release_notes,which lets workflows pin GitHub's comparison base explicitly instead of relying on the default range.
It also includes the recent concurrent asset upload recovery fix, a
working_directorydocs sync,a checked-bundle freshness guard for maintainers, and clearer immutable-prerelease guidance where
GitHub platform behavior imposes constraints on how prerelease asset uploads can be published.
If you still hit an issue after upgrading, please open a report with the bug template and include a minimal repro or sanitized workflow snippet where possible.
What's Changed
Exciting New Features 🎉
Bug fixes 🐛
Other Changes 🔄
v2.5.3Compare Source
2.5.3is a patch release focused on the remaining path-handling and release-selection bugs uncovered after2.5.2.It fixes
#639,#571,#280,#614,#311,#403, and#368.It also adds documentation clarifications for
#541,#645,#542,#393, and#411,where the current behavior is either usage-sensitive or constrained by GitHub platform limits rather than an action-side runtime bug.
If you still hit an issue after upgrading, please open a report with the bug template and include a minimal repro or sanitized workflow snippet where possible.
What's Changed
Bug fixes 🐛
Other Changes 🔄
preserve_order, and special-character asset filename behaviorFull Changelog: softprops/action-gh-release@v2...v2.5.3
v2.5.2Compare Source
2.5.2is a patch release focused on the remaining release-creation and prerelease regressions in the2.5.xbug-fix cycle.It fixes
#705, fixes#708, fixes#740, fixes#741, and fixes#722.Regression testing covers the shared-tag race, prerelease event behavior, dotfile asset labels,
same-filename concurrent uploads, and blocked-tag cleanup behavior.
If you still hit an issue after upgrading, please open a report with the bug template and include a minimal repro or sanitized workflow snippet where possible.
What's Changed
Bug fixes 🐛
New Contributors
Full Changelog: softprops/action-gh-release@v2...v2.5.2
v2.5.1Compare Source
2.5.1is a patch release focused on regressions introduced in2.5.0and on release lookup reliability.It fixes
#713, addresses#703, and fixes#724. Regression testing shows thatcurrent
masterno longer reproduces the finalize-race behavior reported in#704and#709.What's Changed
Bug fixes 🐛
Other Changes 🔄
New Contributors
Full Changelog: softprops/action-gh-release@v2...v2.5.1
step-security/harden-runner (step-security/harden-runner)
v2.16.0Compare Source
What's Changed
Full Changelog: step-security/harden-runner@v2.15.1...v2.16.0
zizmorcore/zizmor (zizmor)
v1.23.1Compare Source
Bug Fixes 🐛🔗
v1.23.0Compare Source
New Features 🌈🔗
New audit: secrets-outside-env detects usage of the secrets context in jobs that don't have a corresponding environment (#1599)
New audit: superfluous-actions detects usage of actions that perform operations already provided by GitHub's own runner images (#1618)
Enhancements 🌱🔗
zizmor's LSP mode is now configuration-aware, and will load configuration files relative to workspace roots (#1555)
zizmor now reads the GITHUB_TOKEN environment variable as an alias/equivalent for GH_TOKEN (#1566)
zizmor now supports inputs that contain duplicated anchor names (#1575)
zizmor now flags missing cooldowns on opentofu ecosystem definitions in Dependabot (again) (#1586)
zizmor now reads the ZIZMOR_GITHUB_TOKEN environment variable as an alias/equivalent for GH_TOKEN and GITHUB_TOKEN (#1641)
The SARIF output format now adds zizmor/confidence, zizmor/persona and zizmor/severity to the properties of findings (#1656)
Added awalsh128/cache-apt-pkgs-action as a cache-aware action to the cache-poisoning audit (#1708)
Changes⚠️ 🔗
SARIF categories have been regraded. zizmor's "medium" is changed from SARIF's "warning" to "low" (#1635)
Bug Fixes 🐛🔗
Fixed a bug where zizmor would crash on uses: clauses containing non-significant whitespace while performing the unpinned-uses audit (#1544)
Fixed a bug in yamlpath where sequences containing anchors were splatted instead of being properly nested (#1557)
Many thanks to @DarkaMaul for implementing this fix!
Fixed a bug in yamlpath where anchor prefixes in sequences and mapping were not stripped during path queries (#1562)
Fixed a bug where "merge into" autofixes would produce incorrect patches in the presence of multi-byte Unicode characters (#1581)
Many thanks to @ManuelLerchnerQC for implementing this fix!
Fixed a bug where the template-injection audit would produce duplicated pedantic-only findings (#1589)
Fixed a bug where the obfuscation audit would produce incorrect autofixes for a subset of constant-reducible expressions (#1597)
Fixed a bug where the obfuscation audit would fail to apply fixes to a subset of inputs with leading whitespace (#1597)
Fixed a bug where the concurrency-limits audit would incorrectly flag reusable-only workflows as needing a concurrency: key (#1620)
Fixed a bug where the known-vulnerable-actions audit would fail when applying some fixes (#1640)
Many thanks to @reubenwong97 for implementing this fix!
Fixed a bug where the pre-commit ecosystem was not recognized in Dependabot configuration files (#1637)
Fixed a bug where the template-injection audit would incorrectly flag github.triggering_actor as an injection risk in the default persona (#1645)
Fixed a bug where zizmor's expression parser did not correctly handle number literals in GitHub Actions expressions (#1625)
Fixed a bug where the template-injection audit would crash on some forms of multi-line expressions (#1669)
Fixed a bug where deserialization of a workflow containing fractional minutes would fail (#1675)
Fixed a bug where deserialization of a workflow where a workflow_run with a scalar types would fail (#1676)
Fixed a bug where zizmor would crash on workflows containing bare numeric values in if: conditions (#1683)
Fixed a bug where GitHub Actions expression string comparisons were not case-insensitive (#1687)
Configuration
📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, only on Monday ( * 0-3 * * 1 ) (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ 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.