Skip to content

Changelog: November 5, 2026 - #109

Open
zeyu2001 wants to merge 1 commit into
mainfrom
changelog/1296a5739
Open

zeyu2001 wants to merge 1 commit into
mainfrom
changelog/1296a5739

Conversation

@zeyu2001

@zeyu2001 zeyu2001 commented Nov 5, 2026 •

Copy link
Copy Markdown
Member
  • Date: November 5, 2026
  • Commit: 1296a5739

Documentation TODOs

These shipped features still need docs. The changelog links only to pages that already exist - add or update these, then link them:

  • @hacktron Slack assistant: Document how to mention @hacktron in a channel, what questions it can answer, how approval cards work for pentest starts, and how teammates can join an existing thread.
  • Scheduled whitebox scans: Document how to create a schedule (daily/weekly/monthly/custom cron), timezone selection, scan profiles, concurrency and credit limits, and how to view execution history.
  • Start a PR review from Slack, MCP, or the API: Document the start_pr_review MCP tool and the REST endpoints (GET /rest/pull-requests, POST /rest/pull-requests/review), including required permissions and how results are published.
  • Fix in review: Document the new "fix in review" finding state, how it is set when a PR references a finding, and how findings auto-resolve when that PR merges into the finding's branch.
  • Finding mentions in PRs and Slack: Document how writing a finding ID (HAC-FD-N) in a PR title, description, branch name, or comment creates a mention activity, and how the same works from Slack messages and thread replies.
  • Finding ID auto-linking in PR descriptions and comments: Document that finding IDs are automatically rewritten as links on GitHub, GitLab, Bitbucket, and Azure DevOps, and what permissions are needed.
  • Fix PRs from Slack and MCP: Document the remediate MCP tool / REST route and how to trigger a fix PR from Slack.
  • Silent PR scanning: Document the new org setting that runs scans without publishing GitHub checks, review comments, or annotations, and how to enable it.
  • Attestation letters in Slack: Document that pasting an attestation letter URL into a connected Slack workspace unfurls a summary card, and what fields appear on it.
  • Pentest lifecycle over MCP: Document the full set of pentest MCP tools (create/update draft, estimate, start, stop, discard, upload archive, check logins) and the equivalent REST routes in the API reference.

Note

Low Risk
Documentation-only changelog update with no application or infrastructure code changes.

Overview
Adds a November 5, 2026 changelog entry and advances the workflow last-prod-sha marker to 1296a573.

The new <Update> block documents shipped capabilities: @hacktron in Slack, scheduled whitebox scans, PR reviews from Slack/MCP/API, fix in review finding state and auto-resolve on merge, finding ID mentions and auto-linking in PRs and Slack, fix PRs from Slack/MCP, silent PR scanning org setting, attestation letter unfurls in Slack, and full pentest lifecycle over MCP. Footer links point to existing docs (whitebox quickstart, automations, Slack, MCP, API reference).

Reviewed by Cursor Bugbot for commit a5bd592. Bugbot is set up for automated code reviews on this repo. Configure here.

@mintlify

mintlify Bot commented Nov 5, 2026 •

Copy link
Copy Markdown
Contributor

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated
hacktronai 🟢 Ready View Preview Nov 5, 2026, 6:12 PM

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Nov 5, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-11-05T18:15:51.078554Z a5bd592 PR opened
ℹ️ 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" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: a5bd592769

ℹ️ 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".

Comment thread changelog.mdx
<Update label="November 5, 2026" tags={["Integrations","Whitebox","Code Review","API","MCP"]}>
## Ask @Hacktron in Slack and get real answers about your security

**@Hacktron Slack assistant**: Mention @Hacktron in any Slack channel to ask about findings and scans, get a pentest priced, and kick one off with a single approval click. Teammates can jump into an existing thread and the bot acts with each person's own access.

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 Use the actual Slack app mention

For a reader following this announcement literally, @Hacktron is not the Slack app's mention name, and the bot is not available in an arbitrary channel: the setup guide requires users to run /invite @Hacktron AI before mentioning @Hacktron AI (platform/slack-assistant.mdx, lines 58–70). As written, the advertised first action will not summon the bot in an uninvited channel; use the exact app name and state the channel setup prerequisite.

AGENTS.md reference: AGENTS.md:L3-L4

Useful? React with 👍 / 👎.

This branch was successfully deployed

1 active deployment
staging — a5bd5927 Deployed Nov 5, 2026 by mintlify[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants