Skip to content

[No QA] Block compromised Java certificates in CI - #785

Closed
roryabraham wants to merge 1 commit into
mainfrom
rory/java-certificates-rollout
Closed

roryabraham wants to merge 1 commit into
mainfrom
rory/java-certificates-rollout

Conversation

@roryabraham

Copy link
Copy Markdown
Contributor

Details

Block compromised eMudhra certificates in the selected Zulu 17 JVM immediately after Java setup, before npm installation or the Android Gradle build. Use the shared action from Expensify/GitHub-Actions#117 so cache hits are patched and verification failure stops the job.

Context: https://expensify.slack.com/archives/C0CAUQBC89F/p1792630445125879?thread_ts=1792538940.390139

AI Tests

  • Passed: actionlint 1.17.0 on the changed workflow, strict YAML parsing, setup/blocklist/Gradle ordering checks, and git diff --check. Embedded shell/Python checks were disabled because their bodies are unchanged.
  • The Android build was not run locally; no application source changed.

Related Issues

For Expensify/GitHub-Actions#117

Manual Tests

// TODO: The human co-author must fill out the tests you ran before marking this PR as "ready for review".

Linked PRs

Expensify/GitHub-Actions#117 (merged shared action)

Apply the shared eMudhra certificate blocklist after Java setup and
cache restoration, before Java network operations. Keep the selected
JVM protected when nested Android actions would otherwise replace it.

Source: Expensify/GitHub-Actions#117
@roryabraham

Copy link
Copy Markdown
Contributor Author

Consolidated into #784; retaining that draft and preserving both branches and commit history.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant