Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 532b8ada11
ℹ️ About Codex in GitHub
Your team has set up Codex to 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 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
|
||
| **Scan failure reason**: When a scan fails, the scan detail page now shows the failure message from the engine so you know exactly what went wrong. | ||
|
|
||
| **Bot PR review on GitHub**: Pull requests opened by bots - Dependabot, Renovate, GitHub Actions - are now reviewed on GitHub, matching the behavior already in place for GitLab and Bitbucket. |
There was a problem hiding this comment.
Qualify bot reviews with the trust eligibility requirement
For a PR opened by one of these named bots that GitHub does not identify as trusted for the target repository, this categorical statement promises an automatic review even though code-review/config.mdx lines 80–84 says untrusted bots and outside contributors are not auto-scanned; the August changelog entry likewise limits this behavior to eligible same-repository PRs. Preserve that eligibility qualification here so users do not expect forked or untrusted bot PRs to be reviewed.
Useful? React with 👍 / 👎.
PRs #70, #71 and #73 were each generated from the same baseline (c5f6cff) over a widening commit window, so they described the same release three times with conflicting details. This folds them into a single September 18 entry: - keeps every distinct item across the three drafts, including the GitLab tag/commit scan target that only #70 and #71 caught - fixes the API key claim (personal settings, not org settings) to match #70/#71 and the merged personal settings page - reframes bot PR review on GitHub as the fix it is, since the August 3 entry already announced the feature, and keeps it consistent with the trusted-bot wording in code-review/config.mdx - edits the copy to the changelog's existing voice and fixes the Prettier failure on the original branch Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
|
Superseded by #73, which merges this entry with #71 into a single September 18, 2026 changelog entry. All three PRs were generated from the same baseline ( |
* docs: add changelog entry for September 18, 2026 * docs: consolidate Sept 15/16/18 changelog drafts into one entry PRs #70, #71 and #73 were each generated from the same baseline (c5f6cff) over a widening commit window, so they described the same release three times with conflicting details. This folds them into a single September 18 entry: - keeps every distinct item across the three drafts, including the GitLab tag/commit scan target that only #70 and #71 caught - fixes the API key claim (personal settings, not org settings) to match #70/#71 and the merged personal settings page - reframes bot PR review on GitHub as the fix it is, since the August 3 entry already announced the feature, and keeps it consistent with the trusted-bot wording in code-review/config.mdx - edits the copy to the changelog's existing voice and fixes the Prettier failure on the original branch Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> --------- Co-authored-by: setlin-hacktron <280193300+setlin-hacktron@users.noreply.github.com> Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
Documentation TODOs
These shipped features still need docs. The changelog links only to pages that already exist - add or update these, then link them:
Note
Low Risk
Documentation-only change to
changelog.mdx; no application code or runtime behavior is modified in this PR.Overview
Publishes the September 15, 2026 product changelog and advances the workflow marker to production commit
9ef27ae.The new
<Update>block documents a broad release spanning findings UX (editable OWASP Top 10:2025 category, CWE and fix text, redesigned drawer/table), scan visibility (engine failure messages on failed scans), Code Review (GitHub bot PR reviews, dashboard Application filter on PR Review), Whitebox (GitLab tag/commit pinning), integrations (Linear triage status sync), remediation (auto-retry on stale diffs, auto-close fix PRs when fixes land elsewhere), account/settings (member API keys, unified/personal-settings), automations (delete from detail page), and on-prem (self-managed GitLab MR scanning, GHES via GitHub App, license details and expiry gating). Footer links point at existing platform docs pages.Reviewed by Cursor Bugbot for commit 532b8ad. Bugbot is set up for automated code reviews on this repo. Configure here.