user102854: Yesterday this PR was merged into the Bitcoin repository, and the process described at https://bitcoincore.org/download mentions that to validate the source code, you must download the txt file with some of the devs' signatures.
Now that process is no longer valid because the file was deleted.
What will be the process to validate the source code download from now on?
I reviewed another answer like this but I can find any related to my question.

user48884: Instead of fetching the keys from keyservers by fingerprint, you can now get the keys actually used from https://github.com/bitcoin-core/guix.sigs/tree/main/builder-keys. This repository contains all of the guix attestations for Bitcoin Core releases, so it makes sense that the same repo should contain the listing of keys.

102854: <p>Yesterday this <a href="https://github.com/bitcoin/bitcoin/commit/296e88225096125b08665b97715c5b8ebb1d28ec" rel="nofollow noreferrer">PR</a> was merged into the Bitcoin repository, and the process described at <a href="https://bitcoincore.org/download" rel="nofollow noreferrer">https://bitcoincore.org/download</a> mentions that to validate the source code, you must download the txt file with some of the devs' signatures.</p>
<p>Now that process is no longer valid because the file was deleted.
What will be the process to validate the source code download from now on?</p>
<p>I reviewed another answer like <a href="https://bitcoin.stackexchange.com/questions/50185/how-to-verify-bitcoin-core-release-signing-keys/50186#50186">this</a> but I can find any related to my question.</p>
 48884: <p>Instead of fetching the keys from keyservers by fingerprint, you can now get the keys actually used from <a href="https://github.com/bitcoin-core/guix.sigs/tree/main/builder-keys" rel="nofollow noreferrer">https://github.com/bitcoin-core/guix.sigs/tree/main/builder-keys</a>. This repository contains all of the guix attestations for Bitcoin Core releases, so it makes sense that the same repo should contain the listing of keys.</p>
