-
-
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
Can't update to Node.js from v20.11.1 to v20.12.1 #3586
Comments
Same here Homebridge v1.7.0
|
We have been relying on unofficial builds from NodeJS for armv6. It looks like they had some automated build failures for 20.12.x which is currently being tracked over at nodejs/unofficial-builds#126. Once that issue gets resolved you should be able to upgrade like normal, however until then |
Works again |
Perfect. I am going to go ahead and close this ticket now. Looks like the unofficial builds that anyone using homebridge would get appear to be compiling successfully, most importantly is the armv61 build is fully functional. @Sir3lly Please open a separate ticket. You are having a different issue. |
Trying to get some required information that’s needed to fill out a ticked how do I obtain logs and configuration?
… On Apr 9, 2024, at 12:27 PM, AppleTechy ***@***.***> wrote:
Closed #3586 <#3586> as completed.
—
Reply to this email directly, view it on GitHub <#3586 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BEXDCEGI5DABHN2SJCO6OCTY4QJHHAVCNFSM6AAAAABFXCTIW2VHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJSGQYDSNZWGI4DGMY>.
You are receiving this because you were mentioned.
|
Analysis
Running the
sudo hb-service update-node
I can't update to version v20.12.1I get the following result:
ℹ Updating Node.js from v20.11.1 to v20.12.1...
ℹ Target: /opt/homebridge
✖ Request failed with status code 404
Expected Behavior
update to latest node.js version
Steps To Reproduce
running
sudo hb-service update-node
Logs
Configuration
..
Environment
Process Supervisor
hb-service
Additional Context
No response
The text was updated successfully, but these errors were encountered: