Auto-Resolve: Vulnerability status is flipping between Resolved and Needs triage

Summary

Some vulnerabilities have a recurring history of state changes between Resolved (via auto-resolve) and Needs Triage (was re-detected). Example: https://gitlab.com/gitlab-org/gitlab/-/security/vulnerabilities/136805456

What is causing this? Is this due to partial pipelines on different types of MRs? Eg. docs-only versus code change?

Additionally, the example above is in Needs Triage, and it's expected that the last note would indicate that state change.

Steps to reproduce

https://gitlab.com/gitlab-org/gitlab/-/security/vulnerabilities/136805456

Example Project

What is the current bug behavior?

1. State changes between Resolved (via auto-resolve) and Needs Triage (was re-detected).

2. The example above is in Needs Triage, and it's expected that the last note would indicate that state change.

What is the expected correct behavior?

Relevant logs and/or screenshots

Output of checks

Results of GitLab environment info

Expand for output related to GitLab environment info

 (For installations with omnibus-gitlab package run and paste the output of: \`sudo gitlab-rake gitlab:env:info\`)  (For installations from source run and paste the output of: \`sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production\`)  

Results of GitLab application Check

Expand for output related to the GitLab application check

(For installations with omnibus-gitlab package run and paste the output of:
`sudo gitlab-rake gitlab:check SANITIZE=true`)

(For installations from source run and paste the output of:
`sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true`)

(we will only investigate if the tests are passing)

Possible fixes

Patch release information for backports

If the bug fix needs to be backported in a patch release to a version under the maintenance policy, please follow the steps on the patch release runbook for GitLab engineers.

Refer to the internal "Release Information" dashboard for information about the next patch release, including the targeted versions, expected release date, and current status.

High-severity bug remediation

To remediate high-severity issues requiring an internal release for single-tenant SaaS instances, refer to the internal release process for engineers.