Release Notes v8.5

We released DevSensei | Code Owners for Bitbucket 8.5 on 30 Jun 2025 🎉

Download on the Atlassian Marketplace for Data Center

Features

🆕 DevSensei Workflow Action: unapprove

We introduced a new DevSensei Workflow Action to unapprove previous reviews. The action lets you remove all current approvals, or approvals from specific members.

Why? This can be useful to remove approvals after a change in the Pull Request.

Can you show me an example?

Here is an example devsensei.yaml file, configured to unapprove all reviews when the pull request leaves the “draft” state:

  - name: Unapprove reviewers when PR is ready
    conditions:
      - not(draft)
    actions:
      - unapprove:
          members: all

🆕 Retrigger action on Pull Request Diff Change

With the advent of the unapprove actions above, we wanted to introduce a new way to retrigger workflow actions when the diff of the Pull Request changes (perhaps after a new commit or a rebase).

Add the diff-change clause to your devsensei.yaml retrigger-on section to make every action in the workflow to run every time.

Can you show me an example?

Here is an example that will unapprove all reviewers (see new feature above) on diff change

  - name: Unapprove reviewers on diff change
    retrigger-on:
      - diff-change
    actions:
      - unapprove:
          members: all

⚡️ Improved performance for Code Owners action with many Bitbucket or Reviewer groups

We improved the performance of the Code Owners action (either from the legacy CODEOWNERS file, or the new devsensei.yaml file) when it involves many Bitbucket groups.

Previously, referring to hundreds of Bitbucket or reviewer groups would cause the Code Owners processing to take a long time. We address this use-case by adding an internal cache on the existing groups. This cache is 30 minutes long, so in certain cases, changes to Bitbucket groups will not be effective right away.

Changelog

🐛 Bugfixes 8.5.0 25 Jun 2025

• UI links to your DevSensei source files was off by one. It resulted to visual glitches when these links are followed.

• Fixed race conditions sometimes causing Code Owners to not be added. Previously, having a busy pull request (with many people interacting) could create unfortunate race conditions leading to Code Owners not being added properly.

• the conflicts attribute will now have an accurate value inside of merge-checks.

Previous: Release Notes v8.4

Do you have any questions, suggestions, or problems?

Let us know. We’re glad to help!