Skip to navigation

5.222.1

(fix): On Node 26, fern generate could stop partway through unpacking the output of a remote generation and still exit with code 0. The rest of the output was never written, and the steps after it never ran, such as deploying a hosted MCP server. The CLI now uses yauzl 3.4.0, whose read streams work on Node 26.

5.222.0

(feat): fern generate now uploads an MCP target’s customer-authored custom-tool and hook modules (the files referenced by customTools/hooks in the SDK Config) so they reach the generator and are emitted into the generated MCP server.

5.221.0

(feat): Add page-actions.options.mcp-auth to docs.yml. When true, MCP clients can sign in to the docs site’s MCP server through the site’s own password, JWT or OAuth2 login and get results scoped to that user. Defaults to false; sites without it are unchanged.

5.220.0

(feat): Send where fern generate ran with each sdk-gen-api build: the Fern project’s Git repository, branch and commit, the paths of its fern/ folder and generators.yml, and the CI run with its actor. The Fern dashboard shows it as each version’s author and source, and keeps the SDK’s Fern repository current. Nothing of it goes into generated files, and it is not part of the build’s idempotency key.

5.219.0

(feat): Add the layout.breadcrumbs.disable-non-page-ancestors docs.yml setting. When set to true, breadcrumb ancestors that aren’t pages (sections, API references and API packages without an overview page) are shown as disabled, non-clickable items. Defaults to false.

5.218.4

(fix): Generators with GitHub auto-merge (github.auto-merge: true or --auto-merge) no longer fall back to legacy Fiddle generation when sdk-gen-api is enabled. The CLI now sends autoMerge to sdk-gen-api with GitHub pull-request output, so auto-merge is enabled on the pull request it opens. Other output modes never open a pull request, so they do not send it.

5.218.3

(fix): fern generate now retries Fiddle job creation refused with 429 Too Many Requests by default (previously only with --retry-rate-limited), and retries up to 10 times (about 10 minutes of backoff) instead of 5 (about 1 minute), so large groups wait for the organization’s rate limit instead of failing. Opt out with --no-retry-rate-limited.

(fix): fern generate now retries an sdk-gen-api build submission that is refused with 429 Too Many Requests (organization rate limit, organization lock or concurrent build cap), waiting as long as the server’s Retry-After header asks, for up to 10 minutes in total. Previously the first 429 failed the generation.