chore(deps): update weekly update#19216
Open
renovate[bot] wants to merge 1 commit into
Open
Conversation
renovate
Bot
changed the title
renovate
Bot
changed the title
renovate
Bot
force-pushed
the
renovate/weekly-update
branch
2 times, most recently
from
July 21, 2026 04:52
c84169a to
dcfb0af
Compare
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
There was a problem hiding this comment.
zizmor found more than 20 potential problems in the proposed changes. Check the Files changed tab for more details.
Pull request dashboard statusStatus last refreshed: 2026-07-22 01:50:00 UTC.
This automated status or its linked feedback items may be incorrect. If something looks wrong, report it with the result you expected. |
renovate
Bot
force-pushed
the
renovate/weekly-update
branch
from
July 21, 2026 15:59
dcfb0af to
4f97edf
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.
This PR contains the following updates:
v7.0.0→v7.0.1v5.5.0→v5.6.068868d0→201fbb81eeacc8→da9d3a489dc1a6→068a8f929d6dba→51cad805dc0f37→d044c297302d59→66c7f7a2e3bf0b→9e32024e17748c→8d11d0f7302d59→66c7f7a29d6dba→51cad80v4.37.0→v4.37.2v1.6.2→v1.6.3v4.2.0→v4.2.1a23b350→b841bb0b7f4819→3131b4cRelease Notes
actions/checkout (actions/checkout)
v7.0.1Compare Source
actions/setup-java (actions/setup-java)
v5.6.0Compare Source
What's Changed
Full Changelog: actions/setup-java@v5...v5.6.0
github/codeql-action (github/codeql-action)
v4.37.2Compare Source
config-fileinput that was introduced in CodeQL Action 4.37.0 is now enabled by default. In addition to the format described there, theremote=prefix can now be used to explicitly indicate that the input refers to a remote file. All previous input formats continue to be accepted as well. #4023v4.37.1Compare Source
graalvm/setup-graalvm (graalvm/setup-graalvm)
v1.6.3Compare Source
jdx/mise-action (jdx/mise-action)
v4.2.1: : Signed checksums and PATH export fixCompare Source
A small patch release with two user-facing fixes: mise downloads are now verified against minisign-signed release checksums by default, and the
envinput no longer leaks the runner'sPATHinto subsequent steps.Fixed
Verify mise downloads with signed checksums (#548) by @jdx
The action now embeds mise's minisign public key and verifies
SHASUMS256.txt.minisigbefore trusting any release checksums, then checks the downloaded mise binary's SHA256 against the verified list. This applies to both GitHub release archives (verified before extraction) and the defaultmise.jdx.devCDN path (verified against the signed checksum for the matching release asset). If a CDN download fails verification, the action warns and falls back to the signed GitHub release asset instead of installing an unverified binary.sha256input still works as an explicit override.2024.12.24(which predate minisign checksums) get a warning and skip signed verification rather than failing.download | tarfast path is replaced with a download-then-verify-then-extract flow.Thanks to @potiuk for the detailed threat-model writeup in #547.
Exclude
PATHfrom environment export (#556) by @jdxThe
envinput has always documented that "PATH modifications are not part of this", but since the switch tomise env --jsonin #252 (needed for redaction support), the action was exporting every string value returned by mise — including the computedPATH— intoGITHUB_ENV. That effectively snapshotted the runner's entirePATHinto subsequent steps and let[env] _.pathentries inmise.tomlleak past the action's own PATH management.exportMiseEnvnow skipsPATH(case-insensitive) when exporting JSON env vars, restoring the documented behavior. Normal mise env vars are still exported, and PATH continues to be managed by the action's own setup (e.g.add_shims_to_path). Fixes #555.Full Changelog: jdx/mise-action@v4.2.0...v4.2.1
Configuration
📅 Schedule: (UTC)
* 0-7 * * 2)🚦 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.