# Regression Bug: Check It Against the Last Release

Source: https://maito.app/workflows/reproduce-a-reported-bug-against-the-last-release

Maito runs the reported steps on the current and previous release, tells you whether the bug is new, old or already fixed, and finds the commit behind it.

Check whether a bug is new, old, or already fixed.

[QA](https://maito.app/workflows/team/qa) · [Software](https://maito.app/workflows/industry/software) · When you ask · Updated October 19, 2026

Works with

-   Slack
-   Email

## How do you reproduce a reported bug against the last release?

To reproduce a reported bug against the last release, mention Maito with the report. It follows the steps in a browser on the current and previous release, records what happens, and finds the first commit where it broke. You learn whether it is new, old or fixed, with videos attached.

## How it's done today

Engineers spend an hour finding where it started.

## What Maito does

1.  Run the bug steps on current and previous versions
2.  Report where it started

## Example

**Mia** (11:40 AM):

did the login bug exist in last week's release? Support says people with a + in their email can't sign in.

**Maito** (12:02 PM):

No. It started in 4.12.

I tried sam+qa@northstar.example with the same password on both releases:  
• 4.11 (Oct 8): signs in  
• 4.12 (Oct 15): 'Invalid email address'

Between the two tags there are 38 commits. The first bad one is 7c2d1e9, Tighten email validation (PR #860). The new pattern doesn't allow +.

**Catch:** signup still accepts + addresses. Since 4.12, people can create accounts they can't log in to, so support will keep hearing about it.

Attached: login-4.11.mp4 and login-4.12.mp4. Want me to open a fix PR?

**Mia** (12:05 PM):

yes, and tell Sam in support what to say meanwhile.

**Maito** (12:21 PM):

PR #924 is open: login and signup use the same email pattern, with a test for +. For Sam: a bug in 4.12 blocks + addresses, fix in review, workaround is signing in with the plain address if it's an alias.

## How to set it up

When you ask Reproduce a reported bug against the last release

Set up

Nothing to set up. Ask in Slack or by email whenever you need it.

## What it won't do

A bug that depends on a specific customer's data or setup cannot be reproduced without it. It will ask for that instead of guessing.

## Questions

### Which releases can it compare?

Any tagged versions or builds your team can run. Tell it which two to compare.

### What if it cannot reproduce the bug?

It says so, lists exactly what it tried, and asks for missing details such as the account or browser.

### Can it find the commit that caused the bug?

Yes. It narrows down the commits between two releases and names the first one that breaks the behavior.

## More qa workflows

-   [Test a branch in a real browser before merge Every change gets clicked through in a real browser, with a video. QA · When something happens Works with Slack, Email.](https://maito.app/workflows/test-a-branch-in-a-real-browser-before-merge)
-   [Nightly regression run Your key flows get tested every night, with a report in the morning. QA · On a schedule Works with Slack, Email.](https://maito.app/workflows/nightly-regression-run)
-   [Write test cases from a spec Turn a feature spec into a checklist of test cases, including edge cases. QA · When you ask Works with Box.](https://maito.app/workflows/write-test-cases-from-a-spec)
-   [Check the site on many screen sizes See how key pages look on phones, tablets and wide screens. QA · When you ask Works with Slack, Email.](https://maito.app/workflows/check-the-site-on-many-screen-sizes)
-   [Check for broken links and pages Crawl your site and docs for broken links, missing images and errors. QA · On a schedule Works with Slack, Email.](https://maito.app/workflows/check-for-broken-links-and-pages)

[See all workflows](https://maito.app/workflows)

## Put your AI teammate to work.

Set it up in minutes. Start with this one, and let it earn the next one.

[Put Maito to work](https://maito.app/login?returnTo=%2Fworkflows%2Freproduce-a-reported-bug-against-the-last-release)[Book a demo](mailto:support@maito.app?subject=Maito%20demo)