Release Notes v8.3

We released DevSensei | Code Owners for Bitbucket 8.3 on 13 May 2025 🎉

Download on the Atlassian Marketplace for Data Center

Features

🆕 DevSensei Workflow Action: schedule-auto-merge

We are previewing a new action to enhance workflows: schedule-auto-merge, which schedules a Bitbucket Auto-Merge. A pull requests on auto merge is merged as soon as all merge checks are fulfilled and there are no merge conflicts.

Why? Use this action to fast track pull requests that need less feedback. For example: back porting code, small fixes, changes to less critical parts like documentation, styles etc.

Can you show me an example?

Here is an example devsensei.yaml file, configured to schedule auto merge if the pull request is a back-port:

  - name: Auto Merge Pull Requests that are backports 
    conditions:
      - destination~=releases/*
      - title~=[BACKPORT]*
      - "!draft"
    actions:
      - schedule-auto-merge:
          message: Backported from the regular development cycle
          strategy: ff

Bitbucket 8.15 required

The auto merge feature is supported for Bitbucket 8.15 or newer.

🆕 Assignment Limits

Code Owners are only added and never automatically removed. When you accidentally rebase a pull request to the incorrect branch, or push an incorrect commit, then Code Owners might add a large number of reviewers. These reviewers are then not removed when you fix the mistake.
To prevent adding too many Code Owners, you now can set an upper limit. If that limit is reached, no reviewers will be added and a warning comment is added instead.

In CODEOWNERS file:

CODEOWNERS.toplevel.assignment_limit <max-number>
# Example: CODEOWNERS.toplevel.assignment_limit 20

In devsensei.yaml file:

    actions: 
      - add-codeowners: 
          assignment-limit: <max-number>

Drop support for older EoL Bitbucket versions

We decided to make Bitbucket 8.9 the minimum supported version, as Atlassian ended Bitbucket 7 support for some time.

Changelog

🐛 Bugfixes 8.3.0 12 May 2025

• Fixed the glob matching, where a glob like dir1/subdir/** would also match dir1/subdir-and-more.

• Also improve performance when multiple arbitrary path wildcards are chained (e.g. /**/**/) (note that if you want a pattern to control the depth of arbitrary directories, then use *, e.g. /*/*/ for two levels.)

Previous: Release Notes v8.2

Do you have any questions, suggestions, or problems?

Let us know. We’re glad to help!