Fix version mismatch in OpenAPI and changelog #804
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What this fixes
The API changelog had a section header dated
2025-11-17, but the openapi.yaml version is2025-10-17. This was confusing because they appeared to be tracking the same thing but didn't match.What happened
2025-10-172025-11-17as part of the v1.3.9 release processThe problem:
2025-11-17was the date the release was cut, not the API version. Since there were no openapi.yaml changes between Oct 17 and Nov 17, the changelog section should match the API version (2025-10-17), not the internal release date.The fix
Change the changelog header from
## 2025-11-17to## 2025-10-17to align with the openapi.yaml version that consumers actually use.@domdomegg am I correct in thinking this was just a typo? Or was the distinction intentional?
Authored by Claude Code, reviewed by me.