chore: upgrade minimum node version to 20

[maksadbek]

also update the E2E test workflows

[derevnjuk]

@maksadbek this contradicts the requirements. We are committed to supporting last 3 LTS versions (e.g., 18, 20, 22). Your changes could be harmful from both a product and dev perspective, as many workflows in Bright still rely on v18 (and can rely until the end of April)

@orubin @bararchy fyi

[adirdidi]

@maksadbek this contradicts the requirements. We are committed to supporting last 3 LTS versions (e.g., 18, 20, 22). Your changes could be harmful from both a product and dev perspective, as many workflows in Bright still rely on v18 (and can rely until the end of April)

@orubin @bararchy fyi

We're still going to support v12 which is using node 18. I'm fine with dropping support from v13, which we're planning actively on pushing customers to upgrade to.

[derevnjuk]

Also, please update the documentation. We have already dropped support for Linux 3.9 and are planning to do the same for Node v18 (as we have already done for versions 14, 16, etc.)

• https://docs.brightsec.com/docs/2-standalone-installation#system-requirements
• https://docs.brightsec.com/docs/npm-yarn-installation

@adirdidi @orubin fyi

[adirdidi]

Also, please update the documentation. We have already dropped support for Linux 3.9 and are planning to do the same for Node v18 (as we have already done for versions 14, 16, etc.)

• https://docs.brightsec.com/docs/2-standalone-installation#system-requirements
• https://docs.brightsec.com/docs/npm-yarn-installation

@adirdidi @orubin fyi

This is part of the ask I made to help me with fresh data so I can update the guide :)
I asked for major OS release numbers instead of Kernel versions which are less clear to customers.

[derevnjuk]

@adirdidi there are ton of Linux flavors, so we cannot specify just one (e.g., Ubuntu v20) and assume that there are same equivalent for Fedora/Debian/etc.

IMHO using the Linux kernel version is a more preferable and common. Even the kernel might not be sufficient CLI depends on the specific version of the C library (such as glibc, musl, etc.) as well.

So, it is better to use specific kernel versions and versions of glibc/musl. Or if you prefer to specify distros, just simply say that we support only the N latest releases of A, B, and C OSes

Currently, we support >= linux kernel 4.18, glibc 2.28, and musl 1.1.24. This is equivalent to >= RHEL8, Ubuntu 20.04 (or 18.04, need to check), Debian 10, Alpine Linux 3.10.

MacOS and Windows remain as in the screenshot above.

[adirdidi]

While there are many indeed, the plan is to only specify the major ones (which I'm fine with the 4 you've specified). We can keep the 'raw' requirements if they want to use something else - but I think that enterprises won't go with something which is not one of the 4.