Skip to content

Releases: korthout/backport-action

Backport-action v4.0.1

15 Dec 12:56

Choose a tag to compare

What's Changed

This patch fixes a bug where environment variables were no longer passed to git since v4.0.0. For instance, this prevented the action to sign commits with GPG using variables like GNUPGHOME. With this fix, environment variables are provided to git again.

  • fix: pass existing environment variables when executing git by @yafanasiev in #527

Full Changelog: v4.0.0...v4.0.1

Backport-action v4.0.0

13 Dec 09:07

Choose a tag to compare

What's Changed

The action now requires Node 24 to run, which is a breaking change. Runner version 2.327.1 or higher is required from now on.

Other changes

Updated dependencies

Full Changelog: v3.4.1...v4.0.0

Backport-action v3.4.1

01 Oct 15:05

Choose a tag to compare

What's Changed

  • fix(action.yml): remove github expression examples by @yafanasiev in #507

Full Changelog: v3.4.0...v3.4.1

Backport-action v3.4.0

01 Oct 06:56

Choose a tag to compare

What's Changed

You can now automatically enable auto-merge on pull requests created by backport-action thanks to a great contribution from @jasonwbarnett - enable it using auto_merge_enabled and control the merge method using auto_merge_method.

It's now also easier to contribute to backport-action. Thanks to @yafanasiev, the CI can push newly built artifacts regardless of whether the PR comes from a fork or not.

Updated dependencies

New Contributors

Full Changelog: v3.3.0...v3.4.0

Backport-action v3.3.0

14 Aug 15:59

Choose a tag to compare

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.

  • feat: make git committer name and email configurable by @yafanasiev in #488

Updated dependencies

New Contributors

Full Changelog: v3.2.1...v3.3.0

Backport-action v3.2.1

26 Jun 06:13

Choose a tag to compare

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: v3.2.0...v3.2.1

Backport-action 3.2.0

23 Feb 22:12

Choose a tag to compare

What's Changed

This release adds two new inputs: add_labels and add_author_as_assignee.

add_labels allows you to specify additional labels for the backport pull request. Thanks @chancez for the great contribution!

  • Add support for statically setting labels on backport PRs by @chancez in #432
  • Delimit add_labels using comma by @korthout in #454

add_author_as_assignee allows 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!

  • Add option to add original author as assignee by @soooch in #445

Updated Dependencies

  • build(deps): bump @actions/core from 1.10.1 to 1.11.1 by @dependabot in #439
  • build(deps-dev): bump @vercel/ncc from 0.38.1 to 0.38.3 by @dependabot in #440
  • build(deps): bump cross-spawn from 7.0.3 to 7.0.6 by @dependabot in #441
  • build(deps): bump undici from 5.28.4 to 5.28.5 by @dependabot in #446
  • build(deps): bump @octokit/request-error from 5.0.1 to 5.1.1 by @dependabot in #447
  • build(deps): bump @octokit/plugin-paginate-rest from 9.1.2 to 9.2.2 by @dependabot in #448
  • build(deps): bump @octokit/request from 8.1.4 to 8.4.1 by @dependabot in #449
  • Bump dev dependencies and ES target by @korthout in #453

New Contributors

Full Changelog: v3.1.0...v3.2.0

Backport-action v3.1.0

21 Aug 17:03

Choose a tag to compare

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!

New Contributors

Full Changelog: v3.0.2...v3.1.0

Backport-action v3.0.2

28 May 11:42

Choose a tag to compare

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.

  • Checkout draft branch instead of target in suggestion by @korthout in #423

Full Changelog: v3.0.1...v3.0.2

Backport-action v3.0.1

28 May 10:29

Choose a tag to compare

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 #422

Full Changelog: v3.0.0...v3.0.1