chore(deps): update korthout/backport-action action to v4.5.2

[sevojulj]

This PR contains the following updates:

Package	Type	Update	Change
korthout/backport-action	action	minor	v4.2.0 → v4.5.2

---

Warning

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

---

Release Notes

korthout/backport-action (korthout/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 #​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 #​641

Updated dependencies

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

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

v4.5.1: Backport-action v4.5.1

Compare Source

What's Changed

Bug fix for comment_style: summary drops conflict-resolution instructions #​633

• Post resolve-conflicts comment on draft PR in summary mode by @​korthout in #​634

Updated dependencies

• Update korthout/backport-action action to v4.5.0 by @​renovate[bot] in #​627
• Lock file maintenance by @​renovate[bot] in #​632

Maintenance changes

• Enable summary comment style for our own backport workflow by @​korthout in #​628

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

v4.5.0: Backport-action v4.5.0

Compare Source

What's Changed

This release introduces a new comment_style input with two options:

• legacy (default): one comment per target branch. This is the same behavior as you know from previous versions.
• summary: a single comment per workflow run that updates progressively as each target is processed. It links back to the workflow run, shows a status table for every target, and includes recovery hints for known failure modes (e.g. push permission denied, cherry-pick conflicts).

Here's what a summary comment looks like mid-run:

Backport-action is backporting this pull request in workflow run 15439584062.

Target	Status
stable/8.7	✅ Created #​612
stable/8.6	⚠️ Drafted with conflicts #​613
stable/8.5	❌ Failed
stable/8.4	➖ Skipped (PR already exists)
stable/8.3	⌛ Pending

❌ stable/8.5 — unable to cherry-pick

Tried to cherry-pick commits onto stable/8.5, but the cherry-pick failed.

Please cherry-pick the changes locally and resolve any conflicts.

git fetch origin stable/8.5
git worktree add -d .worktree/stable/8.5 origin/stable/8.5
cd .worktree/stable/8.5
git switch --create <backport-branch-name>
git cherry-pick -x a1b2c3d e4f5g6h

Opt in by adding comment_style: summary to your workflow:

- uses: korthout/backport-action@v4.5.0
  with:
    comment_style: summary

I'd love feedback on summary while it's opt-in. Drop a comment on #​611 with anything that's confusing, missing, or broken. Once it's proven stable in real workflows, I plan to make it the default and deprecate legacy in a future major release.

• Add summary comment style by @​korthout in #​611

Updated dependencies

• Update korthout/backport-action action to v4.4.0 by @​renovate[bot] in #​606
• Update dependency @​actions/github to v9.1.1 by @​renovate[bot] in #​614
• Update dependency vitest to v4.1.5 by @​renovate[bot] in #​612
• Update dependency @​actions/core to v3.0.1 by @​renovate[bot] in #​613
• Lock file maintenance by @​renovate[bot] in #​621

Maintenance changes

• ci(Mergify): configuration update by @​korthout in #​607
• Configure Mergify merge queue by @​korthout in #​608
• Use PAT for PR info workflow comments by @​korthout in #​615
• Skip PR info comment on Mergify merge queue PRs by @​korthout in #​618
• refactor: restructure backport.ts for readability by @​korthout in #​610
• ci: authenticate Publish/Release pushes via deploy key by @​korthout in #​622
• Automerge Renovate lock file maintenance PRs by @​korthout in #​623

Full Changelog: korthout/backport-action@v4.4.0...v4.5.0

v4.5

Compare Source

v4.4.0: Backport-action v4.4.0

Compare Source

What's Changed

The new add_reviewers and add_team_reviewers inputs allow backport-action to request a review on the created backport pull request from the users and teams specified. These inputs can be used in simple setups where you want a particular user to always review, as well as in advanced setups where reviewers are determined in a separate workflow step. You can use these inputs in addition to any of the other reviewer inputs. Thanks for another great contribution @​mvlassis!

• feat: Add add_reviewers and add_team_reviewers inputs by @​mvlassis in #​588

Backport-action no longer instructs users to force-push (with a lease) in the manual instructions for conflicts when using the draft_commit_conflicts option for the experimental conflict_resolution input. When running these instructions locally, the cherry-pick would fail due to conflicts, and the force push could push back the branch to its base, effectively closing the PR. This was confusing and added to the manual effort needed. Instead, users should resolve conflicts locally and push changes only when they are ready. Thanks for the fix @​ChrisKujawa!

• refactor: rm force push mentioning by @​ChrisKujawa in #​594

Updated dependencies

• Update korthout/backport-action action to v4.3.0 by @​renovate[bot] in #​583
• Update dependency vitest to v4.1.1 by @​renovate[bot] in #​584
• Lock file maintenance by @​renovate[bot] in #​587
• Update dependency vitest to v4.1.3 by @​renovate[bot] in #​586
• Update dependency esbuild to v0.28.0 by @​renovate[bot] in #​589
• Update dependency @​types/node to v24.12.2 by @​renovate[bot] in #​590
• Update dependency typescript to v6 by @​renovate[bot] in #​585
• Update dependency @​actions/github to v9.1.0 by @​renovate[bot] in #​596
• Update dependency vitest to v4.1.4 by @​renovate[bot] in #​597
• Update dependency prettier to v3.8.2 by @​renovate[bot] in #​598
• Lock file maintenance by @​renovate[bot] in #​601
• Update actions/setup-node action to v6.4.0 by @​renovate[bot] in #​602
• Update dependency typescript to v6.0.3 by @​renovate[bot] in #​600
• Update dependency prettier to v3.8.3 by @​renovate[bot] in #​599

Maintenance changes

• Add integration test suite with FakeGithub and real-git tests by @​korthout in #​592
• fix: convert test helpers from execSync to async exec by @​korthout in #​595
• ci: replace gha-find-replace with sed by @​korthout in #​603
• Add merge queue support and Renovate automerge by @​korthout in #​604
• Remove merge queue support by @​korthout in #​605

New Contributors

• @​ChrisKujawa made their first contribution in #​594

Full Changelog: korthout/backport-action@v4.3.0...v4.4.0

v4.4

Compare Source

v4.3.0: Backport-action v4.3.0

Compare Source

What's Changed

The new copy_all_reviewers input allows backport-action to request a review on the backport pull request from all reviewers of the original pull request. When enabled, it requests reviews from both those who have already completed their review and those with pending review requests. You can use it in addition to any of the other reviewer inputs. Thanks for the great contribution @​mvlassis!

• feat: Add copy_all_reviewers input by @​mvlassis in #​578

Updated dependencies

• Lock file maintenance by @​renovate[bot] in #​568
• Update dependency jest to v30.3.0 by @​renovate[bot] in #​569
• Update dependency esbuild to v0.27.4 by @​renovate[bot] in #​572
• Migrate jest to vitest by @​korthout in #​573
• Update dependency vitest to v3.2.4 by @​renovate[bot] in #​574
• Update dependency @​types/node to v24.12.0 - autoclosed by @​renovate[bot] in #​575
• Update dependency vitest to v4 by @​renovate[bot] in #​576
• Update EndBug/add-and-commit action to v10 by @​renovate[bot] in #​580
• Lock file maintenance by @​renovate[bot] in #​581

New Contributors

• @​mvlassis made their first contribution in #​578

Full Changelog: korthout/backport-action@v4.2.0...v4.3.0

v4.3

Compare Source

---

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.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

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

---

This PR has been generated by Mend Renovate.

[sevojulj]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.