starred/uptime-kuma

Fork 0

mirror of https://github.com/louislam/uptime-kuma.git synced 2026-03-02 22:57:00 -05:00

Should node 14 really be supported? #2588

New issue

Closed

opened 2026-02-28 02:59:54 -05:00 by deekerman · 1 comment

deekerman commented

2026-02-28 02:59:54 -05:00

Owner

Originally created by @harryzcy on GitHub (Sep 15, 2023).

⚠️ Please verify that this bug has NOT been raised before.

I checked and didn't find similar issue

🛡️ Security Policy

I agree to have read this project Security Policy

Description

Node.js 14, 16 reached end-of-life already. Should they really be supported? They use OpenSSL 1.1.1 which is EOL as well.

I think it's better to force node>=18 in package.json and drop related tests.

👟 Reproduction steps

Use node 14

👀 Expected behavior

Exit

😓 Actual Behavior

It works

🐻 Uptime-Kuma Version

master branch

💻 Operating System and Arch

All

🌐 Browser

All

🐋 Docker Version

No response

🟩 NodeJS Version

No response

📝 Relevant log output

No response

Originally created by @harryzcy on GitHub (Sep 15, 2023). ### ⚠️ Please verify that this bug has NOT been raised before. - [X] I checked and didn't find similar issue ### 🛡️ Security Policy - [X] I agree to have read this project [Security Policy](https://github.com/louislam/uptime-kuma/security/policy) ### Description Node.js 14, 16 reached end-of-life already. Should they really be supported? They use OpenSSL 1.1.1 which is EOL as well. I think it's better to force node>=18 in `package.json` and drop related tests. ### 👟 Reproduction steps Use node 14 ### 👀 Expected behavior Exit ### 😓 Actual Behavior It works ### 🐻 Uptime-Kuma Version master branch ### 💻 Operating System and Arch All ### 🌐 Browser All ### 🐋 Docker Version _No response_ ### 🟩 NodeJS Version _No response_ ### 📝 Relevant log output _No response_

deekerman

2026-02-28 02:59:54 -05:00

closed this issue
added the
feature-request

A:core
labels

deekerman commented

2026-02-28 02:59:59 -05:00

Author

Owner

@CommanderStorm commented on GitHub (Feb 3, 2024):

I am going to close this issue as the discussion in #3747 has not shown an immediate need to upgrade this part.
=> closing as not IMMEDIATELY planned (we will do so as our dependencies require)

If there are (security/other) reasons which we are missing, we would love to hear them either in this issue (we can reopen in such a case) (if not security related) or as a security advisory if it is.

@CommanderStorm commented on GitHub (Feb 3, 2024): I am going to close this issue as the discussion in #3747 has not shown an immediate need to upgrade this part. => closing as not IMMEDIATELY planned (we will do so as our dependencies require) If there are (security/other) reasons which we are missing, we would love to hear them either in this issue (we can reopen in such a case) (if not security related) or as a security advisory if it is.

deekerman referenced this issue

2026-02-28 03:18:00 -05:00

Edge sinking structure adjustment #3098

deekerman referenced this issue

2026-02-28 03:19:31 -05:00

Need to set proxy only for MS Teams notification. #3140

deekerman referenced this issue

2026-02-28 03:53:02 -05:00

Teams Webhook Workflow no longer working on beta release #4152