And it is a bit random, because using the same container image node:20 on code.forgejo.org didn't show the error. Because it obtained the correct key from the server it by chance connected to.

After this PR, the first step is installing updated corepack, then this issue should be solved.

Alternatively, we could either wait for container update (but this will likely take a while) or change th container, e.g., node:23, but I have no idea, what are our requirements here.

And it is a bit random, because using the same container image node:20 on code.forgejo.org didn't show the error. Because it obtained the correct key from the server it by chance connected to. After this PR, the first step is installing updated corepack, then this issue should be solved. Alternatively, we could either wait for container update (but this will likely take a while) or change th container, e.g., node:23, but I have no idea, what are our requirements here.

earl-warren commented

2025年02月04日 08:58:04 +01:00

Contributor

Copy link

debian@runner-50-lxc:/etc/forgejo-runner$ docker pull data.forgejo.org/oci/node:20-bookworm
20-bookworm: Pulling from oci/node
Digest: sha256:bc3d86568d9a9e062cdf7036367f6e2ce201925e2912758bcd3b0e2657875a63
Status: Image is up to date for data.forgejo.org/oci/node:20-bookworm
data.forgejo.org/oci/node:20-bookworm
debian@runner-50-lxc:/etc/forgejo-runner$ docker pull node:20
20: Pulling from library/node
Digest: sha256:bc3d86568d9a9e062cdf7036367f6e2ce201925e2912758bcd3b0e2657875a63
Status: Image is up to date for node:20
docker.io/library/node:20

This is on the machine where the CI is running.

```sh debian@runner-50-lxc:/etc/forgejo-runner$ docker pull data.forgejo.org/oci/node:20-bookworm 20-bookworm: Pulling from oci/node Digest: sha256:bc3d86568d9a9e062cdf7036367f6e2ce201925e2912758bcd3b0e2657875a63 Status: Image is up to date for data.forgejo.org/oci/node:20-bookworm data.forgejo.org/oci/node:20-bookworm debian@runner-50-lxc:/etc/forgejo-runner$ docker pull node:20 20: Pulling from library/node Digest: sha256:bc3d86568d9a9e062cdf7036367f6e2ce201925e2912758bcd3b0e2657875a63 Status: Image is up to date for node:20 docker.io/library/node:20 ``` This is on the machine where the CI is running.

earl-warren commented

2025年02月04日 08:59:16 +01:00

Contributor

Copy link

After this PR, the first step is installing updated corepack, then this issue should be solved.

I'm not sure I understand why does it fail now? I'm missing something 🤔

> After this PR, the first step is installing updated corepack, then this issue should be solved. I'm not sure I understand why does it fail now? I'm missing something 🤔

mahlzahn commented

2025年02月04日 09:12:36 +01:00

Author

Member

Copy link

See here: https://github.com/nodejs/corepack/issues/612#issuecomment-2615191675

The server farm responding to https://registry.npmjs.org includes 24 different IP addresses and I guess it depends on exactly which Cloudflare server the request hits. I don't know the reason for the two different keys

I don't understand the true reason, but further down in that thread, the update to latest corepack is recommended.

See here: https://github.com/nodejs/corepack/issues/612#issuecomment-2615191675 > The server farm responding to https://registry.npmjs.org includes 24 different IP addresses and I guess it depends on exactly which Cloudflare server the request hits. I don't know the reason for the two different keys I don't understand the true reason, but further down in that thread, the update to latest corepack is recommended.

mahlzahn commented

2025年02月04日 09:33:13 +01:00

Author

Member

Copy link

@earl-warren wrote in #1066 (comment):

Still failing unfortunately 😢

(And this PR here is still using the unmodified workflow from next)

@earl-warren wrote in https://codeberg.org/forgejo/docs/pulls/1066#issuecomment-2680243: > Still failing unfortunately :cry: (And this PR here is still using the unmodified workflow from next)

earl-warren commented

2025年02月04日 09:39:48 +01:00

Contributor

Copy link

Damn, these pull_request_target always get me 😊

Damn, these `pull_request_target` always get me 😊

earl-warren approved these changes

2025年02月04日 09:39:57 +01:00

earl-warren merged commit 1b246b5040 into next

2025年02月04日 09:40:07 +01:00

mahlzahn commented

2025年02月04日 09:51:31 +01:00

Author

Member

Copy link

And, of course, for the website it is failing also for on push: https://codeberg.org/forgejo/website/actions/runs/1216/jobs/0

Let's firstly see here, if the updated workflow works.

And, of course, for the website it is failing also for on push: https://codeberg.org/forgejo/website/actions/runs/1216/jobs/0 Let's firstly see here, if the updated workflow works.

mahlzahn referenced this pull request from forgejo/website

2025年02月04日 10:43:52 +01:00

ci: fix corepack issue, see forgejo/docs#1066 #552

earl-warren referenced this pull request from a commit

2025年02月04日 11:02:41 +01:00

ci: fix corepack issue, see forgejo/docs#1066 (#552)

mahlzahn added the

backport/v7.0

backport/v10.0

labels

2025年02月05日 20:17:25 +01:00

forgejo-website commented