node — Node 26.5.1-dev for Android (build #150)

Automated Android build

Node.js version	26.5.1-dev
Requested ref	v26.x
Artifact label	node
Build profile	balanced
NDK version	r29
Trigger	push
Commit	550f2361ef58705a1238ef06a2a09263bf93c4f4

"Requested ref" is the branch/tag/custom ref that was asked for
(e.g. v26.x, which is a moving branch, not a fixed version) —
"Node.js version" above is what that ref actually resolved to
for this specific build, read from src/node_version.h right
after clone. A -dev suffix means this commit is not itself a
tagged Node.js release, just wherever its release branch
currently sits.

arm64-v8a is always included when the build succeeds; armeabi-v7a
is experimental and only present below if that leg also succeeded.

Each node-v26.5.1-dev-android-<abi>.zip
contains everything needed for that ABI in one download — the
binary, its runtime companion library, and headers for
compiling native addons against it:

• node — single ELF, PIE, statically linked against libc++
  (does NOT dynamically depend on libc++_shared.so — confirmed
  absent from its NEEDED entries during the build), all symbols
  exported via -rdynamic/--export-dynamic. Rename it to lib*.so
  yourself downstream if your app needs Android to extract it
  with exec permissions.
• libc++_shared.so — an unmodified copy of the NDK's
  libc++_shared.so for that ABI, bundled for native-addon
  builds that dynamically need it at runtime. node itself
  does not load this file.
• include/node/ — Node's public headers, all of V8's and
  libuv's includes, and config.gypi, laid out the same way
  official node-vX.Y.Z-headers.tar.gz releases are, for
  node-gyp/node-addon-api via npm config set nodedir=....
  Use the zip matching your target ABI — config.gypi differs
  between arm64-v8a and armeabi-v7a, so mixing them produces a
  wrong native-addon build. (Bundled OpenSSL/zlib headers are
  not included.)