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.

5.218.2

(fix): Show FDR’s custom-domain routing rejection in the red bordered box the CLI’s own Vercel check used to print, instead of a generic “Failed to publish docs” error, and box FDR’s custom-domain routing warnings in yellow.

5.218.1

(fix): fern generate --docs now prints the warnings Fern returns when it registers your docs, such as a custom domain that is not routed through Fern yet. The custom-domain DNS check now runs on Fern’s side for every root custom domain, not just domains on Vercel, so the CLI no longer runs its own copy.

5.218.0

(feat): Add settings.search.popular-searches to docs.yml. When set to true, the empty search box lists the site’s most popular searches before the reader types. Defaults to false.

5.217.2

(fix): Running a version in fern.config.json older than 5.215.0 no longer fails in CI or asks for confirmation. The CLI prints a prominent warning and runs the pinned version. Run fern upgrade to update the pin; --allow-old-cli-version or FERN_ALLOW_OLD_CLI_VERSION=true shortens the warning.

5.217.1

(fix): Keep the Maven signature block when GitHub SDK generation runs through sdk-gen-api. The runtime bundle omits publish credentials on that route and dropped the signature with them, so Java SDKs configured for Maven Central got a release workflow that ran ./gradlew publish without the MAVEN_SIGNATURE_* secrets. The signature is now sent with empty values, so the generator writes the signed ./gradlew sonatypeCentralUpload workflow without receiving any credentials.

5.217.0

(feat): fern claim now moves the guest session’s work, like the dashboard’s claim page: after the claim it moves the docs sites and SDK builds into the organization (also with --org), which drops the guest expiry and the drop banner. New --docs-url renames the docs site and --sdk-name names the SDK. When docs.yml has a single instance, its URL is pointed at the claimed site so the next fern generate --docs updates it. If a move fails, the session is kept and rerunning fern claim retries the move.

5.216.0

(feat): After deploying a Fern-hosted MCP server, fern generate now says whether callers sign in with OAuth. When the API definition declares OAuth or OpenID Connect and sign-in is not on yet, it names the flows and links to the server’s settings in the dashboard, where OAuth sign-in can be turned on.

5.215.2

(fix): Docs profiles: each edition of a page now gets its own sitemap entry and canonical URL in fern docs dev.

5.215.1

(fix): fern --version in a project that pins a CLI older than 5.215.0 prints the pinned version again instead of failing; it no longer runs the older CLI to do it. When the CLI refuses to run an older version, the message now goes to stderr, so scripts that capture stdout (for example $(fern --version)) no longer pick it up.

5.215.0

(feat): The CLI no longer silently hands off to a version in fern.config.json older than 5.215.0. Those versions run npx from the project directory, so a project could run its own executables in place of the CLI or its tools. Interactive terminals ask for confirmation; elsewhere, pass --allow-old-cli-version or set FERN_ALLOW_OLD_CLI_VERSION=true to run the older version anyway. Without that opt-in, fern upgrade from such a project runs in the current CLI instead of the older one.

5.214.0

(feat): fern init ends with a hint for users who drive Fern through a coding agent: npx skills add fern-api/skills --all installs the Fern skills, which teach the agent the whole workflow (docs, SDKs, publishing). The “No Fern account found” error a run hits without a login or FERN_TOKEN carries the same hint next to its --guest suggestion.

5.213.0

(feat): Standalone type pages (types: true on an api navigation item) use the schema’s own example: an OpenAPI object schema’s example/examples, or one assembled from its property-level example values, reaches the Fern definition (examples), the IR (userProvidedExamples) and FDR (TypeDefinition.examples), so the XML/JSON example on the page shows those values instead of placeholders and renders every variant of a oneOf array the example lists. The schema examples are only attached for API sections with types: true (parser option objectSchemaExamples); SDK generation and fern write-definition output are unchanged.

5.212.0

(feat): Add docs profiles. A profile is a named set of values, like a product name or CLI command, that fills ${NAME} placeholders. Publish one set of pages as several editions without copying them.