[dependabot]

Bumps the actions group with 5 updates in the / directory:

Package	From	To
softprops/action-gh-release	3.0.3	3.0.4
ossf/scorecard-action	2.4.4	2.5.0
github/codeql-action/upload-sarif	4.38.3	4.39.3
narayann7/star-history-action	ffcb7d0219c8ccc46f21f6e0f530b17782a73f04	40684de767f6f524052941ff59b91ab5b0c8d4f1
docker/login-action	4.6.0	4.8.0

Bumps the actions group with 1 update in the /.github/actions/setup-env directory: jdx/mise-action.

Updates softprops/action-gh-release from 3.0.3 to 3.0.4

Release notes

Sourced from softprops/action-gh-release's releases.

v3.0.4

• maintenance release with updated dependencies

Changelog

Sourced from softprops/action-gh-release's changelog.

3.0.4

• maintenance release with updated dependencies

3.0.3

3.0.3 is a maintenance release with updated dependencies. It also safely classifies malformed GitHub API errors to avoid secondary failures (#822).

What's Changed

Bug fixes 🐛

• fix: safely classify GitHub API errors by @​chenrui333 in softprops/action-gh-release#822

Other Changes 🔄

• dependency updates

3.0.2

3.0.2 is a patch release focused on release reliability and compatibility. It reuses existing draft releases when publishing prereleases, supports replacing release assets on Gitea, hardens streamed asset uploads, and provides clearer release-creation diagnostics. It also includes TypeScript, coverage, and tooling maintenance merged since 3.0.1.

This release fixes #795, #438, and #803. The upload transport hardening covers the historical failure reported in #790, although current hosted Node 24 runners did not reproduce it naturally. The diagnostics work is related to #786 and does not claim a reproducible release-creation fix.

What's Changed

Exciting New Features 🎉

• feat: improve release error reporting and test coverage by @​chenrui333 in softprops/action-gh-release#813

Bug fixes 🐛

• fix: publish existing draft releases as prereleases by @​godfengliang in softprops/action-gh-release#801
• fix: upload small checksum assets reliably by @​chenrui333 in softprops/action-gh-release#815
• fix: replace existing release assets on Gitea by @​chenrui333 in softprops/action-gh-release#816
• fix: clarify release creation 404 errors by @​chenrui333 in softprops/action-gh-release#817

Other Changes 🔄

• chore(deps): upgrade TypeScript to 7 by @​chenrui333 in softprops/action-gh-release#812
• chore(deps): remove unused TypeScript tooling by @​chenrui333 in softprops/action-gh-release#814
• dependency, Node 24 pin, and CI maintenance merged since 3.0.1

... (truncated)

Commits

• 8a0cd65 release 3.0.4 (#865)
• ac01154 chore(deps): bump the npm group across 1 directory with 4 updates (#864)
• ca4c9d5 chore(deps): bump minimatch and glob (#862)
• e4a57ae chore(deps): bump undici from 6.29.0 to 6.29.1 (#859)
• ee55a0e chore(deps): bump vite from 8.3.2 to 8.3.5 (#855)
• 8d42b22 chore(deps): bump actions/setup-node (#853)
• 6680cc0 chore(deps): bump the npm group with 3 updates (#851)
• 4a050ba chore(deps): bump source-map-js from 1.2.1 to 1.2.2 (#850)
• b5a645e chore(deps): bump the npm group with 4 updates (#848)
• d99a5de chore(deps): bump brace-expansion from 5.0.9 to 5.0.12 (#846)
• Additional commits viewable in compare view

Updates ossf/scorecard-action from 2.4.4 to 2.5.0

Release notes

Sourced from ossf/scorecard-action's releases.

v2.5.0

What's Changed

This release moves the action to Scorecard v5.6.0, the first Scorecard release since its hosted services moved to new infrastructure.

For changes to checks and results, and what the infrastructure move means for you, see the Scorecard v5.6.0 release notes.

• The action's container image is built with Go 1.27.2 on a refreshed distroless base. by @​justaugustus in ossf/scorecard-action#1716
• The installer (cmd/installer) now creates .github/workflows/scorecard.yml, and still recognizes existing scorecards.yml and scorecards-analysis.yml workflows. by @​justaugustus in ossf/scorecard-action#1716
• The Scorecard version in results now always matches the Scorecard release the action is built with. by @​justaugustus in ossf/scorecard-action#1718
• The action no longer prints the GitHub token variable while validating its options. by @​arpitjain099 in ossf/scorecard-action#1709
• results_format accepts intoto, which wraps the JSON results in an in-toto attestation statement. by @​puerco in ossf/scorecard-action#1702

Other

• Add a daily canary against Scorecard main by @​justaugustus in ossf/scorecard-action#1711
• Bump Scorecard to the v5.6.0 candidate and fix the canary toolchain by @​justaugustus in ossf/scorecard-action#1714
• Run Scorecard on every merge, add a zizmor presubmit, analyze workflows with CodeQL, and update RELEASE.md by @​justaugustus in ossf/scorecard-action#1716
• Bump Scorecard to v5.6.0 by @​justaugustus in ossf/scorecard-action#1719

New Contributors

• @​arpitjain099 made their first contribution in ossf/scorecard-action#1709
• @​puerco made their first contribution in ossf/scorecard-action#1702

Full Changelog: ossf/scorecard-action@v2.4.4...v2.5.0

Commits

• fa7117d Bump action tag for v2.5.0 release (#1720)
• cef4eb5 🌱 Bump Scorecard to v5.6.0 (#1719)
• bedb16e ✨ Add intoto results format (#1702)
• de70347 Remove the leftover debug print of the auth token (#1709)
• 950873d 🌱 Derive the reported Scorecard version from go.mod (#1718)
• 2ce8ee4 🌱 Bump github.com/sigstore/cosign/v2 from 2.6.4 to 2.6.5 (#1695)
• aabdf5a 🌱 Bump the github-actions group across 1 directory with 7 updates (#...
• b4b9adf 🌱 CodeQL: Analyze workflows instead of a placeholder JavaScript file
• 4e9f2a2 📖 RELEASE.md: Document drafting release notes
• f618e8b 🌱 Build the image with Go 1.27.2 and refresh distroless
• Additional commits viewable in compare view

Updates github/codeql-action/upload-sarif from 4.38.3 to 4.39.3

Release notes

Sourced from github/codeql-action/upload-sarif's releases.

v4.39.3

• 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

• 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

• Update default CodeQL bundle version to 2.27.3. #4256

v4.39.0

• 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

Changelog

Sourced from github/codeql-action/upload-sarif's changelog.

CodeQL Action Changelog

See the releases page for the relevant changes to the CodeQL CLI and language packs.

[UNRELEASED]

No user facing changes.

4.39.3 - 04 Nov 2026

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

4.39.2 - 03 Nov 2026

• 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

4.39.1 - 21 Oct 2026

• Update default CodeQL bundle version to 2.27.3. #4256

4.39.0 - 15 Oct 2026

• 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

4.38.3 - 08 Oct 2026

• 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

4.38.2 - 24 Sept 2026

• Update default CodeQL bundle version to 2.27.1. #4160

4.38.1 - 18 Sept 2026

• 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

4.38.0 - 09 Sept 2026

• 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

... (truncated)

Commits

• 33d7b85 Merge pull request #4299 from github/update-v4.39.3-064910ba2
• 24393f8 Update changelog for v4.39.3
• 064910b Merge pull request #4297 from github/mbg/update-glob
• f532ac5 Update glob to 14.0.3
• 8cd4dfa Merge pull request #4280 from github/mbg/ci/validate-yaml
• cea289b Return different exit code when a language is not recognised
• 7287bb3 Remove exclude entry that's no longer needed
• 8eb7cdf Use normal .editorconfig pattern
• 160e547 Merge remote-tracking branch 'origin/main' into mbg/ci/validate-yaml
• 913e1bb Merge pull request #4283 from github/sam-robson/decode-diff-informed-sarif-uris
• Additional commits viewable in compare view

Updates narayann7/star-history-action from ffcb7d0219c8ccc46f21f6e0f530b17782a73f04 to 40684de767f6f524052941ff59b91ab5b0c8d4f1

Changelog

Sourced from narayann7/star-history-action's changelog.

Changelog

All notable changes to this action are documented here. Format follows Keep a Changelog, and the project aims to follow Semantic Versioning.

[1.0.6] - 2026-08-26

Fixed

• The legend label no longer runs past its box, and the title no longer runs under the owner logo, in viewers whose substitute font is wider than the bundled one (Firefox with a monospace default font, for example). The SVG ships no @font-face, so upstream's fixed per-character width estimate was off by whatever font the browser picked. The legend box is now sized from text widths measured in the PNG font (resvg with the same font files), and the legend and title <text> carry textLength so any substitute font is fitted into that width. Every theme is rendered with the same font-family so their layouts match. RENDER_VERSION is bumped, so the first run after upgrade re-renders and commits even with flat stars. (#7)
• The SVG now asks for a font stack (xkcd, "Comic Neue", "Chalkboard SE", "Comic Sans MS", sans-serif) instead of the bare xkcd family nobody has, so a browser substitutes a font close in width to the bundled Comic Neue and the textLength fitting above stays mild. Before, the substitute was the browser's default font, and a monospace default meant text compressed by about a quarter. The PNG is unaffected, since resvg skips families it has not loaded. (#7)
• Callers whose package.json pins npm without a committed lockfile no longer fail on the "Set up Node" step. actions/setup-node v5+ turns dependency caching on by itself when no cache input is given, keyed off the caller's package.json in GITHUB_WORKSPACE rather than the renderer's own tree under $ACTION_PATH. The action now passes package-manager-cache: false, keeping the v4 behaviour. (#6)

Changed

• actions/checkout and actions/setup-node bumped from v4 to v7, in the action itself and in the repo's own workflows and examples. (#6)

Compatibility

• The rendered chart changes shape slightly: the legend box is now as wide as the text it holds instead of the old per-character estimate, and legend and title text is drawn at its measured width. Existing charts are regenerated on the next run; no input or output of the action changed. (#7)

[1.0.5] - 2026-08-09

Changed

• The chart no longer draws the "star-history.com" watermark in the bottom-right corner. The vendored renderer is untouched; the watermark text and its icon are stripped after rendering, alongside the existing <style> and .browser-only strips. Attribution for the vendored star-history code stays

... (truncated)

Commits

• 40684de chore: update star history [skip ci]
• 70e8eef chore: update star history [skip ci]
• d8e93c5 chore: update star history [skip ci]
• d13b4bf chore: update star history [skip ci]
• 12543ab chore(release): 1.0.6
• 2b0b61e Merge pull request #7 from BlackHole1/fix/legend-text-fit
• b2c67e1 fix: keep legend and title text in place under any browser font
• 00dfada Merge pull request #6 from BlackHole1/chore/bump-checkout-setup-node-v7
• 6f854db chore: bump checkout and setup-node to v7
• f2e0776 chore: update star history [skip ci]
• Additional commits viewable in compare view

Updates docker/login-action from 4.6.0 to 4.8.0

Release notes

Sourced from docker/login-action's releases.

v4.8.0

• Set Docker Hub OIDC token lifetime default to 1 hour by @​crazy-max in docker/login-action#1070
• Bump @​aws-sdk/client-ecr and @​aws-sdk/client-ecr-public to 3.1161.0 in docker/login-action#1103
• Bump @​docker/actions-toolkit from 0.107.0 to 0.109.0 in docker/login-action#1105
• Bump vite from 7.3.6 to 7.3.7 in docker/login-action#1101

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

v4.7.0

• Preserve explicit ECR settings in registry-auth by @​crazy-max in docker/login-action#1089
• Use registry hosts for scoped credentials by @​crazy-max in docker/login-action#1088
• Raise Docker Hub OIDC max expiry to 6 hours by @​crazy-max in docker/login-action#1068
• Log Docker Hub OIDC token exchange progress by @​crazy-max in docker/login-action#1061
• Bump @​aws-sdk/client-ecr and @​aws-sdk/client-ecr-public to 3.1154.0 in docker/login-action#1093
• Bump @​docker/actions-toolkit from 0.94.0 to 0.107.0 in docker/login-action#1100
• Bump @​humanfs/node from 0.16.7 to 0.16.8 in docker/login-action#1077
• Bump csv-parse from 7.0.1 to 7.0.3 in docker/login-action#1078
• Bump handlebars from 4.7.9 to 4.7.10 in docker/login-action#1091
• Bump js-yaml from 5.2.2 to 5.5.0 in docker/login-action#1066
• Bump postcss from 8.5.22 to 8.5.26 in docker/login-action#1071
• Bump postcss-selector-parser from 7.1.1 to 7.1.6 in docker/login-action#1092
• Bump source-map-js from 1.2.1 to 1.2.2 in docker/login-action#1090
• Bump undici from 6.27.0 to 6.29.1 in docker/login-action#1085
• Bump uuid from 14.0.1 to 14.0.3 in docker/login-action#1096

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

Commits

• 8aa5831 Merge pull request #1105 from docker/dependabot/npm_and_yarn/docker/actions-t...
• 043f81d [dependabot skip] chore: update generated content
• 3ff6998 build(deps): bump @​docker/actions-toolkit from 0.107.0 to 0.109.0
• 694ef6a Merge pull request #1103 from docker/dependabot/npm_and_yarn/aws-sdk-dependen...
• 7c6e412 [dependabot skip] chore: update generated content
• aa2441f build(deps): bump the aws-sdk-dependencies group across 1 directory with 2 up...
• d6c10b0 Merge pull request #1106 from docker/dependabot/github_actions/codeql-actions...
• 319f1ee Merge pull request #1104 from docker/dependabot/github_actions/actions/setup-...
• b483b7f Merge pull request #1101 from docker/dependabot/npm_and_yarn/vite-7.3.7
• dc7d67c Merge pull request #1070 from crazy-max/increase-oidc-default-expiry
• Additional commits viewable in compare view

Updates jdx/mise-action from 5.1.1 to 5.2.7

Release notes

Sourced from jdx/mise-action's releases.

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

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

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/cacheactions/toolkit#2470Error 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

v5.2.5: Bundled packslip verifier updated to 1.11.0; README examples use v5

This release updates the packslip library that the action uses to verify downloaded mise releases, and updates the README examples to use the current major versions.

Changed

• packslip updated from 1.8.0 to 1.11.0. The action uses packslip to check a downloaded mise binary against the signed packslip.sigstore.json that ships with mise releases from 2026.9.3 onward. The new version runs extra checks on the signed statement: the identity it declares must match the certificate that signed it, and the certificate must belong to the github.com/jdx/mise repository. GitHub and GitLab repository names now match regardless of letter case. The action still asks for the same identity, issuer and tag as before, and there are no new inputs. (#715)
• The README examples now use jdx/mise-action@v5 and actions/checkout@v7. (#710 by @​deining)

Full Changelog: jdx/mise-action@v5.2.4...v5.2.5

v5.2.4: Reuse cached signed checksums when restoring mise

Jobs that restore mise from the cache no longer have to download its signed checksums from GitHub on every run, so a network failure at that step no longer fails a job that otherwise restored correctly.

Fixed

• Restoring a cached mise no longer needs a network download of the checksums. The action checks the cached mise binary against the signed SHASUMS256.txt and its .minisig. Before this release it downloaded both files from GitHub on every run, even when the cache restored correctly. When that download failed, for example after repeated curl errors, the job failed. Now, once the signature checks out, the action saves both files as SHASUMS256-<version>.txt and .minisig in <mise_dir>/bin, which is part of the mise cache. On later runs it reads them from the restored cache and checks the minisign signature again before using them. If the files are missing, corrupt or tampered with, the action downloads them as it did before. There are no new inputs. (#708 by @​jdx)
  • Caches saved by earlier versions don't contain these files. The main cache is only saved on a cache miss, so runs keep downloading the checksums until the cache is saved again or its key changes.

Full Changelog: jdx/mise-action@v5.2.3...v5.2.4

v5.2.3: Faster cache key computation in large workspaces

The cache key no longer comes from searching the whole workspace for mise config files. In repos that already contain node_modules or vendor/bundle, this removes a delay of several minutes in "Restoring mise cache".

... (truncated)

Changelog

Sourced from jdx/mise-action's changelog.

Changelog

---

5.2.7 - 2026-11-06

🐛 Bug Fixes

• retry transient download failures with backoff and report the HTTP status (#722) by @​jdx in #722

---

5.2.6 - 2026-11-02

🐛 Bug Fixes

• exit after run and post so a failed cache restore can't hang the step (#718) by @​jdx in #718

---

5.2.5 - 2026-10-31

🔍 Other Changes

• bump versions (#710) by @​deining in #710

---

5.2.4 - 2026-10-27

🐛 Bug Fixes

• (cache) reuse signed checksums saved with a cached mise (#708) by @​jdx in #708

---

5.2.3 - 2026-10-24

🐛 Bug Fixes

• (cache) hash mise config files without walking the workspace (#703) by @​jdx in #703

---

5.2.2 - 2026-10-21

🐛 Bug Fixes

• hash conf.d config fragments in cache key (#698) by @​rileymichael in #698

New Contributors

• @​rileymichael made their first contribution in #698

---

5.2.1 - 2026-10-19

... (truncated)

Commits

• b44d12e chore: release v5.2.7 (#723)
• 95feee8 fix(deps): update dependency packslip to v1.11.2 (#726)
• 7dd01dc chore(deps): update jdx/mise-action action to v5.2.4 (#725)
• ba4db83 chore(deps): update dependency hk to latest (#724)
• 382c35d fix: retry transient download failures with backoff and report the HTTP statu...
• f5be966 chore: release v5.2.6 (#719)
• 2187bd8 chore(deps): lock file maintenance (#720)
• 8008c3f fix: exit after run and post so a failed cache restore can't hang the step (#...
• 6612f0e chore: release v5.2.5 (#711)
• 432c79b chore(deps): update mise tools to latest (#714)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

Run configuration

• Source mode: Auto
• Repository: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: Repository UI
• Review profile: CHILL
• Plan: Advanced
• Run ID: e5bdd6ac-1cf2-42cb-a034-d014477d0046

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• Trigger review

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

• X
• Mastodon
• Reddit
• LinkedIn

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

AI Reviewer: first review requested successfully. AI can make mistakes. Always validate suggestions.

_{TIP This summary will be updated as you push new changes.}

[codacy-production]

Pull Request Overview

✅ No blocking issues noticed

No blocking findings were identified. The updated action references should still receive syntax and revision validation, plus integration coverage for the affected workflows.

Test suggestions

• Validate that each updated workflow and composite action remains syntactically valid and references the intended action revisions.
• Exercise release creation, asset upload, manifest signing, scorecard analysis, star-history generation, Docker login, and toolchain setup with the updated actions.

Prompt proposal for missing tests

Consider implementing these tests if applicable:
1. Validate that each updated workflow and composite action remains syntactically valid and references the intended action revisions.
2. Exercise release creation, asset upload, manifest signing, scorecard analysis, star-history generation, Docker login, and toolchain setup with the updated actions.

_{TIP How was this review? Give us feedback}