You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Wenchen Fan (Jira)" <ji...@apache.org> on 2026/04/02 01:55:00 UTC
[jira] [Resolved] (SPARK-56260) Pin GitHub Actions to specific SHA versions in CI workflows
[ https://issues.apache.org/jira/browse/SPARK-56260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Wenchen Fan resolved SPARK-56260.
---------------------------------
Fix Version/s: 4.2.0
Resolution: Fixed
Issue resolved by pull request 55066
[https://github.com/apache/spark/pull/55066]
> Pin GitHub Actions to specific SHA versions in CI workflows
> -----------------------------------------------------------
>
> Key: SPARK-56260
> URL: https://issues.apache.org/jira/browse/SPARK-56260
> Project: Spark
> Issue Type: Improvement
> Components: Project Infra
> Affects Versions: 4.2.0
> Reporter: Yicong Huang
> Assignee: Yicong Huang
> Priority: Major
> Labels: pull-request-available
> Fix For: 4.2.0
>
>
> Pin all GitHub Actions used in CI workflows to specific commit SHA versions instead of mutable tags (e.g., v4, v5). This is a security best practice recommended by GitHub to prevent supply chain attacks via compromised action tags.
> Currently, several actions use mutable version tags:
> - actions/checkout@v6
> - actions/setup-java@v5
> - actions/setup-python@v6
> - actions/cache@v5
> - actions/upload-artifact@v6
> - bufbuild/buf-*-action@v1
> - codecov/codecov-action@v5
> - and others
> The docker/* actions are already pinned to SHA. This ticket covers pinning the remaining actions.
> This will be done in two PRs:
> 1. Pin official actions/* to SHA
> 2. Pin third-party actions to SHA
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org