Skip to content

chore(deps): update github actions - #151

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/github-actions
Open

renovate[bot] wants to merge 1 commit into
mainfrom
renovate/github-actions

Conversation

@renovate

@renovate renovate Bot commented Nov 7, 2026 •

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Type Update Change Pending
SonarSource/sonarqube-scan-action action minor v8.4.0 → v8.5 v8.5.0
anthropics/claude-code-action action patch v1.0.266 → v1.0.275 v1.0.280 (+4)
github/codeql-action action patch v4.39.1 → v4.39.3
jdx/mise-action action patch v5.2.5 → v5.2.8 v5.2.9

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Release Notes

SonarSource/sonarqube-scan-action

v8.5.0

Compare Source

What's Changed

Full Changelog: SonarSource/sonarqube-scan-action@v8.4.1...v8.5.0

v8.4.1

Compare Source

What's Changed
New Contributors

Full Changelog: SonarSource/sonarqube-scan-action@v8.4.0...v8.4.1

anthropics/claude-code-action

v1.0.275

Compare Source

What's Changed
Other changes

Full Changelog: anthropics/claude-code-action@v1.0.274...v1.0.275

v1.0.274

Compare Source

What's Changed
Other changes

Full Changelog: anthropics/claude-code-action@v1.0.273...v1.0.274

v1.0.273: (breaking changes)

Compare Source

What's Changed
⚠️ Breaking changes
Other changes

Full Changelog: anthropics/claude-code-action@v1.0.272...v1.0.273

⚠️ Upgrade notes: new security defaults

This release tightens what a Claude session can do, especially on content from people without write access. Workflows on @v1 get these changes automatically. Most keep working as they are, but check the items below if yours runs tests on outside pull requests, uses later steps after the action, or relies on --allowedTools as a strict list.

Sessions start in auto mode

A safety review now decides tool calls that no allow rule covers. Calls that used to be denied can run if the review passes, so --allowedTools is no longer a strict list. Workflows with a prompt can also edit workspace files without an allow rule.

Opt out: set the earlier mode in claude_args: --permission-mode acceptEdits for @claude mentions, or --permission-mode default for workflows with a prompt.

Sessions keep the earlier defaults if you set allowed_non_write_users, allowed_bots, a custom ANTHROPIC_BASE_URL or path_to_claude_code_executable. The same applies if your settings input is a file path, or sets a base URL or another permission mode.

Code-running commands are denied on outside pull requests

If a pull request's author doesn't have write access, common commands such as npm test and bun install are denied, even if claude_args allows them. The run still succeeds, so check the log for a warning.

Opt out: restrict_untrusted_prs: false. This lets code from that pull request run in a job that holds your workflow's tokens.

Only trusted text and runs start a session
  • Slash commands and the trusted request come only from text the person who triggered the run wrote. Claude still reads a labeled or assigned issue's body for context.
  • Editing or deleting someone else's comment or review no longer starts a run.
  • With prompt and track_progress, label_trigger and assignee_trigger now apply.
  • workflow_run also checks the owner of the fork the run came from.
  • A run started by a bot's activity on a pull request also needs that pull request's author to have write access or be an allowed bot.

Adjust:

  • If your workflow filters labels itself, set label_trigger to your label, or to "" to accept any label.
  • For workflow_run on outside contributions, add those users to allowed_non_write_users and pass github_token.

There's no opt-out for the rest.

A session can't leave anything behind for later steps

GITHUB_ENV, GITHUB_PATH and git config are restored when the session ends, so a session's changes to them no longer reach later steps. Token revocation also ignores ~/.curlrc, including a proxy set there.

Git hooks are also off from before the checkout on pull requests covered by restrict_untrusted_prs, so a push Claude makes on one of those won't upload Git LFS objects.

Adjust: pass values to later steps with GITHUB_OUTPUT or --json-schema. There's no opt-out.

No token in .git/config when allowed_bots is set

These workflows now use the same credential helper as allowed_non_write_users, and it only answers for your GitHub server.

Adjust: a later step that pushes through origin, or fetches from it on a private repository, needs its own credentials: GH_TOKEN, GIT_ASKPASS, a credential saved for the username x-access-token, or its own remote URL. There's no opt-out.

