Changelog: June 26, 2026#35
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 645b3561c9
ℹ️ 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".
|
|
||
| **Dollar signs in findings render correctly**: Finding descriptions containing `$` no longer get misread as math notation and render as-is. | ||
|
|
||
| **[<u>Configure scan filters →</u>](/code-review/config)** |
There was a problem hiding this comment.
Point scan-filter CTA to complete setup docs
The new CTA sends users to /code-review/config, but in this commit that page's scan rules still only document skip.labels, skip.keywords, and skip.paths and never mention the announced skip.authors, include.authors, or include.labels (checked code-review/config.mdx's skip table/example). Users following the changelog to configure author or include-label filters won't get the required YAML shape or precedence, so update the config page before linking here or make this link target docs that cover the new filters.
Useful? React with 👍 / 👎.
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
Documentation TODOs
These shipped features still need docs. The changelog links only to pages that already exist - add or update these, then link them:
!fixedand!resolvedas new triage commands users can post on PR/MR finding comments, alongside the existing!fpand!accepted_riskcommands. The docs page should explain what state each command sets and when to use fixed vs. resolved.fail_on): Document that thefail_onthreshold in.hacktron/config.yamlnow evaluates findings across all scans for a PR/MR, including earlier scans not just the latest re-scan. Readers need to understand the corrected behavior and any implications for existing CI setups.