4.4.2 - Update all dependencies to latest version

No user-facing changes.

4.2.1 - Fix issue with commit message formatting

Fixed in ffcfcb9

4.1.0 - Explicitly set remote branch name when pushing

• Some versions of Git (2.14.1) were pushing to the wrong branch, when it was not explicitly set (#78)

v4.0.0 Better CLI arguments

• change --own to --all: By default own commits are shown. By passing --all a list of all commits will be displayed
• It is now possible to specify upstream with --upstream and branch with --branch. Eg. backport --upstream elastic/kibana --branch 6.x. If globally installed backport can now be used from any folder, and even for projects not cloned locally.
• Deprecate projects field in global config (~/.backport/config.json)

v3.0.2 - Increase maxBuffer to 100mb

This is a minor release that fixes an issue where big git diffs would cause backport to crash, since Node's maxBuffer size by default is quite small.

This release increases maxBuffer size to 100mb.

v3.0.0 - Improving the getting started experience

This major release drops support for older versions of Node, so I can take advantage of some of the new ES7 feature. The first time experience has been improved substantially, by giving helpful error messages for things like malformed config file, issues with SSH, and by showing the progress for cloning a repository (the slowest part of running backport).

• Bump to Node 8 and drop support for Node 6 (#59)
• Better handling of configs with invalid JSON (#60)
• Allow user to abort during conflict resolution (#60)
• Gracefully abort if user does not have proper ssh access to github (#61)
• Progress indicator for cloning a repository (#62)

v2.2.0

Add joi for config validation (#30)

v2.1.1

Per project config files
In addition to the global, user-specific config file, it is now possible to add a local project-specific config file in the root of your project.

The config must be named.backportrc.json and have the following structure:

{
  "upstream": "elastic/kibana",
  "branches": ["6.x", "6.1", "6.0"]
  "labels": ["backport"]
}

More details available in the readme

v1.4.0

Better handling of merge conflicts
When a cherrypick resultet in a conflict, the user should manually fix it. Unfortunately the user was not made aware, that she should also commit her changes. This sometimes resulted in pull request that didn't have the changes for the conflict resolution.

With this patch the user cannot proceed to from the cherrypick step, if a conflict occurred, and has not been completely resolved. If the index is dirty (new or modified files), and the user still tries to continue, a new prompt will ask her to resolve and commit it.

v1.3.0

Backporting multiple commits
It's now possible to backport multiple commits. It can be enabled by running backport --multiple or adding multiple: true to the backport config.

Bug fixes

• It was previously possible to continue the program by pressing enter, without having selected any commits/versions. This is now fixed, so continuing is not possible before a selection has been made.