Merge branch 'main' into devalog/smart-casing

Author: devalog

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

@@ -0,0 +1,8 @@
+## 0.86.0
+**`(fix):`** Fern definition: use request bodies as reference even when only used once
+
+
+## 0.85.1
+**`(fix):`** Fix: LICENSE file mounting in Docker containers during local generation
+
+

fern/products/docs/docs.yml

@@ -199,6 +199,10 @@ navigation:
       - page: Role based access control (RBAC)
         path: ./pages/authentication/rbac.mdx
         slug: rbac
+      - page: Set up OAuth
+        path: ./pages/authentication/set-up-oauth.mdx
+        hidden: true
+        slug: set-up-oauth
       - page: API key injection
         path: ./pages/api-references/autopopulate-api-key.mdx
       - page: SSO

fern/products/docs/pages/authentication/set-up-oauth.mdx

@@ -0,0 +1,78 @@
+---
+title: Set up OAuth
+subtitle: Integrate your OAuth provider with Fern Docs
+---
+
+<Steps>
+<Step title="Create an OAuth client">
+Go to your OAuth provider's dashboard. Create a new **web application** client. This is the client that will be used by Fern to authenticate users with your OAuth provider.
+</Step>
+
+<Step title="Allowlist Fern callbacks">
+You will need to allowlist the following callback in your OAuth provider:
+`https://<your-domain>/api/fern-docs/oauth2/callback`.
+
+Replace `<your-domain>` with whatever domain you are using for your Fern Docs site. If you want to authenticate both your `.docs.buildwithfern.com` and custom domain, you will need to allowlist both.
+</Step>
+
+<Step title="Send OAuth client details to Fern">
+Fern will need the following details to configure OAuth authentication:
+- [ ] Docs domain
+- [ ] Client ID
+- [ ] Client secret
+- [ ] Authorization URL (e.g. `https://<your-oauth-tenant>/oauth2/authorize`)
+- [ ] Token URL (e.g. `https://<your-oauth-tenant>/oauth2/token`)
+- [ ] Scopes (e.g. `openid`, `profile`, `email`)
+- [ ] Issuer URL (e.g. `https://<your-domain>`)
+
+Send these details to [email protected] or in your dedicated Slack channel.
+</Step>
+
+<Step title="Wait for Fern to configure OAuth">
+Wait for Fern to configure OAuth. You will receive a notification when the site is ready to use authentication.
+</Step>
+
+<Step title="Add a custom claim to set user roles">
+Add a custom claim to your OAuth provider's token response. This claim will be used to set the user's roles in Fern Docs. The resulting token response should look something like this:
+
+```json {12-15}
+{
+  "iss": "https://your-tenant.us.auth0.com/",
+  "sub": "auth0|507f1f77bcf86cd799439011",
+  "aud": "your_client_id_here",
+  "iat": 1728388800,
+  "exp": 1728475200,
+  "email": "[email protected]",
+  "email_verified": true,
+  "name": "John Doe",
+  "nickname": "johndoe",
+  "picture": "https://s.gravatar.com/avatar/...",
+  "roles": [
+    "custom-role",
+    "user-specific-role"
+  ]
+}
+```
+
+<AccordionGroup>
+<Accordion title="Using Auth0">
+To add a custom claim to Auth0, you need to create a **custom action**. This action will be used to add the custom claim to the token response.
+
+1. Go to the **Actions** tab in the Auth0 dashboard.
+2. Create a **Custom Action**.
+3. Select **Login/Post Login**.
+4. Add logic to set a roles.
+5. Click **Create**.
+6. Add the action to your **Post Login Flow**.
+</Accordion>
+<Accordion title="Using another provider">
+If you are using a different OAuth provider, please reach out to Fern with any questions on setting up a custom claim.
+</Accordion>
+</AccordionGroup>
+</Step>
+
+<Step title="Add roles to your docs">
+See [RBAC](/docs/authentication/rbac#set-up-rbac) for more information on how to add roles to your docs.
+</Step>
+
+</Steps>

fern/products/docs/pages/navigation/products.mdx

@@ -188,6 +188,8 @@ products:
 ```
 </CodeBlock>
 
+<Markdown src="/snippets/default-version.mdx" />
+
 </Step>
 <Step title="Indicate availability">
 

fern/products/docs/pages/navigation/versions.mdx

@@ -44,7 +44,7 @@ Version-specific `yml` files:
 </Step>
 <Step title="Add your version configuration">
 
-Define a version in the top-level `docs.yml` by adding an item to the `versions` list and specifying the `display-name` and `path`. 
+Define a version in the top-level `docs.yml` by adding an item to the `versions` list and specifying the `display-name` and `path`.
 
 <CodeBlock title="docs.yml">
 ```yaml
@@ -55,6 +55,9 @@ versions:
     path: ./versions/v2.yml
 ```
 </CodeBlock>
+
+<Markdown src="/snippets/default-version.mdx" />
+
 </Step>
 <Step title="Indicate availability">
 

fern/products/sdks/overview/csharp/configuration.mdx

@@ -1,5 +1,5 @@
 ---
-title: .NET Configuration
+title: .NET configuration
 description: Configuration options for the Fern .NET SDK.
 ---
 
@@ -15,8 +15,6 @@ groups:
           client_class_name: YourApiClient
 ```
 
-## SDK configuration options
-
 <ParamField path="additional-properties" type="boolean" required={false} toc={true}>
 When enabled, allows handling of additional properties not explicitly defined in the API specification. This provides flexibility for APIs that may include extra fields in responses.
 </ParamField>

fern/products/sdks/overview/go/changelog/2025-10-08.mdx

@@ -1,3 +1,7 @@
+## 1.13.13
+**`(fix):`** final fix for embedded local packages
+
+
 ## 1.13.12
 **`(fix):`** must pin wiremock indirect dependencies to later fixed versions
 

fern/products/sdks/overview/go/configuration.mdx

@@ -1,5 +1,5 @@
 ---
-title: Go Configuration
+title: Go configuration
 description: Configuration options for the Fern Go SDK.
 ---
 
@@ -18,8 +18,6 @@ groups:
           path: ../generated/go
 ```
 
-## SDK Configuration Options
-
 <ParamField path="alwaysSendRequiredProperties" type="boolean" required={false} toc={true}>
 When enabled, ensures that all required properties are always included in API requests, even if they have default values or are otherwise optional in the implementation.
 </ParamField>

fern/products/sdks/overview/java/changelog/2025-10-08.mdx

@@ -0,0 +1,5 @@
+## 3.8.9
+**`(fix):`** Fixed dynamic snippets incorrectly placing HTTP headers in request builders. Headers now correctly
+use RequestOptions.builder().addHeader() for body requests.
+
+

fern/products/sdks/overview/java/configuration.mdx

@@ -1,5 +1,5 @@
 ---
-title: Java Configuration
+title: Java configuration
 description: Configuration options for the Fern Java SDK.
 ---
 You can customize the behavior of the Java SDK generator in `generators.yml`:
@@ -14,8 +14,6 @@ groups:
           client-class-name: YourApiClient
 ```
 
-## SDK Configuration Options
-
 <ParamField path="base-api-exception-class-name" type="string" required={false} toc={true}>
 Customizes the name of the base API exception class that all API-specific exceptions will extend. This allows you to define a custom base exception class name for better integration with your existing error handling patterns.
 </ParamField>