v0.1.1

What's new in 0.1.1

Advisory rules (minApprovals: 0) — model non-mandatory reviewers on the same paths as the
mandatory ones. A rule with minApprovals: 0 still auto-adds its owners as reviewers, but it
never blocks the merge (not even when its owners can't be resolved) and contributes no veto
line.

rules:
  - paths: ["frontend/**"]
    owners: ["@frontend-seniors"]
    minApprovals: 1          # mandatory: at least one senior must approve
  - paths: ["frontend/**"]   # same paths
    owners: ["@frontend-all"]
    minApprovals: 0          # advisory: added as reviewers, never blocks

On a frontend/** change the whole team is added as reviewers, but only a senior approval
clears the gate — with a single, clear veto message (no redundant line from the advisory rule).

Install

Two artifacts are attached — pick the one matching your platform line, upload it via
Administration → Manage apps → Upload app, then enable Code Owners Merge Check per
repository/project under Merge checks:

Your Bitbucket	Download
DC 10.x (Java 21)	bitbucket-codeowners-0.1.1.jar
DC 9.x LTS (Java 17)	bitbucket-codeowners-0.1.1-bb9.jar

The default .jar is compiled for Java 21 and will not load on a 9.x instance (Java 17) —
use the -bb9 artifact there. Both are built from the same source (identical behavior); you
can also build the 9.x one yourself with mvn -B -Pbb9 clean package.

Config reference:
docs/configuration.md
· full list of changes in the
CHANGELOG.

Verified

mvn clean verify green on both profiles — default (Bitbucket 10.3.1 / Java 21) and bb9
(Bitbucket 9.3.0 / Java 17), 37 tests each — and the advisory behavior was live-checked on a
Bitbucket 9.3.2 instance: a mandatory+advisory pair on the same path blocks with a single veto,
and an advisory-only path merges freely.

License: MIT. Upgrading from 0.1.0: drop-in; no config changes required.