Update all non-major github action

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
github/codeql-action	action	patch	v4.35.4 → v4.35.5
zeebe-io/backport-action	action	patch	v4.5.1 → v4.5.2

---

Warning

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

---

Release Notes

github/codeql-action (github/codeql-action)

v4.35.5

Compare Source

• We have improved how the JavaScript bundles for the CodeQL Action are generated to avoid duplication across bundles and reduce the size of the repository by around 70%. This should have no effect on the runtime behaviour of the CodeQL Action. #​3899
• For performance and accuracy reasons, improved incremental analysis will now only be enabled on a pull request when diff-informed analysis is also enabled for that run. If diff-informed analysis is unavailable (for example, because the PR diff ranges could not be computed), the action will fall back to a full analysis. #​3791
• If multiple inputs are provided for the GitHub-internal analysis-kinds input, only code-scanning will be enabled. The analysis-kinds input is experimental, for GitHub-internal use only, and may change without notice at any time. #​3892
• Added an experimental change which, when running a Code Scanning analysis for a PR with improved incremental analysis enabled, prefers CodeQL CLI versions that have a cached overlay-base database for the configured languages. This speeds up analysis for a repository when there is not yet a cached overlay-base database for the latest CLI version. We expect to roll this change out to everyone in May. #​3880

zeebe-io/backport-action (zeebe-io/backport-action)

v4.5.2: Backport-action v4.5.2

Compare Source

What's Changed

Bug fix for Summary comment incorrectly reports success when no target branches are found #​629. When the action runs but finds no targets (no matching labels and no target_branches input), the summary comment now explicitly states this instead of the misleading "backported this pull request". The comment also hints at filtering the trigger at the workflow level so the action runs only when there's work to do, and the README usage example now demonstrates that pattern with a label-prefix filter.

• Report no-targets outcome and recommend a workflow filter by @​korthout in korthout#636

Documentation

The README grew a new section on computing target_branches dynamically at workflow runtime. You may need this when targets come from a config file, an API call, or a parsed /backport <branch> comment rather than labels. We also made some further improvements to the README examples. We collapsed the signing example into a <details> block, tightened the comment-trigger example, and bumped the actions/checkout to v6 across examples.

• Document dynamic target_branches and refresh README examples by @​korthout in korthout#641

Updated dependencies

• Update korthout/backport-action action to v4.5.1 by @​renovate[bot] in korthout#635
• Update dependency @​types/node to v24.12.3 by @​renovate[bot] in korthout#638
• Lock file maintenance by @​renovate[bot] in korthout#639

Full Changelog: korthout/backport-action@v4.5.1...v4.5.2

---

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 was generated by Mend Renovate. View the repository job log.