Correct timeline for npm OIDC publishing

Author: Swimburger

fern/products/sdks/overview/typescript/publishing-to-npm.mdx

@@ -8,7 +8,7 @@ registry](https://www.npmjs.com/). After following the steps on this page,
 you'll have a versioned package published on npm.
 
 <Warning title="Already publishing to npm?">
-If you're currently using token-based authentication, npmjs is deprecating long-lived tokens in early 2025. See [Migrating from token-based to OpenID Connect (OIDC) publishing](#migrating-from-token-based-to-oidc-publishing) to upgrade to the more secure OIDC authentication.
+If you're currently using token-based authentication, npmjs is deprecating long-lived tokens in mid-November 2025. See [Migrating from token-based to OpenID Connect (OIDC) publishing](#migrating-from-token-based-to-oidc-publishing) to upgrade to the more secure OIDC authentication.
 </Warning>
 
 <Frame>
@@ -113,7 +113,7 @@ groups:
 Choose how you want to authenticate with npmjs when publishing. 
 
 <Warning>
-**Starting in early 2025**, npmjs.org is deprecating long-lived authentication tokens for publishing from CI/CD workflows. **OpenID Connect (OIDC) authentication is strongly recommended** for security.
+**Starting mid-November 2025**, npmjs.org is deprecating long-lived authentication tokens for publishing from CI/CD workflows. **OpenID Connect (OIDC) authentication is strongly recommended** for security.
 </Warning>
 
 <AccordionGroup>
@@ -205,7 +205,7 @@ Provenance attestations aren't generated for packages published from private rep
 <Accordion title="Token-based authentication (Legacy)">
 
 <Warning>
-**This method is being deprecated by npmjs.org in early 2025.** Long-lived authentication tokens can be exposed in logs, compromised, and are difficult to manage and rotate. [OIDC-based authentication is strongly recommended instead](#migrating-from-token-based-to-oidc-publishing). 
+**This method is being deprecated by npmjs.org in mid-November 2025.** Long-lived authentication tokens can be exposed in logs, compromised, and are difficult to manage and rotate. [OIDC-based authentication is strongly recommended instead](#migrating-from-token-based-to-oidc-publishing).
 </Warning>
 
 <Steps>