Skip to content

Conversation

@tadasant
Copy link
Member

What this fixes

The API changelog had a section header dated 2025-11-17, but the openapi.yaml version is 2025-10-17. This was confusing because they appeared to be tracking the same thing but didn't match.

What happened

  1. Various API changes (v0.1 introduction, endpoint removal) were made in early-to-mid October
  2. On Oct 17, commit 0828bc4 bumped the openapi.yaml version to 2025-10-17
  3. These changes sat under an "Unreleased" section in the changelog
  4. On Nov 17, commit 7b3f01a converted "Unreleased" → 2025-11-17 as part of the v1.3.9 release process

The problem: 2025-11-17 was 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-17 to ## 2025-10-17 to 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.

Change changelog section header from 2025-11-17 to 2025-10-17 to match
the version in openapi.yaml. The previous date was the internal release
date rather than the API version date.
@tadasant tadasant requested review from a team and domdomegg November 27, 2025 19:29
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.

3 participants