Changelog: June 18, 2026#25
Conversation
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 2f8f50a5a6
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| <Update label="June 18, 2026" tags={["Code Review","Whitebox","Billing"]}> | ||
| ## Dismiss a finding and your PR check clears instantly | ||
|
|
||
| **PR and MR checks update on triage**: When you mark a finding as a false positive or accepted risk, the GitHub check or GitLab commit status flips back to passing right away, with no manual re-run needed. If you later reopen the finding, the check fails again to match. |
There was a problem hiding this comment.
Qualify check clearing to the last blocker
In the fail-on-findings flow, the check status is based on the count of all findings at or above the configured threshold, so a PR/MR with multiple blocking findings will still fail after only one finding is marked false positive or accepted risk. As written, this release note says the entire GitHub/GitLab status flips back to passing whenever a finding is triaged, which can mislead teams into expecting a single dismissal to clear a gate while other blocking findings remain; qualify this as passing only when no other blocking findings remain.
Useful? React with 👍 / 👎.
Documentation TODOs
These shipped features still need docs. The changelog links only to pages that already exist - add or update these, then link them:
duplicate_offield onPATCH /rest/findings/:id), what happens to severity gating when a duplicate is involved, and how to unmark it.