build(deps): bump gradle/actions/setup-gradle from 5.0.2 to 6.3.0 - #932
build(deps): bump gradle/actions/setup-gradle from 5.0.2 to 6.3.0#932dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [gradle/actions/setup-gradle](https://github.com/gradle/actions) from 5.0.2 to 6.3.0. - [Release notes](https://github.com/gradle/actions/releases) - [Commits](gradle/actions@0723195...9c97196) --- updated-dependencies: - dependency-name: gradle/actions/setup-gradle dependency-version: 6.3.0 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
dependabot
Bot
added
the
github_actions
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 32712682813 --repo openai/openai-java \
--name castiron-custom-code-32712682813-1 --dir /tmp/castiron-custom-code-32712682813-1
git apply --stat /tmp/castiron-custom-code-32712682813-1/custom-code.patch
cat /tmp/castiron-custom-code-32712682813-1/custom-code.patchOr reproduce it from an SDK checkout containing the vendored reporter: git fetch --no-tags origin 5f499c32eb4357e2552d9f97697d63eddbc6069b b00d638427e5cd5c72bbda21bf367ba67ee2f6a9
python3 scripts/castiron/custom_code_report.py report \
--base 5f499c32eb4357e2552d9f97697d63eddbc6069b \
--head b00d638427e5cd5c72bbda21bf367ba67ee2f6a9 --fetch --require-head-hash --public \
--out /tmp/castiron-custom-code-b00d638427e5
cat /tmp/castiron-custom-code-b00d638427e5/custom-code.patchThis is the current full custom patch for mixed files, not an attribution of only the handwritten lines changed by this PR. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: b00d638427
ℹ️ 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".
|
|
||
| - name: Set up Gradle | ||
| uses: gradle/actions/setup-gradle@0723195856401067f7a2779048b490ace7a47d7c # v5.0.2 | ||
| uses: gradle/actions/setup-gradle@9c971963bec38e04b3d30dcc455b5382be2fdbfb # v6.3.0 |
There was a problem hiding this comment.
This replacement makes GradleCacheTrustPolicyTest.publishing rejects unreviewed action capabilities and cache-enabled inputs fail: the test still calls replaceFirst with the old 072319... reference, so the replacement is a no-op and its subsequent assertTrue(poisonedWorkflow != workflow) fails. Because ./scripts/build runs :buildSrc:test before building the SDK, every CI build reaches this failure; update the fixture to target the newly pinned reference.
AGENTS.md reference: AGENTS.md:L41-L45
Useful? React with 👍 / 👎.
jbeckwith-oai
left a comment
jbeckwith-oai
left a comment
There was a problem hiding this comment.
This major setup-gradle upgrade cannot merge as submitted. Exact-head CI fails the release-security regression test publishing rejects unreviewed action capabilities and cache-enabled inputs because its malicious-fixture mutation still targets the old pinned action SHA, so the release trust-policy coverage no longer validates the changed workflow. Update that regression fixture to derive or match the currently reviewed pinned revision, then rerun the full build, API/runtime compatibility, and release-security checks. Separately, setup-gradle v6 changes its default cache-provider to enhanced, which upstream documents as a closed-source proprietary caching component under separate terms. The current diff silently enables that provider across CI and runtime workflows; explicitly choose cache-provider: basic or obtain a focused review of the new cache trust boundary, data handling, and licensing. Keep publishing cache-disabled: true and preserve the read-only pull-request cache policy.
1 participant
Bumps gradle/actions/setup-gradle from 5.0.2 to 6.3.0.
Release notes
Sourced from gradle/actions/setup-gradle's releases.
... (truncated)
Commits
9c97196Bump the github-actions group across 2 directories with 9 updates (#1024)760e4a4Bump the npm-dependencies group across 1 directory with 2 updates (#1037)73e4c42Update gradle-actions-caching library to v1.0.0 (#1029)a9d1438Add dependabot ignore rules for TypeScript 7.x and@types/node25.x/26.x68f3700[bot] Update dist directory5971332Bump Gradle Wrapper to 9.6.1, wrapper checksums, and Develocity plugin to 4.5...b5bc804[bot] Update dist directorydcbab4eBump npm-dependencies group with TypeScript 6.0.3,@types/node24.x, and secu...ca8d957Move non-smoke restore-gradle-home tests back to the integ-test suite (#1032)4318659[bot] Update dist directoryDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)