Merge branch 'main' of https://github.com/fern-api/docs into fern/document-named-preview-links

Author: devalog

fern/fern.config.json

@@ -1,4 +1,4 @@
 {
   "organization": "fern",
-  "version": "4.35.0"
+  "version": "4.37.4"
 }

fern/products/cli-api-reference/cli-changelog/2023-08-01.mdx

@@ -5,9 +5,9 @@
     properties:
       typesReferencedOnlyByService:
         docs: "Types referenced by exactly one service."
-        type: ``map<commons.ServiceId, list<commons.TypeId>>``
+        type: `map<commons.ServiceId, list<commons.TypeId>>`
       sharedTypes:
         docs: "Types referenced by either zero or multiple services."
-        type: ``list<commons.TypeId>``
+        type: `list<commons.TypeId>`
 ```
 

fern/products/cli-api-reference/cli-changelog/2024-09-04.mdx

@@ -48,13 +48,13 @@ use them in alias declarations to minimize code duplication:
 
 ```yml
 types:
-  ``GenericTest<T>``:
+  `GenericTest<T>`:
     properties:
       value: T
       other-value: string
 
   GenericApplication:
-    type: ``GenericTest<string>``
+    type: `GenericTest<string>`
 ```
 
 More information can be found here: https://buildwithfern.com/learn/api-definition/fern/types#generics.

fern/products/cli-api-reference/cli-changelog/2025-01-14.mdx

@@ -24,7 +24,7 @@ types:
   User:
     properties:
       name: string
-      email: ``nullable<string>``
+      email: `nullable<string>`
 ```
 
 

fern/products/cli-api-reference/cli-changelog/2025-08-14.mdx

@@ -40,9 +40,9 @@ service:
       request:
         body:
           properties:
-            author: ``optional<string>``
-            tags: ``optional<list<string>>``
-            title: ``optional<string>``
+            author: `optional<string>`
+            tags: `optional<list<string>>`
+            title: `optional<string>`
         content-type: application/json
         name: UploadDocumentRequest
         ...

fern/products/cli-api-reference/cli-changelog/2026-03-17.mdx

@@ -1,3 +1,12 @@
+## 4.35.0
+**`(feat):`** Add `--id` flag to `fern generate --docs --preview` for stable preview
+URLs. When `--id <name>` is provided, the preview domain uses the given
+identifier instead of a random UUID, so subsequent runs with the same ID
+overwrite the previous preview and the URL stays constant. In non-CI
+environments the CLI checks whether the preview already exists and
+prompts for confirmation before overwriting (skip with `--force`).
+
+
 ## 4.34.0
 **`(feat):`** Add `infer-default-environment` API definition setting. When set to `false`,
 the OpenAPI importer will not automatically designate the first server as the

fern/products/cli-api-reference/cli-changelog/2026-03-18.mdx

@@ -1,3 +1,35 @@
+## 4.37.1
+**`(fix):`** Optimize protobuf buf generate to reuse a single working directory
+across all proto files. Instead of creating a new temp dir, copying
+the proto root, checking binaries, and resolving deps for every file,
+setup is done once and only `buf generate <target>` runs per file.
+The two buf generate passes (protoc-gen-openapi and protoc-gen-fern)
+also now run concurrently.
+
+
+## 4.37.0
+**`(feat):`** Auto-download `buf` CLI binary from GitHub Releases when it is not found
+on PATH. This eliminates the need for users to pre-install `buf` before
+running proto-based SDK generation. The binary is cached at `~/.fern/bin/`
+with versioning, filesystem locking, and atomic file operations.
+
+
+## 4.36.1
+**`(fix):`** Fix `getLatestRelease` returning semver prerelease tags (e.g.
+`0.0.0-dev-babaf54d`) as the latest release. When GitHub's "latest
+release" API returns a tag that is a semver prerelease, the CLI now
+falls back to scanning recent releases for the first stable
+(non-prerelease, non-draft) version. This prevents
+`computeSemanticVersion` from computing incorrect next versions.
+
+
+## 4.36.0
+**`(feat):`** Auto-download `protoc-gen-openapi` binary from GitHub Releases when it is
+not found on PATH. This eliminates the need to install Go and compile
+`protoc-gen-openapi` from source on every CI run, reducing proto-based
+SDK generation setup time by ~40 seconds.
+
+
 ## 4.34.1
 **`(fix):`** Include available group names in the error message when no group is
 specified and no default-group is set. The error now lists all groups

