Skip to content

Changelog: July 11, 2026#42

Open
maekuss wants to merge 2 commits into
mainfrom
changelog/ae069758
Open

Changelog: July 11, 2026#42
maekuss wants to merge 2 commits into
mainfrom
changelog/ae069758

Conversation

@maekuss

@maekuss maekuss commented Jul 11, 2026

Copy link
Copy Markdown
Contributor
  • Date: July 11, 2026
  • Commit: ae069758

Documentation TODOs

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

  • Interactive taint trace reader: Document the new step-by-step code reader in the finding detail view - how to navigate steps, what the source/propagation/sink annotations mean, and how to use the "View in host" deep-link.
  • Findings export (findings page): Document the CSV/SARIF/JSON export button on the findings list, including what fields each format includes and how active filters apply.
  • Model tier selection: Document the Default vs Legacy model picker on the cost estimation step - what each tier means for scan depth and credit cost.
  • Author and label filters in repo config: Document the skip.authors, include.authors, and include.labels keys for .hacktron/config.yaml, with examples and precedence rules.
  • GitHub inline file-level comments: Document that findings without line numbers now produce file-level comments on GitHub PRs.

@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: 362e5bd9a5

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

Comment thread changelog.mdx

**Findings export on the findings page**: The findings list now has a CSV, SARIF, and JSON export button that honors your active filters, so you can export exactly the findings you are looking at into your own tooling or ticketing system.

**Findings export via the REST API**: A new `GET /rest/findings/export` endpoint lets you pull approved findings as CSV, SARIF, or JSON over an API key. You can scope it to a single repository with the `repo_url` filter and combine it with the existing severity, state, and date filters.

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 public API path for findings export

When users follow the API reference linked from this changelog, this advertises GET /rest/findings/export, but the public API docs define https://api.hacktron.ai/v1 as the base URL and the checked OpenAPI spec has no /rest/findings/export path, only /findings and /scans/{id}/findings/export. This would lead readers to call https://api.hacktron.ai/v1/rest/findings/export, which is inconsistent with the documented public API; please either publish the endpoint in the OpenAPI/docs or change the changelog to the public path.

Useful? React with 👍 / 👎.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.

1 participant