chore(deps): update zeebe-io/backport-action action to v4.4#131
Merged
Conversation
f0a6b41 to
78a0852
Compare
bobh66
approved these changes
Apr 21, 2026
78a0852 to
2ef84e9
Compare
bobh66
approved these changes
Apr 21, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v4.3.0→v4.4Release Notes
zeebe-io/backport-action (zeebe-io/backport-action)
v4.4Compare Source
v4.4.0: Backport-action v4.4.0Compare Source
What's Changed
The new
add_reviewersandadd_team_reviewersinputs 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!Backport-action no longer instructs users to force-push (with a lease) in the manual instructions for conflicts when using the
draft_commit_conflictsoption for the experimentalconflict_resolutioninput. 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!Updated dependencies
Maintenance changes
New Contributors
Full Changelog: korthout/backport-action@v4.3.0...v4.4.0
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.