Skip to content

chore(deps): update github actions - #308

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 Aug 17, 2026 •

Copy link
Copy Markdown
Contributor

Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Type Update Change
actions/create-github-app-token action minor v3.2.0 → v3.3.0
actions/deploy-pages action patch v5.0.0 → v5.0.1
actions/download-artifact action patch v8.0.1 → v8.0.2
actions/setup-python action minor v7.0.0 → v7.1.0
actions/upload-artifact action patch v7.0.1 → v7.0.2
anchore/sbom-action action patch v0.24.0 → v0.24.3
codecov/codecov-action action minor v7.0.0 → v7.1.1
docker/build-push-action action minor v7.3.0 → v7.4.0
docker/login-action action minor v4.6.0 → v4.8.0
docker/setup-buildx-action action minor v4.2.0 → v4.4.1
github/codeql-action action minor v4.37.6 → v4.39.3
helm/kind-action action minor v1.14.0 → v1.15.2
jdx/mise uses-with minor 2026.8.3 → 2026.11.2
jdx/mise-action action minor v4.2.4 → v4.3.0
ossf/scorecard-action action minor v2.4.4 → v2.5.0
sigstore/cosign-installer action patch v4.1.2 → v4.1.3
softprops/action-gh-release action patch v3.0.2 → v3.0.4

Release Notes

actions/create-github-app-token

v3.3.0

Compare Source

