-
Notifications
You must be signed in to change notification settings - Fork 541
Bump Node.js to 20.x #23139
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bump Node.js to 20.x #23139
Conversation
@@ -1,2 +1,2 @@ | |||
deb https://deb.nodesource.com/node_18.x nodistro main | |||
deb-src https://deb.nodesource.com/node_18.x nodistro main | |||
deb https://deb.nodesource.com/node_20.x nodistro main |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need to update the gpg key?
3.139 Err:4 http://deb.debian.org/debian bookworm-updates InRelease
3.139 Unknown error executing apt-key
3.206 Get:8 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages [10.6 kB]
3.758 Get:9 http://deb.debian.org/debian-security bookworm-security/main amd64 Packages [246 kB]
3.827 Reading package lists...
4.224 W: Skipping acquire of configured file 'main/source/Sources' as repository 'https://deb.nodesource.com/node_20.x nodistro InRelease' does not seem to provide it (sources.list entry misspelt?)
4.224 W: GPG error: http://deb.debian.org/debian bookworm-updates InRelease: Unknown error executing apt-key
4.224 E: The repository 'http://deb.debian.org/debian bookworm-updates InRelease' is not signed.
------
Dockerfile:73
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The GPG key is correct, it looks like a problem with the docker image (and not linked to this PR in particular - it's failing on a debian repo). I'll see if we can work around it.
I'll also remove the deb-src
for node as it's useless & not working properly
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Per docker-library/python#837 (comment) this is an issue with the host running docker with that image. I am not seeing it locally or in our CI, were you seeing this on your machine ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Try updating docker on your host maybe ? In any case that's not caused by this PR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
kmeinhardt@Kevins-MacBook-Pro addons-server % make shell
docker compose exec --user olympia web bash
olympia@6c0bd9f3d4cf:~$ node -v
v20.18.3
Node 20 running, build passing. npm tests passing.
Part of mozilla/addons#15266