Skip to content

chore(ci): pin android-emulator-runner to v2.38.0 SHA - #3927

Merged
chaokunyang merged 1 commit into
apache:mainfrom
ppkarwasz:chore/pin-android-emulator
Aug 10, 2026
Merged

chore(ci): pin android-emulator-runner to v2.38.0 SHA#3927
chaokunyang merged 1 commit into
apache:mainfrom
ppkarwasz:chore/pin-android-emulator

Conversation

@ppkarwasz

Copy link
Copy Markdown
Member

What

Pin reactivecircus/android-emulator-runner in .github/workflows/ci.yml from the floating v2 tag to the v2.38.0 commit SHA a421e43855164a8197daf9d8d40fe71c6996bb0d.

Why

Every GitHub Action used by an ASF project must be on the ASF infrastructure allowlist. apache/infrastructure-actions#1100 replaces the reactivecircus/android-emulator-runner@* wildcard entry with the v2.38.0 SHA as the permanent, Dependabot-maintained pin. The floating v2 tag stays allowlisted only as a temporary grace entry until 2026-08-25, after which remove_expired.yml drops it automatically.

That PR lists apache/fory (.github/workflows/ci.yml) among the repos still using the floating v2 tag and therefore needing migration. Without this change, the Android instrumented test job would start failing once the temporary allowlist entry expires.

v2.38.0 is the current latest release, so this is a pin, not a downgrade. CI itself is the test.

ASF projects can only use GitHub Actions that appear on the ASF
infrastructure allowlist. apache/infrastructure-actions#1100 replaces the
`reactivecircus/android-emulator-runner@*` wildcard entry with the
v2.38.0 commit SHA, keeping the floating `v2` tag allowlisted only until
2026-08-25.

Pin the action to `a421e43855164a8197daf9d8d40fe71c6996bb0d` (v2.38.0) so
the Android instrumented test job keeps running once the wildcard is
gone.

Assisted-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
ppkarwasz added a commit to ppkarwasz/infrastructure-actions that referenced this pull request Aug 10, 2026
Code search across the apache org finds no repo referencing either SHA,
so the only transitional ref still needed is the floating v2 tag used by
apache/fory (apache/fory#3927).

Assisted-By: Claude Opus 5 (Claude Code)

@chaokunyang chaokunyang left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lGTM, Thanks

@chaokunyang
chaokunyang merged commit b964449 into apache:main Aug 10, 2026
62 checks passed
@ppkarwasz
ppkarwasz deleted the chore/pin-android-emulator branch August 10, 2026 18:19
@ppkarwasz

Copy link
Copy Markdown
Member Author

Wow, that was fast!

ppkarwasz added a commit to ppkarwasz/infrastructure-actions that referenced this pull request Aug 10, 2026
apache/fory#3927 has merged, so no apache repo references the floating
v2 tag any more. The v2.38.0 SHA is now the only allowed ref.

Assisted-By: Claude Opus 5 (Claude Code)
ppkarwasz added a commit to apache/infrastructure-actions that referenced this pull request Aug 11, 2026
* Pin reactivecircus/android-emulator-runner

Replace the wildcard with the v2.38.0 SHA as the permanent,
Dependabot-maintained pin. The v2.37.0 and v2.34.0 SHAs and the
floating v2 tag (still used by 14 apache repos) are whitelisted
until 2026-08-25 to give those repos time to migrate.

Generated-by: Claude Fable 5 (Claude Code)

* Extend transitional expiry to 2026-09-09

Refresh the grace period for the v2.37.0 and v2.34.0 SHAs and the
floating v2 tag, since the original 2026-08-25 deadline was set
before this PR stalled.

Assisted-By: Claude Opus 5 (Claude Code)

* Drop unused v2.37.0 and v2.34.0 transitional pins

Code search across the apache org finds no repo referencing either SHA,
so the only transitional ref still needed is the floating v2 tag used by
apache/fory (apache/fory#3927).

Assisted-By: Claude Opus 5 (Claude Code)

* Drop the transitional v2 tag pin

apache/fory#3927 has merged, so no apache repo references the floating
v2 tag any more. The v2.38.0 SHA is now the only allowed ref.

Assisted-By: Claude Opus 5 (Claude Code)
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.

2 participants