Stricter git commands in @claude runs
  • Commits go through a wrapper that rejects flags outside a short list, including --amend, --no-verify, --author and flags that read a file.
  • Pushes can't be forced and only update the branch the session was set up on: a new branch, or the open pull request's branch.
  • A deny rule for git commit or git push must be in claude_args to cover these wrappers. One in a settings file doesn't.

Opt out: add your own rule in claude_args, such as Bash(git commit:*) or Bash(git push:*). This brings back what the wrappers block for that workflow.

Signed commits from prompt runs go to their own branch

With use_commit_signing, a run on an issue now commits to issue-N. A run on a pull request commits to its branch, or to pr-N if that branch isn't known to be in this repository. They used to reach the default branch or a branch named by a fork.

Opt out: set CLAUDE_BRANCH in the step's env to choose the branch.

v1.0.272

Compare Source

What's Changed

Full Changelog: anthropics/claude-code-action@v1.0.271...v1.0.272

v1.0.271

Compare Source

Full Changelog: anthropics/claude-code-action@v1.0.270...v1.0.271

v1.0.270

Compare Source

What's Changed
  • release: push tags with the release deploy key (enables tag-ruleset enforcement) by @​chrnorm in #​1650
New Contributors

Full Changelog: anthropics/claude-code-action@v1.0.269...v1.0.270

v1.0.269

Compare Source

Full Changelog: anthropics/claude-code-action@v1.0.268...v1.0.269

v1.0.268

Compare Source

Full Changelog: anthropics/claude-code-action@v1.0.267...v1.0.268

v1.0.267

Compare Source

Full Changelog: anthropics/claude-code-action@v1.0.266...v1.0.267

github/codeql-action

v4.39.3

Compare Source

  • Fixed diff-informed alert filtering incorrectly removing alerts in changed files whose paths contain spaces, special characters, or non-ASCII characters. #​4283

v4.39.2

Compare Source

  • Update default CodeQL bundle version to 2.27.4. #​4284
  • Upcoming breaking change: CodeQL version 2.22.3 and earlier were discontinued on 16 October 2026 alongside GitHub Enterprise Server 3.18, and will be unsupported by the next minor release of the CodeQL Action. Added a deprecation warning for customers using these versions of CodeQL. #​4266
  • Starting with macOS 27 and Xcode 27, traced analyses are unsupported. See this blog post for more information. The CodeQL Action will now try to identify if a workflow is about to perform a traced analysis on version 27 or above of macOS or Xcode. If so, the CodeQL Action will emit a corresponding warning that will also be visible on the Tool Status Page. This check will be rolled out following this release of the CodeQL Action. #​4221
  • The undocumented TRAP cache cleanup feature that could be enabled using the CODEQL_ACTION_CLEANUP_TRAP_CACHES environment variable has been removed, as announced in the release notes for CodeQL Action 4.35.2. The analyze Action 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 the trap-caching: false input to the init Action. #​4243
jdx/mise-action

v5.2.8: : Fix mise install on Windows when MISE_DATA_DIR is on another drive

Compare Source

On Windows, the action can now install mise when MISE_DATA_DIR is on a different drive from the temporary directory. Before this fix, the install failed with EXDEV: cross-device link not permitted.

