chore(deps): update github-actions

[vovinacci]

This PR contains the following updates:

Package	Type	Update	Change
actions/checkout (changelog)	action	digest	9c091bb → 3d3c42e
actions/setup-java	action	minor	v5.6.0 → v5.7.0
jdx/mise-action	action	patch	v4.2.3 → v4.2.4
renovatebot/github-action	action	minor	v46.1.21 → v46.2.1

---

Release Notes

actions/setup-java (actions/setup-java)

v5.7.0

Compare Source

What's Changed

• Fix npm audit failures on releases/v5 by @​brunoborges in #​1154
• Backport #​1151: Fix missing wrapper cache distributions by @​brunoborges in #​1153
• Deprecate legacy Adopt distributions in v5 by @​brunoborges in #​1186

Full Changelog: actions/setup-java@v5.6.0...v5.7.0

jdx/mise-action (jdx/mise-action)

v4.2.4: : Reliable locking detection under forced color

Compare Source

A small patch release that fixes locking-support detection when workflows force colored output.

Fixed

Detect mise install --locked reliably under forced color (#​580 by @​scop)

When colored output was forced globally (for example via CLICOLOR_FORCE=1), ANSI escape codes in mise install --help prevented the action from matching --locked in the help text, so locking support was reported as unavailable even on versions of mise that supported it.

The help probe now runs with NO_COLOR=1 in its environment, which overrides CLICOLOR_FORCE and guarantees plain-text output for the feature detection — regardless of the surrounding workflow's color settings.

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

renovatebot/github-action (renovatebot/github-action)

v46.2.1

Compare Source

Documentation

• update references to renovatebot/github-action to v46.2.0 (b48aa6c)

Miscellaneous Chores

• deps: update dependency globals to v17.8.0 (3e46bd7)
• deps: update dependency lint-staged to v17.2.0 (9c685f2)
• deps: update node.js to v24.18.1 (f525256)

Build System

• deps: lock file maintenance (3d8211a)

Continuous Integration

• deps: update ghcr.io/renovatebot/renovate docker tag to v44.0.1 (d471d52)
• deps: update ghcr.io/renovatebot/renovate docker tag to v44.2.1 (5cb64df)
• deps: update ghcr.io/renovatebot/renovate docker tag to v44.2.2 (a6b5808)
• deps: update ghcr.io/renovatebot/renovate docker tag to v44.2.3 (ab4d1eb)
• deps: update ghcr.io/renovatebot/renovate docker tag to v44.3.0 (a427843)
• deps: update ghcr.io/renovatebot/renovate docker tag to v44.3.3 (2ac8329)
• deps: update ghcr.io/renovatebot/renovate docker tag to v44.4.0 (7665449)
• deps: update ghcr.io/renovatebot/renovate docker tag to v44.4.2 (0166c9f)
• deps: update ghcr.io/renovatebot/renovate docker tag to v44.4.3 (8662b55)
• deps: update ghcr.io/renovatebot/renovate docker tag to v44.4.5 (1e71262)
• deps: update ghcr.io/renovatebot/renovate docker tag to v44.4.6 (7bec40c)
• deps: update ghcr.io/renovatebot/renovate docker tag to v44.5.0 (d146e8b)
• deps: update ghcr.io/renovatebot/renovate docker tag to v44.5.1 (ddd5dca)
• deps: update ghcr.io/renovatebot/renovate docker tag to v44.5.2 (0731dab)
• deps: update ghcr.io/renovatebot/renovate docker tag to v44.5.3 (700f3b5)
• deps: update ghcr.io/renovatebot/renovate docker tag to v44.6.0 (7edb80e)
• deps: update ghcr.io/renovatebot/renovate docker tag to v44.7.0 (127e8ef)
• deps: update ghcr.io/renovatebot/renovate docker tag to v44.7.1 (f7532d1)
• deps: update ghcr.io/renovatebot/renovate docker tag to v44.7.2 (0fcd35b)
• deps: update ghcr.io/zizmorcore/zizmor docker tag to v1.29.0 (#​1068) (581f6ac)
• deps: update zizmorcore/zizmor-action action to v0.6.2 (e36e81c)

v46.2.0

Compare Source

Features

• deps: Update ghcr.io/renovatebot/renovate Docker tag to v44 (#​1067) (efa6654)

Documentation

• update references to renovatebot/github-action to v46.1.21 (66c62f6)

Miscellaneous Chores

• deps: update dependency lint-staged to v17.1.1 (403000c)
• deps: update dependency prettier to v3.9.6 (6787cf2)
• deps: update dependency typescript-eslint to v8.65.0 (656e12f)

Continuous Integration

• deps: update ghcr.io/renovatebot/renovate docker tag to v43.283.0 (560e916)
• deps: update ghcr.io/renovatebot/renovate docker tag to v43.284.0 (92c373e)
• deps: update ghcr.io/renovatebot/renovate docker tag to v43.284.1 (b0f9fee)
• deps: update ghcr.io/renovatebot/renovate docker tag to v43.285.0 (bfb9d5d)
• deps: update ghcr.io/renovatebot/renovate docker tag to v43.285.3 (91ba9dc)
• deps: update ghcr.io/renovatebot/renovate docker tag to v43.285.4 (e41061b)
• deps: update ghcr.io/renovatebot/renovate docker tag to v43.285.6 (e8a7a1c)
• deps: update ghcr.io/renovatebot/renovate docker tag to v43.285.7 (7a22a55)
• deps: update ghcr.io/renovatebot/renovate docker tag to v43.286.0 (7590e1e)
• deps: update ghcr.io/renovatebot/renovate docker tag to v43.286.1 (cae6616)
• deps: update ghcr.io/renovatebot/renovate docker tag to v43.287.0 (#​1066) (4f87158)

---

Configuration

📅 Schedule: (UTC)

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

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

---

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

---

This PR has been generated by Mend Renovate.

[coderabbitai]

Warning

Review limit reached

@vovinacci, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 59 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: b3e79e3e-8a9e-4340-ba59-bec81d3b223c

📥 Commits

Reviewing files that changed from the base of the PR and between 14a08e7 and c6e7a7f.

📒 Files selected for processing (3)

• .github/workflows/k8s-lint.yml
• .github/workflows/renovate.yml
• .github/workflows/reports.yml

---

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

_{Comment @coderabbitai help to get the list of available commands.}