ory/cli v1.3.3

on GitHub

The NPM @ory/cli wrapper now forwards termination signals to Ory CLI, avoiding orphaned processes.
-----BEGIN SSH SIGNATURE-----
U1NIU0lHAAAAAQAAAZcAAAAHc3NoLXJzYQAAAAMBAAEAAAGBALTNqKd862nD5NeOdq/MKV
+hQrquSX0gBWkaTEUAfNiW2SzaUxuwAkRYpMkXkiU6tTRW4AgHxQ5K3VQMi5fjx4NxiiRI
Cot1AfGC59BLjptq7RT1Dt1YTIX/sEr7gPsuv89GzQLnbjCvZ93AXn1Ai9HROwfPCyWPY8
g/UR4doH/OWdMYo7LKn5IP8n52LiqFUqoioPPRgho/8rahT8ST6tSJ/7h8D8QVjevIPPvz
XM4W/w0H9Jbdx5E/WT7ILqL9DsJjz9zbydgLw78DoeapF8rrpVBB5oy+jjE04DGNxE0qIx
6bAPiRSN2LwxJW1pmKPbz87XDnrX/Yt8FZ2ypMRrkrrfTP/prVAzLQYw3GXMxR8rirONtj
7TVh4SPEaCuNsXSn8jgYVrsnctGo+xzSn5JplSQ2imcd9IJJPBTz1XoHDhl2ORq6cFm0D/
ae0i9e6XV65fk6+O5u3OMnzvtAGZJGe5k9ko+RR54Yx7y0r3CC649HYAG6WS8d4t0YaLp1
+wAAAANnaXQAAAAAAAAABnNoYTUxMgAAAZQAAAAMcnNhLXNoYTItNTEyAAABgI6Ev4DeyQ
xwwqLG5EA+eGnKlmw2Vh8Jck4kv3L3+B+VA1kiIsTobMhcPRfug9lqf5PA/Bpk93nd2pUS
C+liJWGXEpfdlKjX4wl8keMz2pnYFf+Et+8eRmvwOF4ZnkbDbbzHfaVoXqBraHDfH8HlcY
j7VXLB5x71HSi29kZYKMKsXE/bB6TrpSl4O0YEQ9tF7dnnxJ3Iw19EnrQWLQLxQZXuvGbT
v09slMiZ72n1RHjzD0s/rJ5tuGmXFT5zQZkvN+jTZkB8qM6eSFvU89RH5cUF3k2YnLXKeZ
XDCp3lSy5EsBlubOgSgbdgyZTUACJj5yD9z01Lu9cHO+4d7JJiSxPSXFEqQvJV4nwXDKHT
Ngz9/1zRV6UCmQxS7BRDgz12evReu6UyJE81YbpDlBe3JuuSxARQNS02V4Df4AWFcTlRMo
Ynsz5pX8QebYgjXYCgge5VnZwn8tBgFCdURne6T+qBCRlkpGSErdGKN+cRzW2Ej7Ue+yuG
Fb17E/PKOD3ygQ==
-----END SSH SIGNATURE-----

Bug Fixes

• Forward termination signals to the CLI binary (#462) (4b2a699):

  The npm launcher spawned the Ory CLI binary with spawnSync and installed no
  signal handlers, so a SIGINT/SIGTERM/SIGHUP delivered to the launcher ended
  the launcher alone and orphaned the binary. ory tunnel and ory proxy
  create a temporary Ory Network API key and delete it in their graceful
  shutdown handler; an orphaned process never runs that handler, so the key
  lingered until its expiry and the running proxy kept serving.

  Spawn the binary asynchronously and forward SIGINT, SIGTERM and SIGHUP to
  it, then exit with the child's status — or, when the child was killed by a
  signal, re-raise that signal on the launcher so callers observe the same
  termination as before. This restores the behaviour callers had when they
  ran the binary directly.

  Add npm/run.test.js (node:test) covering argument passthrough, exit-status
  propagation, signal forwarding, signal-based termination, and the
  missing-binary error, wired into CI as the test-launcher job. The test file
  is excluded from the published package by the existing files allowlist.

Code Generation

• Pin v1.3.3 release commit (da08c71):

  Bumps from v1.3.3-pre.0

Changelog

• da08c71 autogen: pin v1.3.3 release commit
• 4b2a699 fix: forward termination signals to the CLI binary (#462)

Artifacts can be verified with cosign using this public key.