5.194.0
(feat): Add fern docs dev stop, which cleanly stops the fern docs dev server on port 3000, or on the port given with
--port, so agents and CI can shut down local docs without finding and killing the process. It exits 0 with a
message when there is nothing to stop, and --json writes the result to stdout. It uses a new local-only
POST /__fern/shutdown route on the fern docs dev server, alongside GET /__fern/dev-server, which identifies
the server. Both routes only accept requests from the same machine that carry the x-fern-docs-dev: 1 header.
Once the server is ready, fern docs dev prints how to stop it: press Ctrl-C, run
fern docs dev stop --port <port>, or run kill <pid> with the server’s PID. With --json, the ready event
includes the same instructions in a stop object (keys, command, kill).
5.193.3
(fix): fern generator upgrade and fern automations upgrade no longer move a generators.yml entry to a version at or past
its SDK Config cutover (for example TypeScript 4.0.0+, Python 6.0.0+), which fern generate rejects. With
--include-major, the generator upgrades within its current major instead. Cutover versions are reported
under “SDK Config migration required” with a fern sdk migrate instruction rather than an --include-major hint,
and fern automations upgrade --json lists them in sdkConfigMigrationRequired.
5.193.2
(fix): fern generate --docs --guest prints the published site’s own claim link again, next to the guest session’s
claim link. Opening it enables the Claim button in the site’s banner, which claims just the docs site into an
organization you administer; the session link (Claim it to keep this work, or fern claim) still claims the
whole session.