In #3940, ARMv7 was excluded from Node.js 24 support because the Node.js project no longer publishes official binaries for it. This makes sense for moving forward, but it raises the question of ARMv7 support in general. More and more actions will target newer Node.js runtimes. If those actions can't be run on ARMv7, then it will effectively become unsupported, even though the runner itself still works fine on it.
Has this already been considered? Are there any plans to support Node.js 24+ on ARMv7 (e.g., via unofficial or community builds)? If not, should users provision their own custom Node.js builds? Is there documentation for doing so?
Clarifying this would help those of us who are still actively targeting ARMv7. This is especially relevant for embedded and IoT use cases because the hardware might not be easily replaceable. Running native CI/CD pipelines helps keep things working.
In #3940, ARMv7 was excluded from Node.js 24 support because the Node.js project no longer publishes official binaries for it. This makes sense for moving forward, but it raises the question of ARMv7 support in general. More and more actions will target newer Node.js runtimes. If those actions can't be run on ARMv7, then it will effectively become unsupported, even though the runner itself still works fine on it.
Has this already been considered? Are there any plans to support Node.js 24+ on ARMv7 (e.g., via unofficial or community builds)? If not, should users provision their own custom Node.js builds? Is there documentation for doing so?
Clarifying this would help those of us who are still actively targeting ARMv7. This is especially relevant for embedded and IoT use cases because the hardware might not be easily replaceable. Running native CI/CD pipelines helps keep things working.