• v2.30.0 3a132e2817

    v2.30.0
    All checks were successful
    release / build-and-release (push) Successful in 1m8s
    Stable

    littleisland released this 2026-11-18 00:33:41 +00:00 | 16 commits to main since this release

    NOE v2.30.0

    Filesystem operations can now process large copies and directory listings
    without holding the complete input in memory. Web Crypto also supports
    generating HMAC keys and exchanging them as JWKs, including use by jose.

    Filesystem operations

    noe:fs.iterateDir(path, {batchSize = 128, signal} = {}) returns a lazy async
    iterator of Dirent values. Opening starts on the first next request. Entries
    arrive in filesystem order, one bounded batch at a time. Concurrent next
    requests are serialized. EOF, early break, explicit close, async disposal,
    abort, and owner cleanup release the descriptor. Abort delivers the exact
    signal reason. Existing readdir APIs retain their sorted-array behavior.

    copyFile and copyFileSync share a native copy path with a 32 KiB fallback
    buffer. Initial source failures preserve an existing destination, and
    same-file aliases leave contents intact. Existing permissions and
    Root/Cwd/ReadOnly policy remain in force. Copies remain non-atomic; an I/O
    failure during copying can leave partial output. Directory iteration is
    neither recursive nor a snapshot of concurrent changes.

    See the filesystem reference,
    example, and
    implementation record.

    HMAC generation and JWK

    crypto.subtle.generateKey supports HMAC with SHA-1, SHA-256, SHA-384, and
    SHA-512, using the selected host random reader. Omitted lengths use the
    hash block size; positive explicit bit lengths are supported. HMAC importKey
    and exportKey support raw bytes and JWK. JWK algorithm, usage, key_ops, and
    extractability restrictions are checked against the requested key policy.

    Private key snapshots govern operations. Mutating public metadata, import
    arguments, or exported dictionaries cannot change a key's authority or bytes.
    The same APIs are available through global crypto and node:crypto, in main
    and Worker runtimes. jose 6.2.15 can generate, export, import, sign, and verify
    HS256/HS384/HS512 keys and tokens across Node and NOE.

    The supported surface remains an explicit Web Crypto subset. AES/RSA/EC
    key generation, key wrapping, CryptoKey structured cloning, and byte
    streams/BYOB are outside this release. JWK key material uses unpadded
    base64url; padded or whitespace-containing values are rejected. See the
    Web Crypto contract
    and jose example.

    Verification and distribution

    Implementation checks cover whole-tree unit/E2E results, affected race checks,
    vet, public types, lint, main/Worker behavior, embedded references, and
    checkout/artifact Go consumers. An external-consumer fixture usage error in
    the broad run was corrected; the complete stdlib package passed afterward,
    and unchanged passing packages are reused. Unmodified jose interoperability
    checks pass in both directions for Node/main and Node/Worker.

    Dependencies and public Go function signatures remain unchanged, including
    go-quickjs v0.38.0 with JIT disabled. Release verification reuses completed
    source checks and exercises a clean native candidate and the published native
    asset. CI builds six binaries and SHA256SUMS from the immutable tag. Publication
    includes verified installation at both existing vm201 executable paths,
    retaining previous copies. See the release checkpoints.

    Downloads