fern/products/cli-api-reference/cli-changelog/2026-03-19.mdx

@@ -0,0 +1,16 @@
+## 4.37.4
+**`(fix):`** Sanitize preview IDs before sending to FDR API to ensure valid DNS subdomains.
+
+
+## 4.37.3
+**`(fix):`** Sanitize preview IDs passed via `--id` to produce valid DNS subdomain
+labels.
+
+
+## 4.37.2
+**`(fix):`** Remove `cli-progress` from the published `fern-api` package's runtime
+dependencies. The package is a pure JS library that is already bundled
+into the CLI output by tsup, so it does not need to be installed
+separately at runtime.
+
+

fern/products/dashboard/pages/changelog/2026-03-17.mdx

@@ -0,0 +1,11 @@
+---
+tags: ["security"]
+---
+
+## Password-based RBAC
+
+You can now set up multiple passwords in the Dashboard, each mapped to a different role. Combined with [role-based access control (RBAC)](/learn/docs/authentication/features/rbac), this lets you control which pages and sections different groups can access — without needing JWT or OAuth.
+
+To get started, go to **Settings** > **Password** in the [Dashboard](https://dashboard.buildwithfern.com/).
+
+<Button intent="none" outlined rightIcon="arrow-right" href="/learn/dashboard/configuration/password-protection">Read the docs</Button>

fern/products/dashboard/pages/password-protection.mdx

@@ -5,7 +5,7 @@ description: Manage password protection for your documentation site from the Fer
 
 <Markdown src="/snippets/team-plan.mdx"/>
 
-Protect your published documentation site with a shared password directly from the [Fern Dashboard](https://dashboard.buildwithfern.com/). When enabled, visitors must enter the password before they can view any content.
+Protect your published documentation site with a shared password directly from the [Fern Dashboard](https://dashboard.buildwithfern.com/). When enabled, visitors must enter the password before they can view any content. You can also set up multiple passwords for use with [RBAC](/learn/docs/authentication/features/rbac).
 
 <Note>
   Password-protected sites aren't indexed by search engines.
@@ -26,18 +26,23 @@ Navigate to the [Fern Dashboard](https://dashboard.buildwithfern.com/) and selec
 Open the **Settings** page for your docs site. You'll see a **Password** card at the top of the page.
 </Step>
 
-<Step title="Set a password">
+<Step title="Set password(s)">
 
-Enter a password and click **Save**. A confirmation dialog will appear — select **Enable** to activate password protection.
+Enter a single password for your entire set, or select **Add roles** to add multiple passwords that are each mapped to a user role you define. You can add a maximum of three user roles. Click **Save** to activate password protection.
 
-Once enabled, the card displays the current password along with when and by whom it was last updated.
+Once enabled, the card displays the current password(s) along with when and by whom they were last updated.
+</Step>
+
+<Step title="Configure RBAC (optional)">
+
+If you set up multiple passwords with different user roles, configure [role-based access control (RBAC)](/learn/docs/authentication/features/rbac) in `docs.yml` to restrict pages and sections of your site by role.
 </Step>
 </Steps>
 
 ## Manage password protection
 
-In the same dialog, you can **Reset** the password, or **Remove** the password to make your site publicly accessible. 
+In the same dialog, you can **Reset** the password(s), or **Remove** the password(s) to make your site publicly accessible. 
 
-<Note title="Roles">
-  All [role types](/learn/dashboard/configuration/permissions) can view the current password. Only Admins can set, reset, or remove a password.
+<Note>
+  All [members](/learn/dashboard/configuration/permissions) can view the current password(s). Only Admins can set, reset, or remove a password.
 </Note>