Electron 27 is EOL

[alucryd]

Describe the request

Hi there, electron 27 has reached end of life on April 16, would it be possible to upgrade to a newer release?

Describe the current behavior

Electron 27 will soon be removed from that Arch Linux repositories and arduino-ide is currently blocking this removal.

Arduino IDE version

2.3.2

Operating system

Linux

Operating system version

Arch Linux

Additional context

No response

Issue checklist

• I searched for previous requests in the issue tracker
• I verified the feature was still missing when using the latest nightly build
• My request contains all necessary details

[alessandromrc]

Best would be going to Electron 30 directly... The IDE is still really outdated on it's own.

[alerque]

Since the above, even Eletron 30 is how EOL (as it 31). The current version is 34 with 3 releases supported at a time. Perhaps just as importantly 27 uses a version of NodeJS that is also EOL and now has reported CVEs. That makes it urgent for distros to try to mitigate, and the most obvious mitigation is to get EOL versions out of package repositories. For Arch Linux the very last reason to keep Electron 27 or NodeJS Hydrogen around at all is only for this package. I don't want to see it become collateral damage, but please be aware that we can't keep packaging EOL stuff forever. As an upstream project that wants to stay easily available to end users, please do consider making updating Electron an urgent priority. Thanks.

[alessandromrc]

Since the above, even Eletron 30 is how EOL (as it 31). The current version is 34 with 3 releases supported at a time. Perhaps just as importantly 27 uses a version of NodeJS that is also EOL and now has reported CVEs. That makes it urgent for distros to try to mitigate, and the most obvious mitigation is to get EOL versions out of package repositories. For Arch Linux the very last reason to keep Electron 27 or NodeJS Hydrogen around at all is only for this package. I don't want to see it become collateral damage, but please be aware that we can't keep packaging EOL stuff forever. As an upstream project that wants to stay easily available to end users, please do consider making updating Electron an urgent priority. Thanks.

From what I remember the main issue back then was Theia not being really updated... I am not aware if things changed recently but I was able to recompile the IDE with newer versions of Electron, there were lot of packages abandoned by their maintainers tho.

Like you said the focus of the IDE should be on upgrading to a newer Electron version but also either finding more "modern" packages that are currently supported or directly rewrite the functionalities of those inside the IDE sourcecode.

[alerque]

While true and fully maintained dependencies is a worthy thing to work towards, having some unmaintained deps in the SBOM is not going to get the whole app booted from distro packaging the way that using EOL'ed Electron / NodeJS is going to do. Not that it can't also have that effect of course, but the urgency scale is typically different.

[oech3]

@alessandromrc Is

I was able to recompile the IDE with newer versions of Electron,

still valid for Electron 31 on Linux and is it able to run it ? And where are libffmpeg comming from at build time?

[alessandromrc]

@alessandromrc Is

I was able to recompile the IDE with newer versions of Electron,

still valid for Electron 31 on Linux and is it able to run it ? And where are libffmpeg comming from at build time?

I really don't remember anything about libffmpeg, maybe it's a dependency that has been added later on?

[oech3]

eclipse-theia/theia#15837