Jens-G opened a new pull request, #3749: URL: https://github.com/apache/thrift/pull/3749
Preparatory step for THRIFT-6152 (Create Zig Binding): register the upcoming Zig binding in `build/generate-changes.py` so Zig work is filed under a `Zig` heading when the CHANGES.md draft is generated. Three one-line map entries, mirroring how the Mermaid generator was added in 810873995: | Map | Key | Route | |---|---|---| | `JIRA_COMPONENT_MAP` | `"Zig"` | JIRA components `Zig - Library` / `Zig - Compiler` | | `CLIENT_SECTION_MAP` | `"zig"` | `Client: zig` commit trailer | | `GITHUB_LABEL_MAP` | `"zig"` | GitHub PR label | All three map to the identical section string `Zig`, so the three routes collapse into one CHANGES.md section instead of several near-duplicates. Note that the `JIRA_COMPONENT_MAP` entry is not strictly load-bearing: `jira_component_to_section()` ends in `JIRA_COMPONENT_MAP.get(base, base)`, so `Zig - Library` already reduced to `Zig` via the fallback. It is included for consistency with the other bindings and to pin the canonical section name; the test comment says as much. A matching `zig` GitHub label has been created on this repository so the `GITHUB_LABEL_MAP` route has something to match. ### Tests Three cases added to `build/test_generate_changes.py`, one per route (22/22 pass). Verified they are meaningful: with the map entries reverted, the label and trailer tests fail. ``` $ python3 build/test_generate_changes.py Ran 22 tests in 0.001s OK ``` - [x] Did you create an Apache Jira ticket? — THRIFT-6152 - [x] Does your pull request title follow the pattern "THRIFT-NNNN: describe my issue"? - [x] Did you squash your changes to a single commit? - [x] Did you do your best to avoid breaking changes? 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
