Uh oh!
There was an error while loading. Please reload this page.
Merge pull request #1209 from PeterDaveHello/update-node.js - #1209
Conversation
nschonni
left a comment
There was a problem hiding this comment.
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
| x86_64) \ | ||
| ARCH='x64' \ | ||
| CHECKSUM="4c153345a08d2eeb40dfbb62f1ef6ade7ec369630f9cf9f061bf9d52b10acafc" \ | ||
| CHECKSUM="" \ |
There was a problem hiding this comment.
Yeah I forgot to use "WIP" PR, I'll use PR title to indicate that.
| x86_64) \ | ||
| ARCH='x64' \ | ||
| CHECKSUM="4c153345a08d2eeb40dfbb62f1ef6ade7ec369630f9cf9f061bf9d52b10acafc" \ | ||
| CHECKSUM="" \ |
PeterDaveHello
commented
Feb 6, 2020
@rvagg is there any chance we can help speed to the unofficial build for Alpine Linux? |
rvagg
commented
Feb 6, 2020
build failed, the release went out unsigned nodejs/node#31657 (no SHASUMS.txt.asc) |
PeterDaveHello
commented
Feb 6, 2020
Didn't notice that, thanks! |
dominykas
commented
Feb 6, 2020
Is only |
PeterDaveHello
commented
Feb 6, 2020
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? |
SimenB
commented
Feb 6, 2020
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 |
BethGriggs
commented
Feb 6, 2020
Ah sorry, the SHASUMS for v13.8.0 should now be available |
SimenB
commented
Feb 6, 2020
Thanks @BethGriggs! @rvagg does that mean the alpine versions of v13 will be available soon? |
vogsphar
commented
Feb 6, 2020
PeterDaveHello
commented
Feb 6, 2020
Oh I mean the "unofficial" build, sorry for the confusing. |
SimenB
commented
Feb 6, 2020
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
9d02541ComparePeterDaveHello
commented
Feb 6, 2020
Let's see ;) |
PeterDaveHello
commented
Feb 6, 2020
v13 unofficial build has arrived! |
9d02541 to
a0ebd1dComparedjmitche
commented
Feb 6, 2020
Fixes #2010. |
CI is unhappy...
I've restarted the two failing builds |
SimenB
commented
Feb 6, 2020
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
SimenB
commented
Feb 6, 2020
I did so now and pushed. I'll merge if CI is happy |
nodejs-github-bot
commented
Feb 6, 2020
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. |
SimenB
commented
Feb 6, 2020
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 |
rvagg
commented
Feb 7, 2020
v13 update for Alpine Linux was missing due to the delay of unofficial build for Alpine.
PeterDaveHello
commented
Feb 7, 2020
Thanks! It'll be even better if the commit message was also revise to record the changes next time ;) |
PeterDaveHello
commented
Feb 7, 2020
Node.js v13 for Alpine was sent here: #1212 🎉 |
Except v13 for Alpine Linux
See: