Skip to content

Prepare the 0.5.3 release - #461

Merged
nezhyborets merged 1 commit into
mainfrom
release-prep-0.5.3
Oct 11, 2026
Merged

nezhyborets merged 1 commit into
mainfrom
release-prep-0.5.3

Conversation

@nezhyborets

Copy link
Copy Markdown
Collaborator

Release bookkeeping ahead of tagging 0.5.3.

Expected CI result: the API Breakage check compares against 0.5.2 and is likely to report three extension Int/Double/Bool has removed conformance to AtomicRepresentable lines. They are a false positive from the swift-http-types 1.3.1 to 1.8.0 bump changing the digester's dependency closure; no OpenAI API changed. They go away once 0.5.3 is tagged and becomes the baseline.

After merging: tag the merge commit 0.5.3 and publish a GitHub Release.

🤖 Generated with Claude Code

Finalize the changelog: the unreleased section becomes 0.5.2 (the shipped
release it was never filed under), and a 0.5.3 section covers the audio
models, the Demo function-call fix and the dependency bumps. Empty the API
breakage allowlist, since its entries were breaks against 0.5.1 that 0.5.2
already shipped, and update the local-check example in CONTRIBUTING.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@nezhyborets
nezhyborets merged commit 5129e2c into main Oct 11, 2026
12 of 13 checks passed
@nezhyborets
nezhyborets deleted the release-prep-0.5.3 branch October 11, 2026 07:06
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.

2 participants