Fixed
  • Installing mise on Windows no longer fails when MISE_DATA_DIR is on another drive. On hosted windows-2025 runners, the workspace and RUNNER_TEMP are on D:, but the action downloaded mise to os.tmpdir() on C:. If MISE_DATA_DIR pointed into the workspace, moving mise.exe into place failed:

    ##[error]EXDEV: cross-device link not permitted, rename 'C:\Users\RUNNER~1\AppData\Local\Temp\mise-action-…\extract\mise\bin\mise.exe' -> 'D:\a\…\tool-cache\mise\bin\mise.exe'
    

    The action now downloads to RUNNER_TEMP when that variable is set and the directory exists. Otherwise it falls back to the system temp directory. If moving mise.exe, mise-shim.exe or a raw mise binary still crosses drives, the action copies the file and then deletes the original. This also covers self-hosted runners where RUNNER_TEMP is on a different drive from the data directory. Setups that use the default data directory were not affected. If you set TEMP and TMP to ${{ runner.temp }} to work around this, you can remove those settings. (#​732 by @​jdx and @​HengYangDS, fixes #​730)

New Contributors

Full Changelog: jdx/mise-action@v5.2.7...v5.2.8

v5.2.7: : Retry failed mise downloads with backoff and show the HTTP status

Compare 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 22 and 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:

    Download attempt 1/6 failed: Could not download github.com/…/mise-v2026.10.21-linux-x64.tar.zst (HTTP 503 from github.com). Retrying in 3.4 seconds.
    

    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

  • packslip, which the action uses to verify downloaded mise releases, is updated from 1.11.0 to 1.11.2. This version includes upstream hardening of its verifier checks. (#​726)

Full Changelog: jdx/mise-action@v5.2.6...v5.2.7

v5.2.6: : Fix step hanging after a failed cache restore

Compare 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
  • A failed cache restore no longer leaves the step hanging. If the mise cache download failed partway through, for example with 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/cache fired 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't Error objects 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)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 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.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate
renovate Bot requested a review from a team as a code owner November 7, 2026 21:40
@renovate
renovate Bot enabled auto-merge (squash) November 7, 2026 21:40
@codecov

codecov Bot commented Nov 7, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ All tests successful. No failed tests found.

@renovate
renovate Bot force-pushed the renovate/github-actions branch from 84a916a to e5cccb4 Compare November 8, 2026 02:13
@renovate renovate Bot changed the title chore(deps): update jdx/mise-action action to v5.2.6 chore(deps): update github actions Nov 8, 2026
@renovate
renovate Bot force-pushed the renovate/github-actions branch 7 times, most recently from 51d9898 to 0055d94 Compare November 15, 2026 07:02
@renovate
renovate Bot force-pushed the renovate/github-actions branch from 0055d94 to 7691e6a Compare November 17, 2026 21:00
- name: SonarQube Scan
if: ${{ !cancelled() && (env.GITHUB_WORKFLOW_RUNTIME != 'ACT') }}
uses: SonarSource/sonarqube-scan-action@4d1dc0c91ee400dcf8a6dddf2f705ac36542e304 # v8.4.0
uses: SonarSource/sonarqube-scan-action@59202af334b4ba7b5db01b701b8e79f8b3bef0f4 # v8.5

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚫 [pinact] reported by reviewdog 🐶
Action should be pinned: uses: SonarSource/sonarqube-scan-action@59202af # v8.5 -> uses: SonarSource/sonarqube-scan-action@59202af # v8.5.0

Suggested change
uses: SonarSource/sonarqube-scan-action@59202af334b4ba7b5db01b701b8e79f8b3bef0f4 # v8.5
uses: SonarSource/sonarqube-scan-action@59202af334b4ba7b5db01b701b8e79f8b3bef0f4 # v8.5.0

- name: SonarQube Scan
if: ${{ !cancelled() && (env.GITHUB_WORKFLOW_RUNTIME != 'ACT') }}
uses: SonarSource/sonarqube-scan-action@4d1dc0c91ee400dcf8a6dddf2f705ac36542e304 # v8.4.0
uses: SonarSource/sonarqube-scan-action@59202af334b4ba7b5db01b701b8e79f8b3bef0f4 # v8.5

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚫 [pinact] reported by reviewdog 🐶
Action should be pinned: uses: SonarSource/sonarqube-scan-action@59202af # v8.5 -> uses: SonarSource/sonarqube-scan-action@59202af # v8.5.0

Suggested change
uses: SonarSource/sonarqube-scan-action@59202af334b4ba7b5db01b701b8e79f8b3bef0f4 # v8.5
uses: SonarSource/sonarqube-scan-action@59202af334b4ba7b5db01b701b8e79f8b3bef0f4 # v8.5.0

@renovate
renovate Bot force-pushed the renovate/github-actions branch from 7691e6a to d7b7558 Compare November 18, 2026 05:23
@sonarqubecloud

Copy link
Copy Markdown

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants