fix(node): Use dl.yarnpkg.com for Yarn GPG key on all Debian versions

[superironpanda]

Problem

Yarn rotated their signing key on 2026-01-28. The previous fix (#1546) for Debian trixie
fetched the key from keys.openpgp.org using a specific fingerprint, but that source
only has the old key.

Additionally, the old signing subkeys expired on 2026-01-23, breaking all existing
installations that haven't refreshed their keys.

Solution

• Remove the trixie-specific code path
• Use dl.yarnpkg.com/debian/pubkey.gpg for all Debian versions
• This file contains both the old RSA key and the new ed25519 key (created 2026-01-28)
• Use /etc/apt/keyrings/ as the keyring location (modern standard)

Verification

$ curl -sS https://dl.yarnpkg.com/debian/pubkey.gpg | gpg --show-keys
pub   rsa4096/1646B01B86E50310 2016-10-05 [SC]
      72ECF46A56B4AD39C907BBB71646B01B86E50310
uid                            Yarn Packaging <[email protected]>
...
pub   ed25519/B42879CC6B38E118 2026-01-28 [SC]
      4EF8150F4F2D7DE44F1DFF0BB42879CC6B38E118
uid                            Yarn Packaging (2026) <[email protected]>
sub   ed25519/62D54FD4003F6525 2026-01-28 [S] [expires: 2030-01-27]

[Kaniska244]

Hi @superironpanda

Thank you for the fix. Would you kindly bump up the node feature version to 1.6.5?

[max06]

Can you please speed this up a bit? I'm currently pretty much blocked since all of my devcontainers refuse to build due to this issue.

@Kaniska244 I love updates. But please don't mix them with critical bugfixes in the same PR.

[Kaniska244]

Can you please speed this up a bit? I'm currently pretty much blocked since all of my devcontainers refuse to build due to this issue.

@Kaniska244 I love updates. But please don't mix them with critical bugfixes in the same PR.

Hi @max06

Request you to follow this issue for updates and workaround.

[superironpanda]

Hi @superironpanda

Thank you for the fix. Would you kindly bump up the node feature version to 1.6.5?

yep! Done. Please let me know if anything else needs to be modified. Thanks!

[superironpanda]

@microsoft-github-policy-service agree

[max06]

Hi @max06

Request you to follow this issue for updates and workaround.

Hi @Kaniska244

I'm aware of that workaround. But since I'm using the image as an image in my devcontainers and not as base in a local dockerfile, I can't apply the workarounds there. That's why I need that updated image.

[superironpanda]

Quick check on this. Are we able to get this merged or does it need some additional things?