release: 1.16.0 - #188
release: 1.16.0#188openai-sdks[bot] wants to merge 1 commit into
Conversation
Castiron custom code✅ No new custom-code files detected. 5 mixed files remain; 0 existing customizations changed. Compared 5 existing customizations unchanged
A changed generated baseline means this report cannot reliably identify which handwritten lines changed. Inspect the custom-code diffDownload the exact patch produced by this run (requires repository access): gh run download 35563284620 --repo openai/openai-cli \
--name castiron-custom-code-35563284620-1 --dir /tmp/castiron-custom-code-35563284620-1
git apply --stat /tmp/castiron-custom-code-35563284620-1/custom-code.patch
cat /tmp/castiron-custom-code-35563284620-1/custom-code.patchOr reproduce it from an SDK checkout containing the vendored reporter: git fetch --no-tags origin 0169bff050ff9c05c4609b669c06709306d464fa 952661e0cdca21c2dce517fd2b5c944ac65222cb
python3 scripts/castiron/custom_code_report.py report \
--base 0169bff050ff9c05c4609b669c06709306d464fa \
--head 952661e0cdca21c2dce517fd2b5c944ac65222cb --fetch --require-head-hash --public \
--out /tmp/castiron-custom-code-952661e0cdca
cat /tmp/castiron-custom-code-952661e0cdca/custom-code.patchThis is the current full custom patch for mixed files, not an attribution of only the handwritten lines changed by this PR. |
03955a5 to
c3a0049
Compare
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: c3a00493dc
ℹ️ About Codex in GitHub
Codex has been enabled to automatically 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 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
369e82a to
21c76c5
Compare
d9aca5c to
2eb9370
Compare
saioai
left a comment
There was a problem hiding this comment.
i double checked the latest release head. #76 and #117 are on main but still missing from Bug Fixes. the release bot says it can't parse the Go examples in their commit messages, and its refresh after #34 skipped them again. can we add simple commit overrides to those merged PRs and rerun it before tagging 1.16.0?
4a158e0 to
9f7b7cd
Compare
9f7b7cd to
bf23d34
Compare
54eae88 to
cdf1d65
Compare
|
Please include #202 before merging this 1.16.0 release. It adds the built-in MCP connector deprecation and remote-MCP migration guidance to Responses CLI help and the API reference, while preserving compatibility with older models. The update is generated against current main, including the merged webhook commands and Go 3.63.0. Local compile/build and both help pages are verified; public CI and review are still pending. |
71d60b4 to
f9b65c3
Compare
|
@saioai both missing fixes are now in the 1.16.0 Bug Fixes section and CHANGELOG.md: #76 (narrow numeric query parameters) and #117 (static string width underflow). Added Release Please commit overrides to the two merged PRs and reran the release bot successfully. Verified the refreshed head f9b65c3 adds only those two changelog entries; the version and MCP update #202 are preserved. Could you re-review the release-note fix? |
9ae4692 to
9231cbe
Compare
9231cbe to
952661e
Compare
Automated Release PR
1.16.0 (2026-09-21)
Features
Bug Fixes
Chores
Documentation
This PR was generated with Release Please. See documentation.