Update changelogs from fern repo (#6949)

Co-authored-by: thesandlord <8902396+thesandlord@users.noreply.github.com>

Author: thesandlord

fern/products/cli-api-reference/cli-changelog/2026-09-14.mdx

@@ -1,3 +1,9 @@
+## 5.121.2
+**`(fix):`** Autogenerated examples now include required nullable properties with an explicit `null` instead of omitting them.
+Previously these properties were treated as optional, so generated SDK examples and wire tests could omit a key
+that the serialization layer requires.
+
+
 ## 5.121.1
 **`(fix):`** `fern generate --local` without a `FERN_TOKEN` (and air-gapped remote generation) now enables
 pagination and OAuth client generation by default instead of silently disabling them. Previously

fern/products/sdks/generators/typescript/changelog/2026-09-14.mdx

@@ -1,3 +1,22 @@
+## 3.94.0
+**`(feat):`** Add a `websocketHandlerMode` config option (`"replace" | "accumulate"`, defaults to `"replace"`)
+for generated WebSocket `Socket` classes. With `accumulate`, multiple `on()` handlers for the same
+event are all kept and run in registration order instead of the last one replacing the previous.
+Generated sockets now also expose `off(event, callback)` to detach a handler in both modes.
+Defaults to `replace`, so generated output is unchanged unless the option is enabled.
+
+
+**`(fix):`** Fix the generated README/reference pagination snippet, which assigned `page.getNextPage()`
+without `await` and therefore did not type-check.
+
+
+**`(feat):`** Add an optional `shouldReconnect(event: CloseEvent) => boolean` option to `ReconnectingWebSocket` and to the
+generated WebSocket `connect()` args. Return `false` to treat a close as terminal and suppress the automatic
+reconnect (e.g. after the client sent an end-of-stream message and the server closed with a non-1000 code).
+Defaults to the existing behaviour of reconnecting on any close code other than 1000. Also clarifies the
+`reconnectAttempts` docstring (defaults to 30; set to 0 to disable reconnecting).
+
+
 ## 3.93.1
 **`(fix):`** The generated README now always includes a Pagination section (and pagination usage snippets)
 when the API has paginated endpoints, matching the client which always returns `core.Page`.