andygrove opened a new pull request, #2008:
URL: https://github.com/apache/datafusion-ballista/pull/2008

   # Which issue does this PR close?
   
   <!-- No tracked issue; prevents the release-build startup_failure from 
recurring on main. -->
   
   Closes #.
   
   # Rationale for this change
   
   The `Python Release Build` workflow fails with `startup_failure` when an 
`*-rc*` tag is pushed, because the ASF INFRA third-party actions allowlist 
rejects the run before any job starts:
   
   > The action dtolnay/rust-toolchain@29eef336d9b2848a0b548edc03f92a220660cdb8 
is not allowed in apache/datafusion-ballista because all actions must be from a 
repository owned by your enterprise, created by GitHub, or match one of the 
patterns: ...
   
   That SHA was introduced in #1748 but is not on the allowlist. It went 
unnoticed because the workflow only runs on `*-rc*` tags and `python/**` PRs, 
so the pin on `main` was never exercised until the `54.0.0-rc1` tag was cut 
from `branch-54` ([failing 
run](https://github.com/apache/datafusion-ballista/actions/runs/29200296372)).
   
   The equivalent fix for the release branch is #2007; this PR mirrors it to 
`main` so the next release branch does not reintroduce the problem.
   
   # What changes are included in this PR?
   
   Replace `dtolnay/rust-toolchain@<sha>` with plain `rustup` shell commands in 
`build.yml` (5 steps) and `web-tui.yml` (1 step), matching how `rust.yml` 
already installs the toolchain. This removes the third-party-action dependency 
entirely, so a future action bump cannot re-break the release build.
   
   # Are there any user-facing changes?
   
   No. CI-only change.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to