fix(ci): reduce Maven publish runner pressure - #953
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
Castiron custom code✅ No new custom-code files detected. 53 mixed files remain; 0 existing customizations changed. Compared 53 existing customizations unchanged
13 more in the full report. 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 33218883863 --repo openai/openai-java \
--name castiron-custom-code-33218883863-1 --dir /tmp/castiron-custom-code-33218883863-1
git apply --stat /tmp/castiron-custom-code-33218883863-1/custom-code.patch
cat /tmp/castiron-custom-code-33218883863-1/custom-code.patchOr reproduce it from an SDK checkout containing the vendored reporter: git fetch --no-tags origin 5f3ab4a3e839b30f0d22d4b036223c4f6f6fce4e 65ccb009a89a57481f9dc7817d2d801f03ca75e0
python3 scripts/castiron/custom_code_report.py report \
--base 5f3ab4a3e839b30f0d22d4b036223c4f6f6fce4e \
--head 65ccb009a89a57481f9dc7817d2d801f03ca75e0 --fetch --require-head-hash --public \
--out /tmp/castiron-custom-code-65ccb009a89a
cat /tmp/castiron-custom-code-65ccb009a89a/custom-code.patchThis is the current full custom patch for mixed files, not an attribution of only the handwritten lines changed by this PR. |
HAYDEN-OAI
left a comment
There was a problem hiding this comment.
Reviewed 65ccb009a89a57481f9dc7817d2d801f03ca75e0; no substantive issues found. The daemon stop precedes the JVM switch, and serialization is scoped to the final publication invocation. The isolated Gradle home, verified release source, attestation/JAR digest continuity, and publish-step-only signing credentials remain intact.
Automated Release PR --- ## [4.55.0](openai/openai-java@v4.54.0...v4.55.0) (2026-08-31) ### Features * **api:** add compute_units to Responses and Chat Completions usage ([openai#944](openai#944)) ([3e45ffb](openai@3e45ffb)) * **auth:** add X.509 token exchange ([openai#940](openai#940)) ([df0c88d](openai@df0c88d)) * integrate X.509 workload identity with OkHttp clients ([openai#948](openai#948)) ([9684d52](openai@9684d52)) ### Bug Fixes * **auth:** bind X.509 bearer attachment to its mTLS transport ([openai#949](openai#949)) ([5f3ab4a](openai@5f3ab4a)) * bind X.509 transport clients to trusted origins ([openai#946](openai#946)) ([bccb100](openai@bccb100)) * **ci:** preserve release source in Maven provenance ([openai#951](openai#951)) ([0382c7c](openai@0382c7c)), closes [openai#950](openai#950) * **ci:** reduce Maven publish runner pressure ([openai#953](openai#953)) ([02b2d0d](openai@02b2d0d)) * fail closed when protected X.509 verification cannot run ([openai#945](openai#945)) ([24089bd](openai@24089bd)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: openai-sdks[bot] <284451331+openai-sdks[bot]@users.noreply.github.com>
Summary
Context
Follow-up to #951. The provenance fix is working, but three guarded v4.53.0 recovery attempts were canceled during the cold Gradle/Dokka publication phase. Logs show the first Gradle daemon remains alive after the JVM switch and multiple Dokka tasks start concurrently during publication.
Verification
Security