Skip to content

Fix the action reference in the Gradle wrapper validation workflow - #5266

Open
kedimuzafer wants to merge 1 commit into
termux:masterfrom
kedimuzafer:fix-wrapper-validation-action-ref
Open

Fix the action reference in the Gradle wrapper validation workflow#5266
kedimuzafer wants to merge 1 commit into
termux:masterfrom
kedimuzafer:fix-wrapper-validation-action-ref

Conversation

@kedimuzafer

Copy link
Copy Markdown

gradle-wrapper-validation.yml refers to gradle/actions/wrapper-validation@5, but gradle/actions
publishes its tags as v5, v6 and so on — there is no bare 5 tag. GitHub cannot resolve the
reference, so the job dies with a startup failure before running a single step.

This has been happening on every run since the reference was introduced, including pushes to master:

2026-08-15  startup_failure  [emoji-vs16-double-width]
2026-08-13  startup_failure  [master]
2026-08-13  startup_failure  [master]
2026-08-12  startup_failure  [docs/fix-spelling]
2026-08-11  startup_failure  [codex/preserve-enter-modifiers]
2026-08-08  startup_failure  [fix/locale-result-sender-selection-fixes]

Because the failure happens at startup rather than in a step, the run has no log to open, which makes
it easy to miss — it just shows up as a red cross on every PR.

dependency-submission.yml in this repo already uses gradle/actions/dependency-submission@v5, so
this change simply matches the working sibling reference.

One character.

The workflow refers to gradle/actions/wrapper-validation@5, but gradle/actions
publishes tags as v5, v6 and so on; there is no bare 5 tag. GitHub cannot
resolve the reference, so the job dies with a startup failure before running,
on pull requests and on pushes to master alike.

The sibling reference in dependency-submission.yml already uses v5, so this
matches it.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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