Changelog: August 13, 2026 - #60
Conversation
![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: 6e82968fbf
ℹ️ 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".
|
|
||
| **On-prem edition: boot, archive uploads, and air-gapped log retrieval**: The self-hosted edition now boots correctly, accepts scan archive uploads, and retrieves engine logs without requiring an outbound internet connection. | ||
|
|
||
| **Glob patterns in author filters**: The author include/exclude filters in `.hacktron/config.yaml` (and org-wide scan settings) now accept glob patterns using `*`, `**`, `?`, and `` syntax, matching the same dialect already supported for branch and path filters. |
There was a problem hiding this comment.
This changelog item now renders the final glob feature as an empty code span (and `` syntax), so readers only see *, **, and ? and miss that brace expansion is supported. The config docs list brace expansion as part of the dialect, so this release note should include the literal brace token rather than an empty placeholder.
Useful? React with 👍 / 👎.
2 participants
Documentation TODOs
These shipped features still need docs. The changelog links only to pages that already exist - add or update these, then link them:
*,**,?,{a,b}) now supported in.hacktron/config.yamlexclude.authors/include.authorsand the equivalent org-wide settings. Readers need to know which patterns are valid, the shared safety limits (pattern length, wildcard count, brace bounds), and how this differs from the existing exact-match behavior.