docs: Update blog post

Author: amannn

docs/src/pages/blog/_meta.tsx

@@ -3,7 +3,7 @@ export default {
     title: 'Overview'
   },
   'next-intl-4-0': {
-    title: 'next-intl 4.0 beta',
+    title: 'next-intl 4.0',
     display: 'hidden'
   },
   'next-intl-3-22': {

docs/src/pages/blog/index.mdx

@@ -6,8 +6,8 @@ import StayUpdated from '@/components/StayUpdated.mdx';
 <div className="flex flex-col gap-4 py-8">
   <BlogPostLink
     href="/blog/next-intl-4-0"
-    title="next-intl 4.0 beta"
-    date="Dec 23, 2024"
+    title="next-intl 4.0"
+    date="Mar 12, 2025"
     author="By Jan Amann"
   />
   <BlogPostLink

docs/src/pages/blog/next-intl-4-0.mdx

@@ -1,13 +1,13 @@
 ---
-title: next-intl 4.0 beta
+title: next-intl 4.0
 ---
 
 import PartnerContentLink from '@/components/PartnerContentLink';
 import StayUpdated from '@/components/StayUpdated.mdx';
 
-# next-intl 4.0 beta
+# next-intl 4.0
 
-<small>Dec 23, 2024 · by Jan Amann</small>
+<small>Mar 12, 2025 · by Jan Amann</small>
 
 After a year of feature development, this release focuses on streamlining the API surface while maintaining the core architecture of `next-intl`. With many improvements already released in [previous minor versions](/blog/next-intl-3-22), this update introduces several enhancements that will improve your development experience and make working with internationalization even more seamless.
 
@@ -44,7 +44,7 @@ declare module 'next-intl' {
 }
 ```
 
-See the updated [TypeScript augmentation](https://v4.next-intl.dev/docs/workflows/typescript) guide.
+See the updated [TypeScript augmentation](/docs/workflows/typescript) guide.
 
 ## Strictly-typed locale
 
@@ -65,7 +65,7 @@ declare module 'next-intl' {
 
 By doing so, APIs like `useLocale()` or `<Link />` that either return or receive a `locale` will now pick up your app-specific `Locale` type, improving type safety across your app.
 
-To simplify narrowing of `string`-based locales, a `hasLocale` function has been added. This can for example be used in [`i18n/request.ts`](https://v4.next-intl.dev/docs/getting-started/app-router/with-i18n-routing#i18n-request) to return a valid locale:
+To simplify narrowing of `string`-based locales, a `hasLocale` function has been added. This can for example be used in [`i18n/request.ts`](/docs/getting-started/app-router/with-i18n-routing#i18n-request) to return a valid locale:
 
 ```tsx
 import {getRequestConfig} from 'next-intl/server';
@@ -148,13 +148,13 @@ t('followers', {count: 30000});
 "{count, number} followers"
 ```
 
-Due to a current limitation in TypeScript, this feature is opt-in for now. Please refer to the [strict arguments](https://v4.next-intl.dev/docs/workflows/typescript#messages-arguments) docs to learn how to enable it.
+Due to a current limitation in TypeScript, this feature is opt-in for now. Please refer to the [strict arguments](/docs/workflows/typescript#messages-arguments) docs to learn how to enable it.
 
 ## GDPR compliance [#gdpr-compliance]
 
 In order to comply with the current GDPR regulations, the following changes have been made and are relevant to you if you're using the `next-intl` middleware for i18n routing:
 
-1. The locale cookie now defaults to a session cookie that expires when a browser is closed.
+1. The locale cookie now defaults to a session cookie that expires when the browser is closed.
 2. The locale cookie is now only set when a user switches to a locale that doesn't match the `accept-language` header.
 
 If you want to increase the cookie expiration, e.g. because you're informing users about the usage of cookies or if GDPR doesn't apply to your app, you can use the `maxAge` attribute to do so:
@@ -174,11 +174,11 @@ export const routing = defineRouting({
 });
 ```
 
-Since the cookie is now only available after a locale switch, make sure to not rely on it always being present. E.g. if you need access to the user's locale in a [Route Handler](https://v4.next-intl.dev/docs/environments/actions-metadata-route-handlers#route-handlers), a reliable option is to provide the locale as a search param (e.g. `/api/posts/12?locale=en`).
+Since the cookie is now only available after a locale switch, make sure to not rely on it always being present. E.g. if you need access to the user's locale in a [Route Handler](/docs/environments/actions-metadata-route-handlers#route-handlers), a reliable option is to provide the locale as a search param (e.g. `/api/posts/12?locale=en`).
 
-As part of this change, disabling a cookie now requires you to set [`localeCookie: false`](https://v4.next-intl.dev/docs/routing#locale-cookie) in your routing configuration. Previously, `localeDetection: false` ambiguously also disabled the cookie from being set, but since a separate `localeCookie` option was introduced recently, this should now be used instead.
+As part of this change, disabling a cookie now requires you to set [`localeCookie: false`](/docs/routing#locale-cookie) in your routing configuration. Previously, `localeDetection: false` ambiguously also disabled the cookie from being set, but since a separate `localeCookie` option was introduced recently, this should now be used instead.
 
-Learn more in the [locale cookie](https://v4.next-intl.dev/docs/routing#locale-cookie) docs.
+Learn more in the [locale cookie](/docs/routing#locale-cookie) docs.
 
 ## Modernized build output
 
@@ -266,7 +266,7 @@ This will create the following structure:
 - `example.no`: `no-NO`
 - `example.no/en`: `en-NO`
 
-Learn more in the updated docs for [`domains`](https://v4.next-intl.dev/docs/routing#domains).
+Learn more in the updated docs for [`domains`](/docs/routing#domains).
 
 ## Preparation for upcoming Next.js features [#nextjs-future]
 
@@ -300,11 +300,9 @@ For a smooth upgrade, please initially upgrade to the latest v3.x version and ch
 Afterwards, you can upgrade by running:
 
 ```
-npm install next-intl@v4-beta
+npm install next-intl@4
 ```
 
-The beta docs are available here: [v4.next-intl.dev](https://v4.next-intl.dev)
-
 I'd love to hear about your experiences with `next-intl@4.0`! Join the conversation in the [discussions](https://github.com/amannn/next-intl/discussions/1631).
 
 ## Thank you!
@@ -315,6 +313,8 @@ A special thank you goes to <PartnerContentLink href="https://crowdin.com/">Crow
 
 —Jan
 
+(this post has been updated from an initial announcement for the 3.0 release candidate)
+
 PS: Have you heard that [learn.next-intl.dev](https://learn.next-intl.dev) is coming?
 
 <StayUpdated />

docs/src/pages/index.mdx

@@ -20,6 +20,10 @@ import GetStartedBackground from '@/components/GetStartedBackground';
   description="Support multiple languages, with your app code becoming simpler instead of more complex."
   getStarted="Get started"
   viewExample="View an example"
+  announcement={{
+    href: '/blog/next-intl-4-0',
+    label: 'next-intl 4.0 is out now!'
+  }}
 />
 <PartnerBanner intro="Presented by" />
 

docs/src/theme.config.tsx

@@ -27,12 +27,21 @@ export default {
     pre: Pre
   },
   banner: {
+    key: 'banner-learn-next-intl',
     content: (
       <div className="text-center">
-        You‘re viewing the next-intl 4 beta docs
+        Announcing{' '}
+        <a
+          className="underline"
+          href="https://learn.next-intl.dev"
+          rel="noreferrer"
+          target="_blank"
+        >
+          learn.next-intl.dev
+        </a>
+        !
       </div>
-    ),
-    dismissible: false
+    )
   },
   footer: {
     component: Footer