Force push for removing an old commit from another PR

currently blocking error in the CI: error: linking with clang

the rustc_parse's panic with the latest nightly ( nightly-x86_64-unknown-linux-gnu unchanged - rustc 1.94.0-nightly (ba2142a19 2025-12-07) ) reproduced on my PC

this seems caused by rustfmt (cargo fmt)

seems same problem as rust-lang/rustfmt#6739

rust-lang/rust#149692

https://github.com/rust-lang/rust/blob/ba2142a19c1acabe770433418fa395b8a0ef47a4/compiler/rustc_parse/src/parser/diagnostics.rs#L377

@onihilist for now, could you update the other .ymls in .github as well?

@onihilist for now, could you update the other .ymls in .github as well?

@kanarus Yup I'm doing that right now !

Ok in commit 46463a3, I can't change rust-lang/crates-io-auth-action@v1 to rust-lang/crates-io-auth-action@b7e9a28eded4986ec6b1fa40eeee8f8f165559ec because : Retrieve a temporary crates.io access token using trusted publishing.

EDIT:

Same for hmarr/auto-approve-action@v4

I can't change rust-lang/crates-io-auth-action@v1 to rust-lang/crates-io-auth-action@b7e9a28eded4986ec6b1fa40eeee8f8f165559ec because : Retrieve a temporary crates.io access token using trusted publishing.

EDIT:

Same for hmarr/auto-approve-action@v4

Technically, pinning to a commit hash does not affect functionality, even for Trusted Publishing. It ensures the exact same code is executed but significantly improves security against supply chain attacks by making the dependency immutable.

edit:

pinning to a commit hash does not affect functionality

In other words, the way to specify the action's version (tag vs commit hash) does not affect the internal OIDC authentication logic (Trusted Publishing) or the auto-approving logic (GitHub API).