Skip to content

Changelog: June 26, 2026 #35

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
maekuss wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Changelog: June 26, 2026 #35

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 15 additions & 1 deletion changelog.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,21 @@ description: "New features, improvements, and fixes to the Hacktron platform."
rss: true
---

{/* CHANGELOG:INSERT last-prod-sha=fbbbf5cf881c716c00a469e53524fdbbecbb46fd - the changelog workflow inserts new <Update> blocks directly below this line. Do not remove this marker. */}
{/* CHANGELOG:INSERT last-prod-sha=5b1387321e41682d7c2b8d146f0371df27dbe77f - the changelog workflow inserts new <Update> blocks directly below this line. Do not remove this marker. */}

<Update label="June 26, 2026" tags={["Code Review"]}>
## Skip the noise: filter scans by author or label

**Author and label filters**: You can now control exactly which pull and merge requests Hacktron scans. Add `skip.authors`, `include.authors`, or `include.labels` to your `.hacktron/config.yaml` to exclude bot accounts, restrict scanning to specific team members, or gate scans on a trigger label. Skip rules always win over include rules, so exclusions are guaranteed.

**Fixed and resolved triage commands**: Two new commands let you close out findings directly from a PR comment: `!fixed` marks a finding as fixed in the current change, and `!resolved` marks it resolved. Both join the existing `!fp` and `!accepted_risk` commands in the triage workflow.

**Severity gate evaluates all scans**: The `fail_on` severity threshold now checks findings across every scan tied to a PR or MR, not just the most recent one. Re-scans that only diff changed files no longer clear a threshold that an earlier scan tripped.

**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)**

@chatgpt-codex-connector chatgpt-codex-connector Bot Jun 26, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge 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 👍 / 👎.

</Update>

<Update label="June 23, 2026" tags={["Context","Code Review","Whitebox","Integrations","MCP"]}>
## A new Context page for your repositories, applications, and threat models
Expand Down