Features
Bug Fixes
  • deps: bump nested undici from 6.24.0 to 6.29.0 (#​403) (12461a3)
  • deps: bump the production-dependencies group across 1 directory with 3 updates (#​395) (a69c19d)
actions/deploy-pages

v5.0.1

Compare Source

Changelog


See details of all code changes since previous release.

⚠️ For use with products other than GitHub.com, such as GitHub Enterprise Server, please consult the compatibility table.

actions/download-artifact

v8.0.2

Compare Source

What's Changed

New Contributors

Full Changelog: actions/download-artifact@v8.0.1...v8.0.2

actions/setup-python

v7.1.0

Compare Source

What's Changed
Enhancements
Dependency Upgrade
New Contributors

Full Changelog: actions/setup-python@v7.0.0...v7.1.0

actions/upload-artifact

v7.0.2

Compare Source

What's Changed
  • Improves artifact download retries when the service returns HTTP 429 (rate limiting), including honoring valid Retry-After headers.
  • Updates @​actions/artifact to v6.3.1.
New Contributors

Full Changelog: actions/upload-artifact@v7.0.1...v7.0.2

anchore/sbom-action

v0.24.3

Compare Source

Added Features
Bug Fixes

(Full Changelog)

v0.24.2

Compare Source

Added Features
Additional Changes

(Full Changelog)

v0.24.1

Compare Source

codecov/codecov-action

v7.1.1

Compare Source

What's Changed

Full Changelog: codecov/codecov-action@v7.1.0...v7.1.1

v7.1.0

Compare Source

What's Changed

Full Changelog: codecov/codecov-action@v7.0.0...v7.1.0

docker/build-push-action

v7.4.0

Compare Source

Full Changelog: docker/build-push-action@v7.3.0...v7.4.0

docker/login-action

v4.8.0

Compare Source

Full Changelog: docker/login-action@v4.7.0...v4.8.0

v4.7.0

Compare Source

Full Changelog: docker/login-action@v4.6.0...v4.7.0

docker/setup-buildx-action

v4.4.1

Compare Source

Full Changelog: docker/setup-buildx-action@v4.4.0...v4.4.1

v4.4.0

Compare Source

Full Changelog: docker/setup-buildx-action@v4.3.0...v4.4.0

v4.3.0

Compare Source

Full Changelog: docker/setup-buildx-action@v4.2.0...v4.3.0

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

v4.39.1

Compare Source

v4.39.0

Compare Source

  • Breaking change: Bump the minimum required CodeQL bundle version to 2.20.7. #​4205
  • The codeql-action/analyze step now validates that a correct argument for the checkout_path input has been provided. The checkout_path input must be set to the path where the repository that is being analyzed is checked out at on the runner, if that path is something other than the workspace root. If the path does not point to a repository checkout or is different from the path that was used by codeql-action/init, then the CodeQL Action now produces a warning. #​4148
  • Resolved an issue with third-party caching implementations that prevented caches from being restored correctly. #​4206
  • The codeql-action/start-proxy step that is used in Code Scanning Default Setup now finds CodeQL releases using the same logic as codeql-action/init. This primarily benefits customers who are using GitHub instances other than github.com where the codeql-action/start-proxy step may previously have been unable to locate recent releases and ended up using outdated versions of the private registry authentication proxy as a result. #​4198

v4.38.3

Compare Source

  • Upcoming breaking change: CodeQL version 2.21.2 and earlier were discontinued on 24 September 2026 alongside GitHub Enterprise Server 3.17, and will be unsupported by the next minor release of the CodeQL Action. Added a deprecation warning for customers using these versions of CodeQL. #​4188
  • Update default CodeQL bundle version to 2.27.2. #​4203
  • Fixed a bug where the decision of whether to use a per-language bundle did not account for custom configurations that reference queries outside of compiled CodeQL packs. This issue was caught during internal testing and did not affect any customer repositories. We will resume the roll out of per-language bundles in the coming weeks. #​4184

v4.38.2

Compare Source

v4.38.1

Compare Source

  • The CodeQL Action now has experimental support for CodeQL releases for which per-language bundles are available. Per-language bundles support analysis for a single language and are therefore smaller than the combined bundles that allow analysis for all supported languages. As a result, per-language bundles take up less space on disk and are faster to download. We expect to roll this change out to everyone in the coming weeks. #​4146

v4.38.0

Compare Source

  • On GitHub-hosted runners, the CodeQL Action now deletes unused CodeQL bundles from the toolcache before downloading a different bundle, which frees up disk space for the analysis. We expect to roll this change out to everyone in September. #​4124
  • The CodeQL Action now supports CodeQL releases that are compatible with Linux Arm64 and downloads the native linux-arm64 CodeQL bundle when available. #​4072
  • Update default CodeQL bundle version to 2.27.0. #​4129

v4.37.9

Compare Source

v4.37.8

Compare Source

No user facing changes.

v4.37.7

Compare Source

helm/kind-action

v1.15.2

Compare Source

What's Changed

New Contributors

Full Changelog: helm/kind-action@v1.15.1...v1.15.2

v1.15.1

Compare Source

What's Changed

  • feat: add version_file input to read the kind version from a file by @​somaz94 in #​162
  • chore: bump kubectl to v1.37.1 and cloud-provider-kind to v0.12.0 by @​cpanato in #​170

New Contributors

Full Changelog: helm/kind-action@v1.15.0...v1.15.1

v1.15.0

Compare Source

What's Changed

New Contributors

Full Changelog: helm/kind-action@v1.14.0...v1.15.0

jdx/mise

v2026.11.2: : Task tags, summary output, JSON run reports, and mise run --at

Compare Source

This release adds four mise run features that help CI scripts and coding agents: tags for selecting tasks, a summary output style that only shows failures, a JSON run report, and --at for running tasks at another git revision. It also fixes problems with safe-mode lockfiles, symlink-each dotfiles, shims and shell completion.

Added

  • Task tags. You can label tasks with tags, then run every task that has a tag with mise run --tag. A tag can be a string or a list. File tasks set them with #MISE tags=[...], and templates add their tags to the tasks that extend them. You can repeat --tag, and a task matches if it has any of the given tags. Dependencies run whatever their tags are. If you also give a pattern, such as mise run --tag slow 'test:*', mise runs only the matching tasks that have the tag. mise tasks ls --tag filters the task list, and tasks ls --json, tasks info and the MCP task list now include tags. #​15406 (@​jdx)

    [tasks."lint:docs"]
    run = "markdownlint docs"
    tags = ["lint", "docs"]
    
    [tasks."test:e2e"]
    run = "./e2e/run"
    tags = ["test", "slow"]
    mise run --tag lint
    mise tasks ls --tag slow
  • summary task output style. mise holds each task's output until the task ends. A task that passed prints one line, such as [unit] passed in 4.2s. A task that failed prints everything it wrote. Tasks that mise stopped print [name] cancelled. This style is opt-in: use --output summary, MISE_TASK_OUTPUT=summary, task.output, or a task's output. mise keeps up to 64 KiB of output per task and drops the oldest output past that. A long-running task such as a dev server prints nothing until it exits, so give those tasks output = "interleave". #​15403 (@​jdx)

    $ mise run --output summary test
    [lint] $ cargo clippy -- -D warnings
    [lint] error: unused variable: `x`
    [unit] passed in 4.2s
    [lint] ERROR task failed
  • JSON run reports. mise run --report-file <PATH>, or MISE_TASK_REPORT_FILE, writes a JSON report when the run ends. This happens whether the run passes, fails, is interrupted or hits --timeout.

    • The report has the run's status (passed, failed, cancelled or timed_out) and every scheduled task, dependencies included.
    • Each task has its status (passed, failed, cancelled, skipped, cached or not_run), exit code, duration and timestamps.
    • Task arguments are redacted the same way as in terminal output.
    • The flag can't be combined with --dry-run. Tasks don't inherit the variable, so a nested mise run can't overwrite the outer report.

    #​15405 (@​jdx)

  • mise run --at REV. Runs tasks at another git revision without touching your checkout. mise checks the revision out into a temporary detached worktree, runs the task with that revision's own config and tasks, then removes the worktree. It also removes it after a failure, a timeout or Ctrl-C. --at-setup CMD prepares the worktree first, for example by installing dependencies.

    • Submodules are initialized.
    • Tasks and the setup command get MISE_RUN_AT_SOURCE (your checkout) and MISE_RUN_AT_REV (the commit).
    • Config at that revision gets your main checkout's trust, and you can't bypass this with a prompt or --yes.
    • Paranoid mode always refuses a config at that revision.

    #​15410 (@​jdx)

    mise run --at main test
    mise run --at HEAD~1 --at-setup "npm ci" test

Fixed

  • Lockfiles and safe mode
    • MISE_SAFE=1 MISE_LOCKED=1 mise install works again for node, python and go when mise.lock has their checksums. It used to fail with "No lockfile URL found". These tools now work out their own download URL and check it against the locked checksum. If safe mode is the reason a URL is missing, the error now says so. #​15392 (@​jdx)
    • npm: tools locked through aube now install in safe mode and in untrusted projects. mise keeps the lockfile's dependency graph if it only fetches from the registry using integrity hashes. Graphs that name tarball URLs, git sources or local paths are still dropped. #​15401 (@​jdx)
    • mise lock java@temurin-27 no longer rewrites java = "temurin-26" to the broken temurin-temurin. It now writes temurin-27, with the same precision as the original request. Switching vendor at the same version, as in java@zulu-26, is saved too. #​15386 (@​jdx)
    • When mise lock tool@3.0.1 changes tool = "2" to tool = "3" in the config, the lockfile entry now records "3", the request the config holds, instead of "3.0.1". Before, later lookups for that request couldn't find the entry. #​15404 (@​jdx)
  • Dotfiles and bootstrap
    • mise bootstrap now writes mise's own config files first and plans the rest of the dotfiles from the result, as mise dot apply already did. If a dotfile entry deploys a conf.d file, the entries in that file now apply in the same run, not the next one. --dry-run previews them as well. #​15387 (@​jdx, @​webkaz)
    • A symlink-each entry no longer writes through a directory symlink you made inside its target. That symlink is now reported as a conflict that needs --force. unapply also no longer deletes a directory symlink as if it were an empty folder. #​15399 (@​jdx)
    • On the first apply, a symlink-each source that contains a dangling symlink no longer loses its link right after creating it. #​15395 (@​jdx)
    • mise dot unapply --group and mise dot apply --prune now delete a group's leftover symlink-each state records once none of its links remain. #​15390 (@​jdx)
    • On a second machine whose local history holds no files, mise dot origin set now adopts the origin's history. It used to fail with "local and origin histories are unrelated". If origin set refuses to connect, it no longer writes [history.origin]. #​15394 (@​jdx)
    • History snapshots no longer start a git process for each encrypted tracked file. This speeds up mise bootstrap and the dotfile history commands when you have many encrypted files. #​15393 (@​jdx)
  • Shims
    • On macOS, when a due tool_update.global_auto check ran from a shim, the tool was launched with mise's internal arguments (jq: Unknown option --id). mise now runs the update itself. #​15389 (@​jdx)
    • When the installed version ships other executables but not the one you called, as after mprocs was renamed to dekit, the shim and mise which errors no longer suggest a reinstall that can't help. They now show the error mprocs@0.10.3 does not provide mprocs (it provides: dekit), or name another installed version that does provide it. #​15388 (@​jdx)
  • Completion
    • In mise x -- <cmd> <Tab>, every word after the command now completes file names, as it would in a plain shell. The same applies to mise dot capture --, mise bootstrap repos exec -- and mise ssh. #​15396 (@​jdx, @​Yasushi)
    • When a task has the same name as a built-in command, such as upgrade, completing mise up now shows the built-in command's description. mise run <TAB> still shows the task. #​15385 (@​jdx)
  • Installs and config
    • Go tool installs now retry go install after temporary network errors from the module proxy or checksum database, using the http_retries setting. When the retries run out, mise shows the network error, not a misleading unknown revision. #​15384 (@​jdx)
    • On Windows, aqua raw downloads whose URL ends in .exe now keep the extension when the recipe sets complete_windows_ext: false. Before, aqua:SonarSource/sonarqube-cli installed sonar instead of sonar.exe. #​15412 (@​jdx)
    • mise no longer crashes with PermissionDenied if it can't resolve a config path. This happened on Windows inside workspace sandboxes. A config trusted outside the sandbox may show as untrusted inside it; MISE_TRUSTED_CONFIG_PATHS works around that. #​15383 (@​jdx)
    • With skills.auto_sync, a tool that only your global config declares no longer has its agent skills linked into every project as well. Global tools are linked only under your home directory. mise skills sync without --dir or --global follows the same rule. Links that are already in project directories stay until you run mise skills sync --prune. [#​15391](https://redirect.github.com/jd

[!IMPORTANT]
✂ PR body was truncated to here.


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • "before 6am on monday"
  • 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 dannysauer as a code owner August 17, 2026 02:12
@renovate renovate Bot added autoapprove Stampbot automatic approval dependencies labels Aug 17, 2026
@renovate
renovate Bot enabled auto-merge (squash) August 17, 2026 02:12
@codecov

codecov Bot commented Aug 17, 2026 •

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (7b90054) to head (d97d634).

Additional details and impacted files
@@            Coverage Diff            @@
##              main      #308   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           10        10           
  Lines         1344      1344           
  Branches       168       168           
=========================================
  Hits          1344      1344           
Flag Coverage Δ
unittests 100.00% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@github-actions

Copy link
Copy Markdown
Contributor

🐳 Docker image built and pushed: ghcr.io/dannysauer/stampbot:pr-32bad41

@renovate
renovate Bot force-pushed the renovate/github-actions branch from 597ffd3 to a34e387 Compare August 17, 2026 21:31
@github-actions

Copy link
Copy Markdown
Contributor

🐳 Docker image built and pushed: ghcr.io/dannysauer/stampbot:pr-49e4e54

@renovate
renovate Bot force-pushed the renovate/github-actions branch from a34e387 to eb5c0dc Compare August 19, 2026 19:13
@github-actions

Copy link
Copy Markdown
Contributor

🐳 Docker image built and pushed: ghcr.io/dannysauer/stampbot:pr-b559d1e

@renovate
renovate Bot force-pushed the renovate/github-actions branch from eb5c0dc to eaf71d1 Compare August 20, 2026 00:00
@github-actions

Copy link
Copy Markdown
Contributor

🐳 Docker image built and pushed: ghcr.io/dannysauer/stampbot:pr-6e95a10

@renovate
renovate Bot force-pushed the renovate/github-actions branch from eaf71d1 to 62ed86b Compare August 20, 2026 18:49
@github-actions

Copy link
Copy Markdown
Contributor

🐳 Docker image built and pushed: ghcr.io/dannysauer/stampbot:pr-99d4f2e

@renovate
renovate Bot force-pushed the renovate/github-actions branch from 62ed86b to 5a27ce4 Compare August 21, 2026 17:03
@github-actions

Copy link
Copy Markdown
Contributor

🐳 Docker image built and pushed: ghcr.io/dannysauer/stampbot:pr-aaf6d1c

@renovate
renovate Bot force-pushed the renovate/github-actions branch from 5a27ce4 to 3fd9611 Compare August 23, 2026 17:54
@github-actions

Copy link
Copy Markdown
Contributor

🐳 Docker image built and pushed: ghcr.io/dannysauer/stampbot:pr-b76cf8a

@renovate
renovate Bot force-pushed the renovate/github-actions branch from 3fd9611 to 6373462 Compare August 24, 2026 21:55
@github-actions

Copy link
Copy Markdown
Contributor

🐳 Docker image built and pushed: ghcr.io/dannysauer/stampbot:pr-b0d37d6

@renovate
renovate Bot force-pushed the renovate/github-actions branch from 6373462 to e7de349 Compare August 25, 2026 19:07
@github-actions

Copy link
Copy Markdown
Contributor

🐳 Docker image built and pushed: ghcr.io/dannysauer/stampbot:pr-3affe02

@renovate
renovate Bot force-pushed the renovate/github-actions branch from e7de349 to e8bd071 Compare August 26, 2026 00:34
@github-actions

Copy link
Copy Markdown
Contributor

🐳 Docker image built and pushed: ghcr.io/dannysauer/stampbot:pr-daea0a4

@renovate
renovate Bot force-pushed the renovate/github-actions branch from e8bd071 to f890631 Compare August 26, 2026 05:03
@github-actions

Copy link
Copy Markdown
Contributor

🐳 Docker image built and pushed: ghcr.io/dannysauer/stampbot:pr-2e0b875

@renovate
renovate Bot force-pushed the renovate/github-actions branch from f890631 to 73c5b47 Compare August 26, 2026 20:49
@github-actions

Copy link
Copy Markdown
Contributor

🐳 Docker image built and pushed: ghcr.io/dannysauer/stampbot:pr-f4fd554

@renovate
renovate Bot force-pushed the renovate/github-actions branch from 73c5b47 to 10c91ee Compare August 27, 2026 22:39
@renovate
renovate Bot force-pushed the renovate/github-actions branch 10 times, most recently from eb029b6 to f177100 Compare September 25, 2026 04:37
@renovate
renovate Bot force-pushed the renovate/github-actions branch 10 times, most recently from 3bc0c46 to b653959 Compare October 2, 2026 18:30
@renovate
renovate Bot force-pushed the renovate/github-actions branch 9 times, most recently from 6fcca67 to 8695c4d Compare October 8, 2026 16:59

This branch has not been deployed

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

Labels

autoapprove Stampbot automatic approval dependencies

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants