From a749bbcd60875d578e9bac8e34b5984c1a7a1060 Mon Sep 17 00:00:00 2001
From: Niels Swimberghe <3382717+Swimburger@users.noreply.github.com>
Date: Tue, 28 Oct 2025 12:54:15 -0400
Subject: [PATCH] Update publishing-to-npm.mdx

---
 .../sdks/overview/typescript/publishing-to-npm.mdx | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/fern/products/sdks/overview/typescript/publishing-to-npm.mdx b/fern/products/sdks/overview/typescript/publishing-to-npm.mdx
index 0ec156a52..0222a7b4f 100644
--- a/fern/products/sdks/overview/typescript/publishing-to-npm.mdx
+++ b/fern/products/sdks/overview/typescript/publishing-to-npm.mdx
@@ -122,7 +122,7 @@ Choose how you want to authenticate with npmjs when publishing.
 OIDC-based publishing (also known as "trusted publishing") is the most secure way to publish. With OIDC, you don't need to manage authentication tokens - npmjs trusts your GitHub repository to publish directly.
 
 <Info title="Prerequisites">
-- Fern TypeScript SDK generator version `3.12.0` or later
+- Fern TypeScript SDK generator version `3.12.2` or later
 - Fern CLI version `0.94.0` or later (only required for local generation with `--local`)
 </Info>
 
@@ -136,7 +136,7 @@ OIDC-based publishing (also known as "trusted publishing") is the most secure wa
 	  ts-sdk:
 		generators:
 		  - name: fernapi/fern-typescript-sdk
-			version: <Markdown src="/snippets/version-number-ts.mdx"/>  # Must be 3.12.0 or later
+			version: <Markdown src="/snippets/version-number-ts.mdx"/>  # Must be 3.12.2 or later
 			output:
 			  location: npm
 			  package-name: your-package-name
@@ -335,10 +335,10 @@ Select the approach that fits your situation:
 <AccordionGroup>
 <Accordion title="Path 1: Upgrade your generator (Recommended)">
 
-This is the easiest path if you can upgrade to version 3.12.0 or later of the TypeScript SDK generator.
+This is the easiest path if you can upgrade to version 3.12.2 or later of the TypeScript SDK generator.
 
 **When to use this path:**
-- You're able to upgrade to Fern TypeScript SDK generator version 3.12.0 or later
+- You're able to upgrade to Fern TypeScript SDK generator version 3.12.2 or later
 - You haven't `.fernignore`'d your CI workflow file
 
 <Steps>
@@ -359,14 +359,14 @@ This is the easiest path if you can upgrade to version 3.12.0 or later of the Ty
 
 	<Step title="Update your generators.yml">
 
-	Change the `output.token` field from `${NPM_TOKEN}` to `OIDC` and ensure you're using version `3.12.0` or later:
+	Change the `output.token` field from `${NPM_TOKEN}` to `OIDC` and ensure you're using version `3.12.2` or later:
 
 	```yaml title="generators.yml"
 	groups:
 	  ts-sdk:
 		generators:
 		  - name: fernapi/fern-typescript-sdk
-			version: <Markdown src="/snippets/version-number-ts.mdx"/>  # Must be 3.12.0 or later
+			version: <Markdown src="/snippets/version-number-ts.mdx"/>  # Must be 3.12.2 or later
 			output:
 			  location: npm
 			  package-name: your-package-name
@@ -534,7 +534,7 @@ If your workflow continues using the old token-based authentication:
 
 - Verify you've removed the `npm config set` line and the `env: NPM_TOKEN` block from the publish step
 - Check that npm CLI version 11.5.1+ is installed (add the update npm step)
-- Ensure you're using generator version 3.12.0 or later (if using Path 1)
+- Ensure you're using generator version 3.12.2 or later (if using Path 1)
 - When using `--local` generation, you need to use Fern CLI version 0.94.0 or later
 
 </Accordion>