Skip to content

chore(deps): bump @morojs/engine from 1.1.13 to 1.1.20 - #37

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/morojs/engine-1.1.20
Open

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/morojs/engine-1.1.20

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 16, 2026 •

Copy link
Copy Markdown
Contributor

Bumps @morojs/engine from 1.1.13 to 1.1.20.

Release notes

Sourced from @​morojs/engine's releases.

v1.1.20

@​morojs/engine 1.1.20

TLS is terminated by a bundled BoringSSL, and the bundled copy is kept current by a release that makes itself.

Nothing to change to get it, and nothing to change to keep running: update, and the default binary is the one that carries BoringSSL. A server behind a proxy that terminates TLS (nginx, a load balancer) never touches a TLS library and runs exactly the code it ran. A process whose OpenSSL is specially configured (FIPS mode, an OpenSSL config or provider option) keeps Node's OpenSSL without being asked, and so does a server whose TLS configuration BoringSSL has no support for. Additive for callers: one export (selectTls), one field on probe() (tls), one environment variable (MORO_ENGINE_TLS). What behaves differently is listed under "What changes" below.

Two binaries, one difference

Every platform package now carries two builds of the engine per Node ABI, from the same source:

Binary TLS library Loaded
..._<abi>_boringssl.node BoringSSL, inside the addon by default
..._<abi>.node the OpenSSL the running node exports — every binary up to 1.1.19 when that OpenSSL is configured, when asked for, as the fallback

probe().tls says which is loaded and why:

{ library: 'boringssl', version: '0.20261105.0', date: '2026-11-05', reason: 'default' }

The choice is made when the binding is first loaded on a thread, in this order:

  1. selectTls('boringssl' | 'openssl'), before the first probe() or serve(). Asking for the other library after that throws (MORO_ENGINE_TLS_LOADED); a loaded addon cannot be swapped. selectTls('auto') makes no choice and leaves it to the next two rules.
  2. MORO_ENGINE_TLS=boringssl|openssl|auto (node is accepted for openssl). An unknown value is an error.
  3. auto: BoringSSL, unless Node's OpenSSL has been configured — --enable-fips, --force-fips, --openssl-config, --openssl-shared-config, --openssl-legacy-provider (command line or NODE_OPTIONS), OPENSSL_CONF, OPENSSL_MODULES, or FIPS mode on. Then OpenSSL, and reason names what was found.

Two more things keep an update from breaking a running setup, both only when nobody named a library:

... (truncated)

Changelog

Sourced from @​morojs/engine's changelog.

Changelog

One file per release in https://github.com/Moro-JS/engine/blob/main/changelog; the GitHub Release for a tag carries the same text. Newest first.

  • 1.1.21 — documentation release: README and roadmap brought up to date; no source change.
  • 1.1.20 — TLS on a bundled BoringSSL (two binaries per ABI; Node's OpenSSL selected by itself under FIPS or an OpenSSL config, or with MORO_ENGINE_TLS / selectTls()); the bundled copy follows upstream by a scheduled release; probe().tls.
  • 1.1.19 — HTTP/2 (ALPN and prior knowledge, the engine's own implementation; h2spec 146/146); TLS replies written straight to the socket, AES-128-GCM preferred by default; request bodies as heap strings or lent buffers (getBodyType, getBodyText, getBodyLent), body buffers pooled per loop; epoll: each ready socket served once per loop turn.
  • 1.1.18 — request bodies collected straight into the body buffer (one copy, half the peak memory of an upload); getBody() hands the bytes over without a copy; one callback scope per WebSocket read.
  • 1.1.17 — TLS on the engine's own BIOs (one copy in, one append out, no zeroing); bodies over 8 KiB encrypted from the caller's bytes; ciphertext scratch kept up to 1 MiB.
  • 1.1.16 — wsSend() borrows its payload (the backpressure shed is deferred); ASCII text frames as one-byte strings; TLS record buffers released again.
  • 1.1.15 — WebSocket upgrades performed by the engine (setWsAutoUpgrade, handshake accessors); frames built in the cork buffer; TLS record buffers kept between records.
  • 1.1.14 — WebSocket replies corked per read (one write for a pipelined batch); one ciphertext buffer per loop on the TLS write path.
  • 1.1.13 — epoll transport: the service order is selectable (grouped, arrival, or measured auto); the default is unchanged.
  • 1.1.12 — epoll transport serves each loop turn's sockets grouped by peer CPU.
  • 1.1.11 — epoll transport on one epoll_wait per loop turn; engine-answered routes parsed and routed per request.
  • 1.1.10 — engine-answered routes parsed in place and framed from a prepared head; epoll transport the Linux default; request-registry fix.
  • 1.1.9 — parameter routes (setParamRoute, clearParamRoutes).
  • 1.1.8 — TLS release, one new native function.
  • 1.1.7 — correctness release with one transport improvement.
  • 1.1.6 — the JS boundary: prepared templates, static routes, V8 fast API calls, worker-thread teardown, PGO builds.
  • 1.1.5 — hot-path and memory-headroom audit.
  • 1.1.4 — correctness hardening from the code-quality audit.
  • 1.1.3 — security hardening, third-party audit closed.
  • 1.1.1 — hot-path performance patch.
  • 1.1.0 — pipelined response corking, zero-allocation hot path.
Commits
  • 5bf8839 chore: release v1.1.20
  • 897c24b Docs and changelog for 1.1.20: the TLS library
  • 51e2767 The bundled BoringSSL kept current: scheduled roll, release gate, both binari...
  • 57b3399 TLS on a bundled BoringSSL: a second binary per ABI, chosen by the loader
  • 829d344 chore: release v1.1.19
  • fc353b0 Changelog for 1.1.19: HTTP/2, the TLS write path, request bodies
  • 9552139 HTTP/2: ALPN on TLS, prior knowledge on cleartext, HTTP/1.1 beside it
  • 5377773 Request bodies as heap strings or lent buffers; body buffers pooled per loop
  • b72e85d TLS replies written straight to the socket; AES-128-GCM preferred by default
  • 8354ae0 Changelog for 1.1.19
  • Additional commits viewable in compare view

@dependabot
dependabot Bot requested a review from M-Chris as a code owner November 16, 2026 03:09
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Nov 16, 2026
Bumps [@morojs/engine](https://github.com/Moro-JS/engine) from 1.1.13 to 1.1.20.
- [Release notes](https://github.com/Moro-JS/engine/releases)
- [Changelog](https://github.com/Moro-JS/engine/blob/main/CHANGELOG.md)
- [Commits](Moro-JS/engine@v1.1.13...v1.1.20)

---
updated-dependencies:
- dependency-name: "@morojs/engine"
  dependency-version: 1.1.20
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/morojs/engine-1.1.20 branch from b3a4bf0 to 528656a Compare November 16, 2026 05:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants