Version 5.0.0+ is compatible with Bitbucket DC 8.0

1. Sets a timeout for git patch id calculations

2. Adds a property that can be set in bitbucket.properties to configure the timeout

3. Adds a property that can be set in bitbucket.properties to disable patch ID behaviour

See the README for more details: https://bitbucket.org/atlassian/stash-auto-unapprove-plugin/src/master/README.md

Depending on the input, "git patch-id --stable" can produce multiple patch IDs, one per line of output. Previously, only the first was considered, which resulted in approvals not being withdrawn if the first patch ID between two diffs was the same but a subsequent one was not.

This version adds handling for multiple patch IDs, only preserving approvals if the old and new diffs produce the same number of patch IDs with the same values in the same order.

Configure the auto-unapprove plugin at the project level to automatically apply to all repositories in that project. Repositories can override the project default to set their own.

Configure the plugin at the global level to automatically apply to all projects and repositories. Projects and repositories can override the global default to set their own.

Resolves an issue where commits that only modified binary files would not withdraw approvals. (#42)

Previously, processing to determine whether to unapprove a pull request after a rescope was performed directly on Bitbucket Server's event threads. Since processing can (in the worst case) take multiple minutes, that can result in the event queue filling up and potentially dropping events.

Miscelaneous bugfixes, most notably https://jira.atlassian.com/browse/BSERV-10439

Version 2.2.0's changes to use git diff | git patch-id broke compatibility with Bitbucket Server 5.x. 3.0.0 reintroduces support for 5.x, and raises the minimum supported version to 5.0.0.

If you're running Bitbucket Server 4.x, install 2.2.0 instead. It has all the same functionality!

• Handles changes to the target branch on declined pull requests (#12)
• Does not withdraw approvals on target branch updates if the new target branch references the same latest commit as the previous target branch (#13)
• Uses git diff | git patch-id to detect whether new commits pushed to the source branch actually update the diff and, if not, no longer withdraws approvals (#14, #15)

All PR approvals are reset to unapproved when the target branch is changed.

Beta release - adds a new option to the Repository Settings -> Pull requests menu, allowing you to automatically unapprove reviewers when the source branch of a pull request is updated.