Repository navigation
Node 26.13.1 build (RHEL 8 toolchain) for LunaServer - #34
Merged
Merged
Conversation
Standard and FIPS builds configured with --experimental-enable-pointer-compression (multi-cage, V8 sandbox off) and Temporal support, with no Node or V8 source changes. Node 26 needs GCC >= 13.2, newer than Ubuntu 22.04's libstdc++ (the sandbox and remote-execution hosts). Like the official release binaries, these build on RHEL 8 (AlmaLinux 8) with gcc-toolset-14, which keeps the runtime requirements at glibc 2.28, GLIBCXX_3.4.25 and libatomic. The FIPS build compiles against OpenSSL 3.0 LTS built from source and links against the system libssl.so.3 at runtime. Each build is verified before it is published: symbol versions must be available on Ubuntu 22.04, and asana-smoke-test.js must pass with LD_BIND_NOW=1 on stock Ubuntu 22.04 and on Wolfi. Native packages are rebuilt with the same toolchain; @datadog/pprof moves to 5.20.0, the first line with Node 26 (ABI 147) support. Co-authored-by: Cursor <[email protected]>
Co-authored-by: Cursor <[email protected]>
gcc-toolset on RHEL 8 doesn't build PIE by default, so the Node 26 binaries lost the ASLR coverage our Node 22 builds got from Ubuntu's GCC. asana-verify-build.sh now fails a non-PIE build. Co-authored-by: Cursor <[email protected]>
BUILD_REF defaulted to the upstream v26.12.1 branch, so running the workflow from another branch silently built different code than the standard build. Leave it empty to build the branch the workflow runs from, as build-node.yml does. Co-authored-by: Cursor <[email protected]>
Pin almalinux:8 and Rust to the versions that built the published binaries and packages. The dnf packages, including gcc-toolset-14, still float. The binaries need GLIBCXX_3.4.21 at most and don't link libatomic.
GitHub only runs workflow_run triggers from the default branch's copy of a workflow, so this one never fired. Correct the S3 comment: main's copy builds Node 22's packages, so this branch's are uploaded by hand. Co-authored-by: Cursor <[email protected]>
Node exits on an option it doesn't know, so a release that drops one of the flags LunaServer passes should fail the smoke test, not LunaServer. Co-authored-by: Cursor <[email protected]>
6 tasks done
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Moves our Node 26 builds to 26.13.1, a security release with nine high-severity CVEs in
http2,tlsandhttp.The base branch
v26.13.1is upstream's signedv26.13.1tag, unchanged. This branch adds the same seven build commits asv26.12.1(#31), cherry-picked without conflicts and with no Node or V8 source changes. Each build file is identical to thev26.12.1branch.The builds derive the version from
src/node_version.h, so they publish to newnode-v26.13.1-releaseandnode-v26.13.1-fips-releaseslots. The native packages built for 26.12.1 keep working: a patch release has the sameNODE_MODULE_VERSIONand the same pointer-compression configuration.