Repository navigation
release/v1.2: coursier/cache-action pin no longer on the ASF actions allowlist #7572
Description
What happened?
CI runs on release/v1.2 fail at workflow parse: the branch pins coursier/cache-action v8.1.0, which is no longer on the ASF actions allowlist (its entry expired on 2026-08-05 after v8.1.1 was approved). main already uses the allowed v8.1.1 pin. Same situation as #6989/#6990. The docker action pins on the branch expire Aug 16/19 too, so worth bumping in the same pass.
Proposed fix: bump the pins in build.yml and build-and-push-images.yml to the SHAs main uses, same as #6990 did for setup-sbt.
How to reproduce?
Push to release/v1.2 or open a PR targeting it; the run fails at parse before any job starts.
Version/Branch
release/v1.2
Relevant log output
The action coursier/cache-action@90c37294538be80a558fd665531fcdc2b467b475 is not allowed in apache/texera because all actions must be from a repository owned by your enterprise, created by GitHub, or match one of the patterns: ...
Metadata
Metadata
Assignees
Labels
No labels
Activity
github-actions commentedon Aug 11, 2026
👋 Thanks for opening this issue, @xuang7!
It looks like the issue description doesn't quite follow our template yet:
Filling out the template helps reviewers understand and triage your contribution faster. Please edit the description to complete it. This message will disappear automatically once the template is followed.
You can find the template prompts by editing the description, or see CONTRIBUTING.md for the full contribution flow.
fix(deps, ci, v1.2): refresh expired and expiring action pins (apache…
chore(amber): remove the unused DeployStrategy family (apache#7705)
chore(amber): remove the unused ClosureRequest from ClientActor (apac…
chore(amber): remove the unused ReportCurrentProcessingTuple client e…