Repository navigation
chore(deps): update github actions - #151
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. |
renovate
Bot
force-pushed
the
renovate/github-actions
branch
from
November 8, 2026 02:13
84a916a to
e5cccb4
Compare
renovate
Bot
force-pushed
the
renovate/github-actions
branch
4 times, most recently
from
November 11, 2026 15:02
396ea04 to
bdf5f69
Compare
renovate
Bot
force-pushed
the
renovate/github-actions
branch
from
November 11, 2026 23:27
bdf5f69 to
ddd829a
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:
v8.4.0→v8.4.1v1.0.266→v1.0.269v1.0.275(+5)v4.39.1→v4.39.3v5.2.5→v5.2.7v5.2.8Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
SonarSource/sonarqube-scan-action
v8.4.1Compare Source
What's Changed
New Contributors
Full Changelog: SonarSource/sonarqube-scan-action@v8.4.0...v8.4.1
anthropics/claude-code-action
v1.0.269Compare Source
Full Changelog: anthropics/claude-code-action@v1.0.268...v1.0.269
v1.0.268Compare Source
Full Changelog: anthropics/claude-code-action@v1.0.267...v1.0.268
v1.0.267Compare Source
Full Changelog: anthropics/claude-code-action@v1.0.266...v1.0.267
github/codeql-action
v4.39.3Compare Source
v4.39.2Compare Source
CODEQL_ACTION_CLEANUP_TRAP_CACHESenvironment variable has been removed, as announced in the release notes for CodeQL Action 4.35.2. TheanalyzeAction now warns if this environment variable is set. If you used TRAP cache cleanup to limit Actions cache usage, we recommend disabling TRAP caching by passing thetrap-caching: falseinput to theinitAction. #4243jdx/mise-action
v5.2.7: : Retry failed mise downloads with backoff and show the HTTP statusCompare Source
When the action can't download mise, the log now shows the HTTP status and host for each failed attempt. Retries wait longer between attempts, so a short GitHub outage is less likely to fail the job.
Fixed
Download failures now show what went wrong, and brief outages are retried for longer. Before this release, a failed mise download logged only
The process '/usr/bin/curl' failed with exit code 22and retried five times with a fixed 2-second wait. From that message you couldn't tell a rate limit from a missing asset or a server error. Each failed attempt now logs the HTTP status and the host that answered:The wait between attempts doubles from about 2s up to a 30s cap, with random jitter, so the five retries cover roughly a minute. Only transient failures are retried: connection errors and timeouts, and HTTP 408, 429 and 5xx responses. A 404, any other 4xx, or a local file-write error fails at once. The log shows only the host and file name of each URL, never signed query strings or curl/wget stderr. Partial files are deleted before the next attempt. wget now runs with
--tries=1, so its own 20-retry default no longer stacks on top of the action's retries. This applies to every download the action makes: the release archive, checksums and the packslip bundle. Checksum and signature verification are unchanged, and there are no new inputs. (#722 by @jdx, fixes #721)Changed
Full Changelog: jdx/mise-action@v5.2.6...v5.2.7
v5.2.6: : Fix step hanging after a failed cache restoreCompare Source
The action now exits as soon as its work is done. Before this release, a cache restore that failed during the download could leave the step running for up to ten minutes after setup had finished.
Fixed
getaddrinfo EAI_AGAIN, the action logged a warning, installed the tools and saved the cache, then stopped producing output. The step stayed in progress until the job was cancelled or a timer inside@actions/cachefired after 10 minutes. That timer is left running when a download fails (actions/toolkit#2470), and it kept the Node process alive. The action now exits explicitly after both the main step and the post step finish. It waits up to 5 seconds for log output to flush, then exits. The exit code set by any earlier failure is kept. Errors that aren'tErrorobjects now mark the step as failed with their message. Before, they caused an unhandled rejection. (#718 by @jdx and @kjanat, fixes #717)Full Changelog: jdx/mise-action@v5.2.5...v5.2.6
Configuration
📅 Schedule: (in timezone Europe/Berlin)
🚦 Automerge: Enabled.
♻ 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.