release: 3.45.0#707
Conversation
…t in workflow templates
e958743 to
6f2c039
Compare
…notes # Conflicts: # .github/workflows/ci.yml
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 974d5b8478
ℹ️ About Codex in GitHub
Your team has set up Codex to 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 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| `golang.org/x/net` to v0.57.0 to address security findings and aligns the SDK | ||
| with supported Go toolchains. v3.44.0 is the final release that builds with Go | ||
| 1.22–1.24; older SDK releases do not receive guaranteed security backports. No | ||
| exported SDK API or `/v3` import path changes are included. |
There was a problem hiding this comment.
Correct the claim that the exported API is unchanged
Release consumers are told that v3.45.0 includes no exported SDK API changes, but this same commit adds the exported constants responses.ResponseErrorCodeDataResidencyMismatch and openai.BetaResponseErrorCodeDataResidencyMismatch. Qualify this as “no breaking API changes” or scope the statement specifically to the Go-version update so the published compatibility note is accurate.
Useful? React with 👍 / 👎.
Automated Release PR
3.45.0 (2026-07-22)
Full Changelog: v3.44.0...v3.45.0
Go version requirement
openai-go v3.45.0 requires Go 1.25 or newer. This release upgrades
golang.org/x/netto v0.57.0 to address security findings and aligns the SDKwith supported Go toolchains. v3.44.0 is the final release that builds with Go
1.22–1.24; older SDK releases do not receive guaranteed security backports. No
exported SDK API or
/v3import path changes are included.Features
Nonefor prompt_cache_key/safety_identifier (711460e)This pull request is managed by Stainless's GitHub App.
The semver version number is based on included commit messages. Alternatively, you can manually set the version number in the title of this pull request.
For a better experience, it is recommended to use either rebase-merge or squash-merge when merging this pull request.
🔗 Stainless website
📚 Read the docs
🙋 Reach out for help or questions