build(deps): bump zeebe-io/backport-action from 1.4.0 to 3.1.0

[dependabot]

Bumps zeebe-io/backport-action from 1.4.0 to 3.1.0.

Release notes

Sourced from zeebe-io/backport-action's releases.

Backport-action v3.1.0

What's Changed

This release adds a new input source_pr_number that 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 on workflow_dispatch events, and complex workflows that require flexibility. Thanks for this great contribution @​chancez!

• Add source_pr_number input by @​chancez in korthout/backport-action#434

New Contributors

• @​chancez made their first contribution in korthout/backport-action#434

Full Changelog: korthout/backport-action@v3.0.2...v3.1.0

Backport-action v3.0.2

Fixed

This release fixes a small bug in the draft_commit_conflicts option for the experimental conflict_resolution feature. 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/backport-action#421.

• Checkout draft branch instead of target in suggestion by @​korthout in korthout/backport-action#423

Full Changelog: korthout/backport-action@v3.0.1...v3.0.2

Backport-action v3.0.1

Fixed

This release fixes a small bug in the draft_commit_conflicts option for the experimental conflict_resolution feature. 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.

• Suggest to fetch and checkout draft pr branch directly by @​korthout in korthout/backport-action#422

Full Changelog: korthout/backport-action@v3.0.0...v3.0.1

Backport-action v3.0.0

Changed

• [Breaking] Use merge method to cherry-pick by default by @​korthout in korthout/backport-action#420

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.

• For "Squash and merge", the action cherry-picks the squashed commit.
• For "Rebase and merge", the action cherry-picks the rebased commits.
• For "Merged as a merge commit", the action cherry-picks the commits from the pull request.

If you previously used the experimental detect_merge_method input, we suggest you remove it from your workflow. This experimental input has been deprecated and replaced by the cherry_picking input.

If you want to return to the previous behavior, you can set the cherry_picking input to pull_request_head.

This behavior was previously available via the experimental detect_merge_method input, introduced in korthout/backport-action#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!

... (truncated)

Commits

• be567af dist: release 3.1.0
• 6610ffe Merge pull request #434 from chancez/pr/chancez/workflow_dispatch_support
• bb1878b docs: add source_pr_number description
• 0fe1534 Merge pull request #431 from korthout/dependabot/npm_and_yarn/prettier-3.3.3
• f525c01 dist: build new version
• 0000171 refactor: remove unused github method
• 0dd861c dist: build new version
• cacb018 feat: remove event type restriction
• a5011fa docs: clarify source_pr_number input behavior
• f6b4356 docs: sort inputs alphabetically
• Additional commits viewable in compare view

You can trigger a rebase of this PR by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud