Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upMerge pull request #1209 from PeterDaveHello/update-node.js #1209
Conversation
|
Looks like a few of the unofficial Alpine builds didn't finish yet, or it the missing shas issue still being tracked on the nodejs/build repo |
| @@ -12,7 +12,7 @@ RUN addgroup -g 1000 node \ | |||
| && case "${alpineArch##*-}" in \ | |||
| x86_64) \ | |||
| ARCH='x64' \ | |||
| CHECKSUM="4c153345a08d2eeb40dfbb62f1ef6ade7ec369630f9cf9f061bf9d52b10acafc" \ | |||
| CHECKSUM="" \ | |||
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
PeterDaveHello
Feb 6, 2020
Author
Member
Yeah I forgot to use "WIP" PR, I'll use PR title to indicate that.
| @@ -12,7 +12,7 @@ RUN addgroup -g 1000 node \ | |||
| && case "${alpineArch##*-}" in \ | |||
| x86_64) \ | |||
| ARCH='x64' \ | |||
| CHECKSUM="4c153345a08d2eeb40dfbb62f1ef6ade7ec369630f9cf9f061bf9d52b10acafc" \ | |||
| CHECKSUM="" \ | |||
This comment has been minimized.
This comment has been minimized.
|
@rvagg is there any chance we can help speed to the unofficial build for Alpine Linux? |
|
build failed, the release went out unsigned nodejs/node#31657 (no SHASUMS.txt.asc) |
|
Didn't notice that, thanks! |
|
Is only |
Yes, and it's only Alpine Linux build, it's possible to ship the other versions and the other builds first, @nodejs/docker what do you think? |
|
It's not the alpine build, 13.8.0 is missing for all variants (https://nodejs.org/dist/v13.8.0/SHASUMS256.txt.asc) which is why CI is failing. v10 and v12 works for all distros. So rolling back the updates to node 13 and keeping 10 and 12 makes sense to me. Those are the LTS versions anyways, which hopefully is what most people are running in production |
|
Ah sorry, the SHASUMS for v13.8.0 should now be available |
|
Thanks @BethGriggs! @rvagg does that mean the alpine versions of v13 will be available soon? |
vogsphar
commented
Feb 6, 2020
Oh I mean the "unofficial" build, sorry for the confusing. |
|
At the time of your comment, "official" builds for v13 was also broken. Now though those should be fixed, so if you rollback v13 for alpine and force push to trigger new CI, we should be good to go |
5a52fd0
to
9d02541
|
perfect! |
|
Let's see ;) |
|
v13 unofficial build has arrived! |
9d02541
to
a0ebd1d
djmitche
commented
Feb 6, 2020
|
Fixes #2010. |
|
CI is unhappy...
I've restarted the two failing builds |
|
That fixed CI, but Alpine v13 are still wrong. Those need to be reverted |
v10.18.1 -> v10.19.0, v12.14.1 -> v12.15.0, v13.7.0 -> v13.8.0 See: - https://nodejs.org/en/blog/release/v10.19.0 - https://nodejs.org/en/blog/release/v12.15.0 - https://nodejs.org/en/blog/release/v13.8.0
|
I did so now and pushed. I'll merge if CI is happy |
|
Created PR to the official-images repo (docker-library/official-images#7429). See https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what if you are wondering when it will be available on the Docker Hub. |
|
Node 13 are missing their updates for alpine as https://unofficial-builds.nodejs.org/download/release/v13.8.0/SHASUMS256.txt is not available at this time |
v13 update for Alpine Linux was missing due to the delay of unofficial build for Alpine.
Thanks! It'll be even better if the commit message was also revise to record the changes next time ;) |
|
Node.js v13 for Alpine was sent here: #1212 |
PeterDaveHello commentedFeb 6, 2020
•
edited
Except v13 for Alpine Linux
See: