-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Heads up of Node.js security releases 8 August 2023 #1945
Comments
The release is ready for integration. |
The autoupdater fails to verify the shasum for some reason: https://github.com/nodejs/docker-node/actions/runs/5818818729/job/15775983962. And the update script doesn't work on mac 😅 #1848 |
Ok, the issue is that https://nodejs.org/dist is gone, leading the Line 1 in c1a8937
Line 125 in c1a8937
/cc @nodejs/docker @nodejs/build (sorry, I don't know who to tag for the website) |
cc: @ovflowd |
I got a 404 on |
Haha, wow 😅 great catch 👍 it's definitely a bug (and regression), but adding the trailing slash should at least unblock the update |
I will create an issue for the webteam regarding the trailing slash, maybe a redirection from |
I created a PR that I hope fix this @SimenB nodejs/nodejs.org#5623 |
Ah sweet, thanks! Then I'll not change anything here. The cron runs every 15 minutes, so it'll Just Work ™️ once the URL works (as long as |
I just fixed it in the Cloudflare rule. |
|
@SimenB no tweak needed, we're not going to make the redirect approach. (We just updated Cloudflare rule, so it should be ok now) |
We actually provide |
It was already a redirect before. |
Worked: #1950 🎉 |
As per the Node.js security release process, this is the FYI that there is going to be a security release on 8 August 2023.
https://nodejs.org/en/blog/vulnerability/august-2023-security-releases
The text was updated successfully, but these errors were encountered: