docs: add changelog page#9
Conversation
Add a Mintlify changelog page backfilled from recent platform releases, with a CHANGELOG:INSERT marker for automated updates, and register it as a Changelog product plus global anchor in docs.json. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 413c0a4e76
ℹ️ 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 2026" description="Hacktron Platform"> | ||
| ## GitLab parity, enterprise GitHub, and smarter triage |
There was a problem hiding this comment.
When /changelog/rss.xml is enabled, Mintlify treats Markdown headings inside an <Update> without an rss prop as separate feed entries rather than one entry for the whole update. In this new page, each month has this ## heading plus a later ### Fixes heading, so RSS subscribers will receive fragmented items such as a standalone “Fixes” entry for a single release wave; add an rss={{...}} prop per update or remove the internal headings if each monthly block should publish once.
Useful? React with 👍 / 👎.
Remove items not visible to customers: sentiment-search digests, internal Slack bug intake, admin cost dashboard filters, admin triage export, and internal admin Slack notifications. Keep customer org-admin features (billing, seats, usage). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…rose Hide the changelog from navigation for now via Mintlify `hidden` flags (Changelog product + group, page frontmatter) and drop the global anchor. Rewrite the June and May entries to Greptile-style depth: lead with the user benefit, drop the internal-plumbing fixes (Stripe customer resolution, webhook payload sizes, diagram traces), and keep entries tight. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Reconstruct the May and June entries from web main history (author-date grouped, post-monorepo-merge). May adds on-demand `@hacktron review`; June covers GitLab MR parity, GHES, in-conversation triage, Applications in the scan wizard, pentest commit targeting, and pooled billing. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
April predates the monorepo merge and is not on web main, so reconstruct it from the archived iva + hecktron repos: public REST API, Code Review page, richer finding details (syntax highlighting + trace diagrams), context documents, flexible pentest sources, and self-serve billing. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Restore the changelog to navigation: remove the Mintlify `hidden` flags from the Changelog product, group, and page frontmatter, and re-add the global "Changelog" anchor. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Applications v0 was merged (web #59) and reverted ~5 min later (#183) and never re-landed on main, so remove it from the May and June entries. Add February 2026 (org seat billing, pentest credits, public scan disclosure, PR remediation guidance) and March 2026 (cost estimation, live scan progress, web triage, Markdown finding details, PDF pentest reports) sourced from legacy iva/hecktron main history. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: d3844cc62f
ℹ️ 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".
| **GitLab merge request reviews** — Comment `@hacktronai review` on a merge | ||
| request to get a findings summary and inline review, on par with GitHub. |
There was a problem hiding this comment.
This new GitLab MR announcement tells users to comment @hacktronai review, but the existing Code Review setup guide for both pull requests and merge requests documents the trigger as @hacktron review (code-review/setup.mdx:52), and the May changelog entry below uses the same shorter command. Users following this changelog entry on a GitLab MR can mention the wrong handle and fail to start the on-demand review, so this should match the documented trigger unless the product command has intentionally changed everywhere.
Useful? React with 👍 / 👎.
1 participant
Adds a customer-facing Changelog to the docs site.
What's here
changelog.mdx— a Mintlify changelog page (RSS enabled) using<Update>blocks, backfilled with the last two release waves (June 2026, May 2026) written in plain product language.docs.json— registers the page as a Changelog product and a global anchor.{/* CHANGELOG:INSERT */}marker so future entries are inserted automatically.How it stays updated
A companion workflow in
HacktronAI/web(changelog.yml) fires when astaging → mainPR merges, asks Claude to summarize the shipped features in plain language, and opens a PR here adding a new<Update>block at the marker. See that repo's PR for details.🤖 Generated with Claude Code