chore(deps): update zeebe-io/backport-action action to v3 #59
+1
−1
Conversation
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
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
renovate
bot
force-pushed
the
renovate/zeebe-io-backport-action-3.x
branch
from
9943ece to
9099ed1
Compare
renovate
bot
force-pushed
the
renovate/zeebe-io-backport-action-3.x
branch
from
9099ed1 to
4014f96
Compare
bobh66
approved these changes
Aug 29, 2025
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:
v2.5.0->v3.3.0Release Notes
zeebe-io/backport-action (zeebe-io/backport-action)
v3.3.0: Backport-action v3.3.0Compare Source
What's Changed
Thanks to a great contribution from @yafanasiev, you can now change the git committer name and email - enabling signing the cherry-picked commits.
Updated dependencies
New Contributors
Full Changelog: korthout/backport-action@v3.2.1...v3.3.0
v3.2.1: Backport-action v3.2.1Compare Source
What's Changed
Backport-action now detects when a backport branch or pull request already exists and continues without posting an error comment. This means you can safely add backport labels after a previous run. It also allows you to retry the workflow where the branch was pushed, but the pull request couldn’t be created. In earlier versions, rerunning in those situations would have left an error comment on the original pull request. Now, it handles these gracefully. The actions' log shows what happens in detail. Thanks @wolfgangwalther for this great contribution!
A typo in the actions' log was also fixed thanks to @codygarver.
Updated dependencies
New Contributors
Full Changelog: korthout/backport-action@v3.2.0...v3.2.1
v3.2.0: Backport-action 3.2.0Compare Source
What's Changed
This release adds two new inputs:
add_labelsandadd_author_as_assignee.add_labelsallows you to specify additional labels for the backport pull request. Thanks @chancez for the great contribution!add_labelsusing comma by @korthout in korthout#454add_author_as_assigneeallows you to control whether the action should set the author of the original pull request as an assignee on the backport pull request. Thanks @soooch for the great contribution!Updated Dependencies
New Contributors
Full Changelog: korthout/backport-action@v3.1.0...v3.2.0
v3.1.0: Backport-action v3.1.0Compare Source
What's Changed
This release adds a new input
source_pr_numberthat allows you to specify the pull request to backport in your workflow. Previously, the action always determined the pull request from the event payload, limiting the action only to backport the pull request associated with the current workflow run. This new input can be helpful in workflows that prefer to be explicit, workflows that run onworkflow_dispatchevents, and complex workflows that require flexibility. Thanks for this great contribution @chancez!source_pr_numberinput by @chancez in korthout#434New Contributors
Full Changelog: korthout/backport-action@v3.0.2...v3.1.0
v3.0.2: Backport-action v3.0.2Compare Source
Fixed
This release fixes a small bug in the
draft_commit_conflictsoption for the experimentalconflict_resolutionfeature. When encountering conflicts, the backport pull request is opened in draft mode with the conflicts committed. Instructions are provided to resolve these conflicts locally, but these were incorrect. For more details see korthout#421.Full Changelog: korthout/backport-action@v3.0.1...v3.0.2
v3.0.1: Backport-action v3.0.1Compare Source
Fixed
This release fixes a small bug in the
draft_commit_conflictsoption for the experimentalconflict_resolutionfeature. When encountering conflicts, the backport pull request is opened in draft mode with the conflicts committed. Instructions are provided to resolve these conflicts locally, but these were incorrect. For more details see #421.Full Changelog: korthout/backport-action@v3.0.0...v3.0.1
v3.0.0: Backport-action v3.0.0Compare Source
Changed
This release changes the default behavior of the action to determine which commits are cherry-picked. While this behavior change doesn't necessarily require changes to your workflow, it warrants a major version bump.
Previously, the action cherry-picked the commits from the pull request. Specifically, those reachable from the pull request's head and not reachable from the pull request's base.
From now on, the action cherry-picks the commits based on the method used to merge the pull request by default.
If you previously used the experimental
detect_merge_methodinput, we suggest you remove it from your workflow. This experimental input has been deprecated and replaced by thecherry_pickinginput.If you want to return to the previous behavior, you can set the
cherry_pickinginput topull_request_head.This behavior was previously available via the experimental
detect_merge_methodinput, introduced in korthout#399. Special thanks go out to @jschmid1 for contributing this feature.Added
This release also adds two new experimental features. Special shoutouts to @tasso94 and @vermz99 for contributing these!
With the experimental
downstream_repoanddownstream_ownerinputs, you can backport to a repository other than where the workflow runs. For example, when you use a fork to maintain the previously released versions. You can also see this as backporting to a remote repository, but we felt it was better described as backporting to a downstream repository. The default behavior remains that the action always backports to the repository in which the workflow runs.conflict_resolutioninput by @vermz99 in korthout#417With the experimental
conflict_resolutioninput, you can now change how the action will handle conflicts during cherry-picking. Set it todraft_commit_conflictsto create a draft pull request with the first conflict encountered committed to reduce some of the manual efforts in backporting. The default behavior stays like before and can be configured explicitly asfail. In that case, the backport fails when the cherry-pick encounters a conflict.Updated Dependencies
New Contributors
Full Changelog: korthout/backport-action@v2.5.0...v3.0.0
Configuration
📅 Schedule: 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 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.