release: 1.12.0

[openai-sdks]

Automated Release PR

1.12.0 (2026-09-08)

Features

• api: Add prompt cache comparison response option (#155) (aa76074)
• api: add service-account API key expiration fields (#157) (bf513cb)

Bug Fixes

• autocomplete: use distinct status for no completion (#164) (094a4ab)
• jsonview: preserve raw API fields in lazy-loaded rows (#163) (0bf80c0)
• jsonview: retain lazy-loaded items across JSON toggles (#160) (ef1b383)
• output: preserve upstream errors when streaming (#159) (1048593)
• requestflag: handle inner fields after null array objects (#162) (659eb06)
• requestflag: preserve piped query arrays (#167) (265cf63)

Chores

• api: correct function argument completion event fields (openapi-545) (#156) (465360b)
• api: document incomplete web search call status (#153) (a843cea)
• api: document throttling and model overload responses — SDK-235 (#158) (76d3959)
• migrate to forked steady (#152) (9c18bfa)

---

This PR was generated with Release Please. See documentation.

[github-actions]

Castiron custom code

✅ No new custom-code files detected.

5 mixed files remain; 0 existing customizations changed.

Compared 265cf6378ab2 → 68eacb6558d2. Generated baselines verified.

5 existing customizations unchanged

• pkg/cmd/adminorganizationcertificate.go
• pkg/cmd/cmd.go
• scripts/castiron/README.md
• scripts/castiron/custom_code_report.py
• scripts/castiron/test_custom_code_report.py

A changed generated baseline means this report cannot reliably identify which handwritten lines changed.

Inspect the custom-code diff

Download the exact patch produced by this run (requires repository access):

gh run download 34192441941 --repo openai/openai-cli \
  --name castiron-custom-code-34192441941-1 --dir /tmp/castiron-custom-code-34192441941-1
git apply --stat /tmp/castiron-custom-code-34192441941-1/custom-code.patch
cat /tmp/castiron-custom-code-34192441941-1/custom-code.patch

Or reproduce it from an SDK checkout containing the vendored reporter:

git fetch --no-tags origin 265cf6378ab2e6a27c17bc7c0b6a6cbe6dbd477b 68eacb6558d204570d5cf64fb98adbbd5ed52fe5
python3 scripts/castiron/custom_code_report.py report \
  --base 265cf6378ab2e6a27c17bc7c0b6a6cbe6dbd477b \
  --head 68eacb6558d204570d5cf64fb98adbbd5ed52fe5 --fetch --require-head-hash --public \
  --out /tmp/castiron-custom-code-68eacb6558d2
cat /tmp/castiron-custom-code-68eacb6558d2/custom-code.patch

This is the current full custom patch for mixed files, not an attribution of only the handwritten lines changed by this PR.

Full report and patch

[markstuart-oai]

@codex review

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-09-06T01:31:55.625761Z	4ae766c	Manual request
🔒 Security Review	✅ Completed 2026-09-06T01:33:13.756029Z	4ae766c	Manual request

ℹ️ 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" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. Already looking forward to the next diff.

Reviewed commit: 4ae766c1dd

ℹ️ 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".

[chatgpt-codex-connector]

Security review completed. No security issues were found in this pull request.

Reviewed commit: 4ae766c1dd

View security finding report

Only the user who started this review can view the report in Codex.

ℹ️ About Codex security reviews in GitHub

This is an experimental Codex feature. Security reviews are triggered when:

• You comment "@codex security review"
• A regular code review gets triggered (for example, "@codex review" or when a PR is opened), and you’re opted in so security review runs alongside code review

Once complete, Codex will leave suggestions, or a comment if no findings are found.