diff --git a/.changeset/pre.json b/.changeset/pre.json
index 0a5e6ce609e..97df5f29023 100644
--- a/.changeset/pre.json
+++ b/.changeset/pre.json
@@ -20,5 +20,87 @@
     "@remix-run/server-runtime": "1.19.3",
     "@remix-run/testing": "1.19.3"
   },
-  "changesets": []
+  "changesets": [
+    "add-error-to-meta",
+    "beige-pugs-drive",
+    "brown-seals-look",
+    "cool-penguins-film",
+    "cool-wombats-chew",
+    "create-remix-overwrite",
+    "create-remix",
+    "cuddly-rings-mate",
+    "curly-moons-cover",
+    "decouple-css-bundle-from-dev",
+    "deduplicate-prefetch-link-tags",
+    "destory-session-maxage",
+    "dirty-bags-wink",
+    "disabled-link-preload",
+    "empty-cameras-walk",
+    "enable-css-features-by-default",
+    "error-response-type",
+    "fair-falcons-wink",
+    "fix-commit-session-expires",
+    "fix-stub-route-object-type",
+    "fluffy-bananas-love",
+    "fluffy-fishes-lay",
+    "friendly-fireants-report",
+    "fuzzy-mugs-swim",
+    "giant-crews-care",
+    "global-fetch-instanceof",
+    "grumpy-trees-flow",
+    "handle-error-response",
+    "heavy-crabs-kick",
+    "improve-minified-css-compatibility",
+    "khaki-roses-matter",
+    "kind-grapes-clap",
+    "large-goats-double",
+    "light-rivers-tell",
+    "loud-pandas-do",
+    "lovely-drinks-bow",
+    "memory-session-id",
+    "moody-pants-laugh",
+    "neat-impalas-divide",
+    "olive-lemons-marry",
+    "orange-suits-nail",
+    "polyfill-package-imports-in-deps",
+    "popular-trains-do",
+    "purple-tables-switch",
+    "purple-zoos-refuse",
+    "quiet-lemons-fold",
+    "remix-testing-meta-links",
+    "remove-default-server-node-polyfills",
+    "remove-fetch-polyfill-references-in-adapters",
+    "remove-magic-import-eslint-warnings",
+    "remove-stream-recursion",
+    "remove-unstable-should-reload",
+    "remove-v1-meta",
+    "resource-route-boundary-only",
+    "rich-months-search",
+    "rotten-penguins-eat",
+    "selfish-months-behave",
+    "seven-queens-try",
+    "shiny-teachers-cheer",
+    "silver-readers-think",
+    "sour-parrots-dream",
+    "strong-rice-applaud",
+    "stupid-emus-repair",
+    "tame-moons-buy",
+    "tasty-apricots-doubt",
+    "use-fetch-duplex",
+    "useloaderdata-types-yarn-pnp",
+    "v2-default-to-esm",
+    "v2-remove-auto-globals-install",
+    "v2-remove-catch-boundary",
+    "v2-remove-fetcher-compat",
+    "v2-remove-magic-exports",
+    "v2-remove-normalize-form-method",
+    "v2-remove-unstable-warnings",
+    "v2-remove-use-transition",
+    "v2-route-convention",
+    "v2-serve-dynamic-import",
+    "v2-use-deepest-headers-function",
+    "wicked-points-unite",
+    "wild-garlics-draw",
+    "xdm-to-mdx"
+  ]
 }
diff --git a/packages/create-remix/CHANGELOG.md b/packages/create-remix/CHANGELOG.md
index 556bb5cd7f0..fe05cf4bb0f 100644
--- a/packages/create-remix/CHANGELOG.md
+++ b/packages/create-remix/CHANGELOG.md
@@ -1,5 +1,24 @@
 # `create-remix`
 
+## 2.0.0-pre.0
+
+### Major Changes
+
+- The `create-remix` CLI has been rewritten to feature a cleaner interface, Git repo initialization and optional `remix.init` script execution. The interactive template prompt and official Remix stack/template shorthands have also been removed so that community/third-party templates are now on a more equal footing. ([#6887](https://github.com/remix-run/remix/pull/6887))
+
+  The code for `create-remix` has been moved out of the Remix CLI since it's not intended for use within an existing Remix application. This means that the `remix create` command is no longer available.
+
+- Stop passing `isTypeScript` to `remix.init` script ([#7099](https://github.com/remix-run/remix/pull/7099))
+- Require Node >=18.0.0 ([#6939](https://github.com/remix-run/remix/pull/6939))
+
+### Minor Changes
+
+- Remove empty directory checking in favor of `overwrite` prompt/flag. ([#7062](https://github.com/remix-run/remix/pull/7062))
+
+  `create-remix` now allows you to write into an existing non-empty directory. It will perform a file-level comparison and if the template will overwrite any existing files in the destination directory, it will prompt you if it's OK to overwrite those files. If you answer no (the default) then it will exit without copying any files. You may skip this prompt with the `--overwrite` CLI flag.
+
+- Support bun package manager ([#7074](https://github.com/remix-run/remix/pull/7074))
+
 ## 1.19.3
 
 ### Patch Changes
diff --git a/packages/create-remix/package.json b/packages/create-remix/package.json
index df6fa12ecdc..dd99c725419 100644
--- a/packages/create-remix/package.json
+++ b/packages/create-remix/package.json
@@ -1,6 +1,6 @@
 {
   "name": "create-remix",
-  "version": "1.19.3",
+  "version": "2.0.0-pre.0",
   "description": "Create a new Remix app",
   "homepage": "https://remix.run",
   "bugs": {
diff --git a/packages/remix-architect/CHANGELOG.md b/packages/remix-architect/CHANGELOG.md
index 9a6b212e2d6..b17085e00fd 100644
--- a/packages/remix-architect/CHANGELOG.md
+++ b/packages/remix-architect/CHANGELOG.md
@@ -1,5 +1,37 @@
 # `@remix-run/architect`
 
+## 2.0.0-pre.0
+
+### Major Changes
+
+- Require Node >=18.0.0 ([#6939](https://github.com/remix-run/remix/pull/6939))
+- For preparation of using Node's built in fetch implementation, installing the fetch globals is now a responsibility of the app server. If you are using `remix-serve`, nothing is required. If you are using your own app server, you will need to install the globals yourself. ([#7009](https://github.com/remix-run/remix/pull/7009))
+
+  ```js filename=server.js
+  import { installGlobals } from "@remix-run/node";
+
+  installGlobals();
+  ```
+
+  source-map-support is now a responsibility of the app server. If you are using `remix-serve`, nothing is required. If you are using your own app server, you will need to install [`source-map-support`](https://www.npmjs.com/package/source-map-support) yourself.
+
+  ```sh
+  npm i source-map-support
+  ```
+
+  ```js filename=server.js
+  import sourceMapSupport from "source-map-support";
+  sourceMapSupport.install();
+  ```
+
+### Patch Changes
+
+- - Switch to `headers.entries()` instead of non-spec-compliant `headers.raw()` in `sendRemixResponse` ([#7150](https://github.com/remix-run/remix/pull/7150))
+  - Update to `@remix-run/web-fetch@4.3.7`
+- remove references to fetch polyfills in node and arc adapters ([#7230](https://github.com/remix-run/remix/pull/7230))
+- Updated dependencies:
+  - `@remix-run/node@2.0.0-pre.0`
+
 ## 1.19.3
 
 ### Patch Changes
diff --git a/packages/remix-architect/package.json b/packages/remix-architect/package.json
index 482e6b48c06..887cf68ac70 100644
--- a/packages/remix-architect/package.json
+++ b/packages/remix-architect/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@remix-run/architect",
-  "version": "1.19.3",
+  "version": "2.0.0-pre.0",
   "description": "Architect server request handler for Remix",
   "bugs": {
     "url": "https://github.com/remix-run/remix/issues"
@@ -15,7 +15,7 @@
   "typings": "dist/index.d.ts",
   "dependencies": {
     "@architect/functions": "^5.2.0",
-    "@remix-run/node": "1.19.3",
+    "@remix-run/node": "2.0.0-pre.0",
     "@types/aws-lambda": "^8.10.82"
   },
   "devDependencies": {
diff --git a/packages/remix-cloudflare-pages/CHANGELOG.md b/packages/remix-cloudflare-pages/CHANGELOG.md
index 0cbd68574e4..6dab35bf14f 100644
--- a/packages/remix-cloudflare-pages/CHANGELOG.md
+++ b/packages/remix-cloudflare-pages/CHANGELOG.md
@@ -1,5 +1,17 @@
 # `@remix-run/cloudflare-pages`
 
+## 2.0.0-pre.0
+
+### Major Changes
+
+- Require Node >=18.0.0 ([#6939](https://github.com/remix-run/remix/pull/6939))
+- Drop `@cloudflare/workers-types` v2 & v3 support ([#6925](https://github.com/remix-run/remix/pull/6925))
+
+### Patch Changes
+
+- Updated dependencies:
+  - `@remix-run/cloudflare@2.0.0-pre.0`
+
 ## 1.19.3
 
 ### Patch Changes
diff --git a/packages/remix-cloudflare-pages/package.json b/packages/remix-cloudflare-pages/package.json
index 86c8ee09e28..f4eef063617 100644
--- a/packages/remix-cloudflare-pages/package.json
+++ b/packages/remix-cloudflare-pages/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@remix-run/cloudflare-pages",
-  "version": "1.19.3",
+  "version": "2.0.0-pre.0",
   "description": "Cloudflare Pages request handler for Remix",
   "bugs": {
     "url": "https://github.com/remix-run/remix/issues"
@@ -15,7 +15,7 @@
   "typings": "dist/index.d.ts",
   "module": "dist/esm/index.js",
   "dependencies": {
-    "@remix-run/cloudflare": "1.19.3"
+    "@remix-run/cloudflare": "2.0.0-pre.0"
   },
   "devDependencies": {
     "@cloudflare/workers-types": "^4.20230518.0",
diff --git a/packages/remix-cloudflare-workers/CHANGELOG.md b/packages/remix-cloudflare-workers/CHANGELOG.md
index 977920a0c77..fccdd8ab09a 100644
--- a/packages/remix-cloudflare-workers/CHANGELOG.md
+++ b/packages/remix-cloudflare-workers/CHANGELOG.md
@@ -1,5 +1,17 @@
 # `@remix-run/cloudflare-workers`
 
+## 2.0.0-pre.0
+
+### Major Changes
+
+- Require Node >=18.0.0 ([#6939](https://github.com/remix-run/remix/pull/6939))
+- Drop `@cloudflare/workers-types` v2 & v3 support ([#6925](https://github.com/remix-run/remix/pull/6925))
+
+### Patch Changes
+
+- Updated dependencies:
+  - `@remix-run/cloudflare@2.0.0-pre.0`
+
 ## 1.19.3
 
 ### Patch Changes
diff --git a/packages/remix-cloudflare-workers/package.json b/packages/remix-cloudflare-workers/package.json
index 383b207a5ed..7e70dc6f2a8 100644
--- a/packages/remix-cloudflare-workers/package.json
+++ b/packages/remix-cloudflare-workers/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@remix-run/cloudflare-workers",
-  "version": "1.19.3",
+  "version": "2.0.0-pre.0",
   "description": "Cloudflare worker request handler for Remix",
   "bugs": {
     "url": "https://github.com/remix-run/remix/issues"
@@ -16,7 +16,7 @@
   "module": "dist/esm/index.js",
   "dependencies": {
     "@cloudflare/kv-asset-handler": "^0.1.3",
-    "@remix-run/cloudflare": "1.19.3"
+    "@remix-run/cloudflare": "2.0.0-pre.0"
   },
   "devDependencies": {
     "@cloudflare/workers-types": "^4.20230518.0",
diff --git a/packages/remix-cloudflare/CHANGELOG.md b/packages/remix-cloudflare/CHANGELOG.md
index 95870793d82..50f696a4f74 100644
--- a/packages/remix-cloudflare/CHANGELOG.md
+++ b/packages/remix-cloudflare/CHANGELOG.md
@@ -1,5 +1,72 @@
 # `@remix-run/cloudflare`
 
+## 2.0.0-pre.0
+
+### Major Changes
+
+- Remove `createCloudflareKVSessionStorage` ([#6898](https://github.com/remix-run/remix/pull/6898))
+- Require Node >=18.0.0 ([#6939](https://github.com/remix-run/remix/pull/6939))
+- We have made a few important changes to the route `meta` API as reflected in the v1 implementation when using the `future.v2_meta` config option. ([#6958](https://github.com/remix-run/remix/pull/6958))
+
+  - The `meta` function should no longer return an object, but an array of objects that map to the HTML tag's respective attributes. This provides more flexibility and control over how certain tags are rendered, and the order in which they appear.
+  - In most cases, `meta` descriptor objects render a `<meta>` tag. There are a few notable exceptions:
+    - `{ title: "My app" }` will render `<title>My app</title>`.
+    - `{ 'script:ld+json': { /* ... */ } }` will render `<script type="application/ld+json">/* ... */</script>`, where the value is serialized to JSON and rendered inside the `<script>` tag.
+    - `{ tagName: 'link', ...attributes }` will render `<link {...attributes} />`
+      - This is useful for things like setting canonical URLs. For loading assets, we encourage you to use the `links` export instead.
+      - It's important to note that `tagName` may only accept `meta` or `link`, so other arbitrary elements will be ignored.
+  - `<Meta />` will no longer render the `meta` output from the entire route hierarchy. Only the output from the leaf (current) route will be rendered unless that route does not export a `meta` function, in which case the output from the nearest ancestor route with `meta` will be rendered.
+    - This change comes from user feedback that auto-merging meta made effective SEO difficult to implement. Our goal is to give you as much control as you need over meta tags for each individual route.
+    - Our suggested approach is to **only export a `meta` function from leaf route modules**. However, if you do want to render a tag from another matched route, `meta` now accepts a `matches` argument for you to merge or override parent route meta as you'd like.
+    ```tsx
+    export function meta({ matches }) {
+      return [
+        // render all ancestor route meta except for title tags
+        ...matches
+          .flatMap((match) => match.meta)
+          .filter((match) => !("title" in match)),
+        { title: "Override the title!" },
+      ];
+    }
+    ```
+  - The `parentsData` argument has been removed. If you need to access data from a parent route, you can use `matches` instead.
+    ```tsx
+    // before
+    export function meta({ parentsData }) {
+      return [{ title: parentsData["routes/some-route"].title }];
+    }
+    // after
+    export function meta({ matches }) {
+      return [
+        {
+          title: matches.find((match) => match.id === "routes/some-route").data
+            .title,
+        },
+      ];
+    }
+    ```
+
+- Drop `@cloudflare/workers-types` v2 & v3 support ([#6925](https://github.com/remix-run/remix/pull/6925))
+- Removed support for "magic exports" from the `remix` package. This package can be removed from your `package.json` and you should update all imports to use the source `@remix-run/*` packages: ([#6895](https://github.com/remix-run/remix/pull/6895))
+
+  ```diff
+  - import type { ActionArgs } from "remix";
+  - import { json, useLoaderData } from "remix";
+  + import type { ActionArgs } from "@remix-run/node";
+  + import { json } from "@remix-run/node";
+  + import { useLoaderData } from "@remix-run/react";
+  ```
+
+### Minor Changes
+
+- Re-export new `redirectDocument` method from React Router ([#7040](https://github.com/remix-run/remix/pull/7040), [#6842](https://github.com/remix-run/remix/pull/6842)) ([#7040](https://github.com/remix-run/remix/pull/7040))
+
+### Patch Changes
+
+- Export proper `ErrorResponse` type for usage alongside `isRouteErrorResponse` ([#7244](https://github.com/remix-run/remix/pull/7244))
+- Updated dependencies:
+  - `@remix-run/server-runtime@2.0.0-pre.0`
+
 ## 1.19.3
 
 ### Patch Changes
diff --git a/packages/remix-cloudflare/package.json b/packages/remix-cloudflare/package.json
index bccaea2c942..ce835985cf9 100644
--- a/packages/remix-cloudflare/package.json
+++ b/packages/remix-cloudflare/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@remix-run/cloudflare",
-  "version": "1.19.3",
+  "version": "2.0.0-pre.0",
   "description": "Cloudflare platform abstractions for Remix",
   "bugs": {
     "url": "https://github.com/remix-run/remix/issues"
@@ -15,7 +15,7 @@
   "typings": "dist/index.d.ts",
   "dependencies": {
     "@cloudflare/kv-asset-handler": "^0.1.3",
-    "@remix-run/server-runtime": "1.19.3"
+    "@remix-run/server-runtime": "2.0.0-pre.0"
   },
   "devDependencies": {
     "@cloudflare/workers-types": "^4.20230518.0",
diff --git a/packages/remix-css-bundle/CHANGELOG.md b/packages/remix-css-bundle/CHANGELOG.md
index 1856362a5c4..97c6f200fe9 100644
--- a/packages/remix-css-bundle/CHANGELOG.md
+++ b/packages/remix-css-bundle/CHANGELOG.md
@@ -1,5 +1,17 @@
 # @remix-run/css-bundle
 
+## 2.0.0-pre.0
+
+### Major Changes
+
+- Require Node >=18.0.0 ([#6939](https://github.com/remix-run/remix/pull/6939))
+
+### Patch Changes
+
+- Decouple the `@remix-run/dev` package from the contents of the `@remix-run/css-bundle` package. ([#6982](https://github.com/remix-run/remix/pull/6982))
+
+  The contents of the `@remix-run/css-bundle` package are now entirely managed by the Remix compiler. Even though it's still recommended that your Remix dependencies all share the same version, this change ensures that there are no runtime errors when upgrading `@remix-run/dev` without upgrading `@remix-run/css-bundle`.
+
 ## 1.19.3
 
 No significant changes to this package were made in this release. [See the releases page on GitHub](https://github.com/remix-run/remix/releases/tag/remix%401.19.3) for an overview of all changes in v1.19.3.
diff --git a/packages/remix-css-bundle/package.json b/packages/remix-css-bundle/package.json
index aab3cc13d97..1377a144995 100644
--- a/packages/remix-css-bundle/package.json
+++ b/packages/remix-css-bundle/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@remix-run/css-bundle",
-  "version": "1.19.3",
+  "version": "2.0.0-pre.0",
   "description": "CSS bundle href when using CSS bundling features in Remix",
   "homepage": "https://remix.run",
   "bugs": {
diff --git a/packages/remix-deno/CHANGELOG.md b/packages/remix-deno/CHANGELOG.md
index 4f5aa088b15..4042c8a5945 100644
--- a/packages/remix-deno/CHANGELOG.md
+++ b/packages/remix-deno/CHANGELOG.md
@@ -1,5 +1,60 @@
 # `@remix-run/deno`
 
+## 2.0.0-pre.0
+
+### Major Changes
+
+- Require Node >=18.0.0 ([#6939](https://github.com/remix-run/remix/pull/6939))
+- We have made a few important changes to the route `meta` API as reflected in the v1 implementation when using the `future.v2_meta` config option. ([#6958](https://github.com/remix-run/remix/pull/6958))
+
+  - The `meta` function should no longer return an object, but an array of objects that map to the HTML tag's respective attributes. This provides more flexibility and control over how certain tags are rendered, and the order in which they appear.
+  - In most cases, `meta` descriptor objects render a `<meta>` tag. There are a few notable exceptions:
+    - `{ title: "My app" }` will render `<title>My app</title>`.
+    - `{ 'script:ld+json': { /* ... */ } }` will render `<script type="application/ld+json">/* ... */</script>`, where the value is serialized to JSON and rendered inside the `<script>` tag.
+    - `{ tagName: 'link', ...attributes }` will render `<link {...attributes} />`
+      - This is useful for things like setting canonical URLs. For loading assets, we encourage you to use the `links` export instead.
+      - It's important to note that `tagName` may only accept `meta` or `link`, so other arbitrary elements will be ignored.
+  - `<Meta />` will no longer render the `meta` output from the entire route hierarchy. Only the output from the leaf (current) route will be rendered unless that route does not export a `meta` function, in which case the output from the nearest ancestor route with `meta` will be rendered.
+    - This change comes from user feedback that auto-merging meta made effective SEO difficult to implement. Our goal is to give you as much control as you need over meta tags for each individual route.
+    - Our suggested approach is to **only export a `meta` function from leaf route modules**. However, if you do want to render a tag from another matched route, `meta` now accepts a `matches` argument for you to merge or override parent route meta as you'd like.
+    ```tsx
+    export function meta({ matches }) {
+      return [
+        // render all ancestor route meta except for title tags
+        ...matches
+          .flatMap((match) => match.meta)
+          .filter((match) => !("title" in match)),
+        { title: "Override the title!" },
+      ];
+    }
+    ```
+  - The `parentsData` argument has been removed. If you need to access data from a parent route, you can use `matches` instead.
+    ```tsx
+    // before
+    export function meta({ parentsData }) {
+      return [{ title: parentsData["routes/some-route"].title }];
+    }
+    // after
+    export function meta({ matches }) {
+      return [
+        {
+          title: matches.find((match) => match.id === "routes/some-route").data
+            .title,
+        },
+      ];
+    }
+    ```
+
+### Minor Changes
+
+- Re-export new `redirectDocument` method from React Router ([#7040](https://github.com/remix-run/remix/pull/7040), [#6842](https://github.com/remix-run/remix/pull/6842)) ([#7040](https://github.com/remix-run/remix/pull/7040))
+
+### Patch Changes
+
+- Export proper `ErrorResponse` type for usage alongside `isRouteErrorResponse` ([#7244](https://github.com/remix-run/remix/pull/7244))
+- Updated dependencies:
+  - `@remix-run/server-runtime@2.0.0-pre.0`
+
 ## 1.19.3
 
 ### Patch Changes
diff --git a/packages/remix-deno/package.json b/packages/remix-deno/package.json
index 22a79c07b27..05ebc287a3c 100644
--- a/packages/remix-deno/package.json
+++ b/packages/remix-deno/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@remix-run/deno",
-  "version": "1.19.3",
+  "version": "2.0.0-pre.0",
   "description": "Deno platform abstractions for Remix",
   "homepage": "https://remix.run",
   "main": "./index.ts",
@@ -15,7 +15,7 @@
   "license": "MIT",
   "sideEffects": false,
   "dependencies": {
-    "@remix-run/server-runtime": "1.19.3",
+    "@remix-run/server-runtime": "2.0.0-pre.0",
     "mime": "^3.0.0"
   },
   "peerDependencies": {
diff --git a/packages/remix-dev/CHANGELOG.md b/packages/remix-dev/CHANGELOG.md
index 069a899f874..e7382323e09 100644
--- a/packages/remix-dev/CHANGELOG.md
+++ b/packages/remix-dev/CHANGELOG.md
@@ -1,5 +1,166 @@
 # `@remix-run/dev`
 
+## 2.0.0-pre.0
+
+### Major Changes
+
+- Remove `serverBuildTarget` config option ([#6896](https://github.com/remix-run/remix/pull/6896))
+- The `create-remix` CLI has been rewritten to feature a cleaner interface, Git repo initialization and optional `remix.init` script execution. The interactive template prompt and official Remix stack/template shorthands have also been removed so that community/third-party templates are now on a more equal footing. ([#6887](https://github.com/remix-run/remix/pull/6887))
+
+  The code for `create-remix` has been moved out of the Remix CLI since it's not intended for use within an existing Remix application. This means that the `remix create` command is no longer available.
+
+- Remove deprecated REMIX_DEV_HTTP_ORIGIN env var. ([#6963](https://github.com/remix-run/remix/pull/6963))
+
+  Use REMIX_DEV_ORIGIN instead.
+
+- Enable built-in PostCSS and Tailwind support by default. ([#6909](https://github.com/remix-run/remix/pull/6909))
+
+  These tools are now automatically used within the Remix compiler if PostCSS and/or Tailwind configuration files are present in your project.
+
+  If you have a custom PostCSS and/or Tailwind setup outside of Remix, you can disable these features in your `remix.config.js`.
+
+  ```js
+  module.exports = {
+    postcss: false,
+    tailwind: false,
+  };
+  ```
+
+- Remove `devServerBroadcastDelay` config option ([#7063](https://github.com/remix-run/remix/pull/7063))
+- Stop passing `isTypeScript` to `remix.init` script ([#7099](https://github.com/remix-run/remix/pull/7099))
+- remove deprecated `devServerPort` option ([#7078](https://github.com/remix-run/remix/pull/7078))
+
+  use `--port` / `config.dev.port` option instead
+
+- remove deprecated REMIX_DEV_SERVER_WS_PORT env var ([#6965](https://github.com/remix-run/remix/pull/6965))
+
+  use `remix dev`'s '`--port`/`port` option instead
+
+- Remove `replace-remix-magic-imports` codemod ([#6899](https://github.com/remix-run/remix/pull/6899))
+- Drop React 17 support ([#7121](https://github.com/remix-run/remix/pull/7121))
+- Require Node >=18.0.0 ([#6939](https://github.com/remix-run/remix/pull/6939))
+- Remove default Node.js polyfills from the server build when targeting non-Node.js platforms. ([#6911](https://github.com/remix-run/remix/pull/6911))
+
+  Any Node.js polyfills that are required for your server code to run on non-Node.js platforms must be manually specified in `remix.config.js` using the `serverNodeBuiltinsPolyfill` option.
+
+  ```js
+  exports.serverNodeBuiltinsPolyfill = {
+    modules: {
+      path: true, // Provide a JSPM polyfill
+      fs: "empty", // Provide an empty polyfill
+    },
+  };
+  ```
+
+- We have made a few important changes to the route `meta` API as reflected in the v1 implementation when using the `future.v2_meta` config option. ([#6958](https://github.com/remix-run/remix/pull/6958))
+
+  - The `meta` function should no longer return an object, but an array of objects that map to the HTML tag's respective attributes. This provides more flexibility and control over how certain tags are rendered, and the order in which they appear.
+  - In most cases, `meta` descriptor objects render a `<meta>` tag. There are a few notable exceptions:
+    - `{ title: "My app" }` will render `<title>My app</title>`.
+    - `{ 'script:ld+json': { /* ... */ } }` will render `<script type="application/ld+json">/* ... */</script>`, where the value is serialized to JSON and rendered inside the `<script>` tag.
+    - `{ tagName: 'link', ...attributes }` will render `<link {...attributes} />`
+      - This is useful for things like setting canonical URLs. For loading assets, we encourage you to use the `links` export instead.
+      - It's important to note that `tagName` may only accept `meta` or `link`, so other arbitrary elements will be ignored.
+  - `<Meta />` will no longer render the `meta` output from the entire route hierarchy. Only the output from the leaf (current) route will be rendered unless that route does not export a `meta` function, in which case the output from the nearest ancestor route with `meta` will be rendered.
+    - This change comes from user feedback that auto-merging meta made effective SEO difficult to implement. Our goal is to give you as much control as you need over meta tags for each individual route.
+    - Our suggested approach is to **only export a `meta` function from leaf route modules**. However, if you do want to render a tag from another matched route, `meta` now accepts a `matches` argument for you to merge or override parent route meta as you'd like.
+    ```tsx
+    export function meta({ matches }) {
+      return [
+        // render all ancestor route meta except for title tags
+        ...matches
+          .flatMap((match) => match.meta)
+          .filter((match) => !("title" in match)),
+        { title: "Override the title!" },
+      ];
+    }
+    ```
+  - The `parentsData` argument has been removed. If you need to access data from a parent route, you can use `matches` instead.
+    ```tsx
+    // before
+    export function meta({ parentsData }) {
+      return [{ title: parentsData["routes/some-route"].title }];
+    }
+    // after
+    export function meta({ matches }) {
+      return [
+        {
+          title: matches.find((match) => match.id === "routes/some-route").data
+            .title,
+        },
+      ];
+    }
+    ```
+
+- remove deprecated cli args and flags ([#6962](https://github.com/remix-run/remix/pull/6962))
+
+  - `--no-restart`/`restart` 👉 use `--manual`/`manual` instead
+  - `--scheme`/`scheme` and `--host`/`host` 👉 use `REMIX_DEV_ORIGIN` instead
+
+- promote config.future.v2_dev to config.dev ([#7002](https://github.com/remix-run/remix/pull/7002))
+- Remove `browserBuildDirectory` config option ([#6900](https://github.com/remix-run/remix/pull/6900))
+- remove codemod command ([#6918](https://github.com/remix-run/remix/pull/6918))
+- Remove `serverBuildDirectory` config option ([#6897](https://github.com/remix-run/remix/pull/6897))
+- Default to serverModuleFormat esm, and update remix-serve to use dynamic import to support esm and cjs build outputs. ([#6949](https://github.com/remix-run/remix/pull/6949))
+- Remove `v2_errorBoundary` flag and `CatchBoundary` implementation ([#6906](https://github.com/remix-run/remix/pull/6906))
+- Removed support for "magic exports" from the `remix` package. This package can be removed from your `package.json` and you should update all imports to use the source `@remix-run/*` packages: ([#6895](https://github.com/remix-run/remix/pull/6895))
+
+  ```diff
+  - import type { ActionArgs } from "remix";
+  - import { json, useLoaderData } from "remix";
+  + import type { ActionArgs } from "@remix-run/node";
+  + import { json } from "@remix-run/node";
+  + import { useLoaderData } from "@remix-run/react";
+  ```
+
+- Remove `v2_normalizeFormMethod` future flag - all `formMethod` values will be normalized in v2 ([#6875](https://github.com/remix-run/remix/pull/6875))
+- Remove `v2_routeConvention` flag. The flat route file convention is now standard. ([#6969](https://github.com/remix-run/remix/pull/6969))
+- Remove `v2_headers` flag. It is now the default behavior to use the deepest `headers` function in the route tree. ([#6979](https://github.com/remix-run/remix/pull/6979))
+
+### Minor Changes
+
+- Warn users about obsolete future flags in remix.config.js ([#7048](https://github.com/remix-run/remix/pull/7048))
+- detect built mode via `build.mode` ([#6964](https://github.com/remix-run/remix/pull/6964))
+
+  Prevents mode mismatch between built Remix server entry and user-land server.
+  Additionally, all runtimes (including non-Node runtimes) can use `build.mode` to determine if HMR should be performed.
+
+- Support bun package manager ([#7074](https://github.com/remix-run/remix/pull/7074))
+
+### Patch Changes
+
+- Fix importing of PNGs, SVGs, and other assets from packages in `node_modules` ([#6813](https://github.com/remix-run/remix/pull/6813)) ([#7182](https://github.com/remix-run/remix/pull/7182))
+- Decouple the `@remix-run/dev` package from the contents of the `@remix-run/css-bundle` package. ([#6982](https://github.com/remix-run/remix/pull/6982))
+
+  The contents of the `@remix-run/css-bundle` package are now entirely managed by the Remix compiler. Even though it's still recommended that your Remix dependencies all share the same version, this change ensures that there are no runtime errors when upgrading `@remix-run/dev` without upgrading `@remix-run/css-bundle`.
+
+- allow non-development modes for remix watch ([#7117](https://github.com/remix-run/remix/pull/7117))
+- stop remix dev when esbuild is not running ([#7158](https://github.com/remix-run/remix/pull/7158))
+- Improve browser compatibility of minified CSS ([#7187](https://github.com/remix-run/remix/pull/7187))
+
+  We now minify CSS targeting the Remix browser support baseline (i.e. anything that supports [ES module scripts](https://caniuse.com/es6-module)), whereas previously CSS was minified using esbuild's default "esnext" target. This meant that CSS in the production build could be using properties that are unsupported in some browsers. This change also means you now have more control over CSS transformations using the built-in PostCSS support since they won't be reversed by esbuild's minification.
+
+- allow decorators in app code ([#7176](https://github.com/remix-run/remix/pull/7176))
+- allow jsx in js files during hmr ([#7112](https://github.com/remix-run/remix/pull/7112))
+- Support dependencies that import polyfill packages for Node built-ins via a trailing slash (e.g. importing the `buffer` package with `var Buffer = require('buffer/').Buffer` as recommended in their readme). These imports were previously marked as external. This meant that they were left as dynamic imports in the client bundle and would throw a runtime error in the browser (e.g. `Dynamic require of "buffer/" is not supported`). ([#7198](https://github.com/remix-run/remix/pull/7198))
+- Remove outdated ESM import warnings ([#6916](https://github.com/remix-run/remix/pull/6916))
+
+  Most of the time these warnings were false positives.
+  Instead, we now rely on built-in Node warnings for ESM imports.
+
+- do not trigger rebuilds when .DS_Store changes ([#7172](https://github.com/remix-run/remix/pull/7172))
+- Remove warnings for stabilized flags: ([#6905](https://github.com/remix-run/remix/pull/6905))
+
+  - `unstable_cssSideEffectImports`
+  - `unstable_cssModules`
+  - `unstable_vanillaExtract`
+
+- allow any mode (NODE_ENV) ([#7113](https://github.com/remix-run/remix/pull/7113))
+- Replace the deprecated [`xdm`](https://github.com/wooorm/xdm) package with [`@mdx-js/mdx`](https://github.com/mdx-js/mdx) ([#4054](https://github.com/remix-run/remix/pull/4054))
+- Updated dependencies:
+  - `@remix-run/serve@2.0.0-pre.0`
+  - `@remix-run/server-runtime@2.0.0-pre.0`
+
 ## 1.19.3
 
 ### Patch Changes
diff --git a/packages/remix-dev/package.json b/packages/remix-dev/package.json
index 129f287466b..88c1790c4dc 100644
--- a/packages/remix-dev/package.json
+++ b/packages/remix-dev/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@remix-run/dev",
-  "version": "1.19.3",
+  "version": "2.0.0-pre.0",
   "description": "Dev tools and CLI for Remix",
   "homepage": "https://remix.run",
   "bugs": {
@@ -27,7 +27,7 @@
     "@babel/traverse": "^7.21.5",
     "@mdx-js/mdx": "^2.3.0",
     "@npmcli/package-json": "^4.0.1",
-    "@remix-run/server-runtime": "1.19.3",
+    "@remix-run/server-runtime": "2.0.0-pre.0",
     "@types/mdx": "^2.0.5",
     "@vanilla-extract/integration": "^6.2.0",
     "arg": "^5.0.1",
@@ -69,7 +69,7 @@
     "ws": "^7.4.5"
   },
   "devDependencies": {
-    "@remix-run/serve": "1.19.3",
+    "@remix-run/serve": "2.0.0-pre.0",
     "@types/cacache": "^17.0.0",
     "@types/gunzip-maybe": "^1.4.0",
     "@types/jsesc": "^3.0.1",
@@ -88,7 +88,7 @@
     "tiny-invariant": "^1.2.0"
   },
   "peerDependencies": {
-    "@remix-run/serve": "^1.19.3",
+    "@remix-run/serve": "^2.0.0-pre.0",
     "typescript": "^5.1.0"
   },
   "peerDependenciesMeta": {
diff --git a/packages/remix-eslint-config/CHANGELOG.md b/packages/remix-eslint-config/CHANGELOG.md
index 19ef708d01f..57a742f670f 100644
--- a/packages/remix-eslint-config/CHANGELOG.md
+++ b/packages/remix-eslint-config/CHANGELOG.md
@@ -1,5 +1,14 @@
 # `@remix-run/eslint-config`
 
+## 2.0.0-pre.0
+
+### Major Changes
+
+- Remove `@remix-run/eslint-config/jest` ESLint config ([#6903](https://github.com/remix-run/remix/pull/6903))
+- Drop React 17 support ([#7121](https://github.com/remix-run/remix/pull/7121))
+- Remove magic imports ESLint warnings ([#6902](https://github.com/remix-run/remix/pull/6902))
+- Remove `v2_normalizeFormMethod` future flag - all `formMethod` values will be normalized in v2 ([#6875](https://github.com/remix-run/remix/pull/6875))
+
 ## 1.19.3
 
 No significant changes to this package were made in this release. [See the releases page on GitHub](https://github.com/remix-run/remix/releases/tag/remix%401.19.3) for an overview of all changes in v1.19.3.
diff --git a/packages/remix-eslint-config/package.json b/packages/remix-eslint-config/package.json
index c8ba3302ac3..3d1160a5ea6 100644
--- a/packages/remix-eslint-config/package.json
+++ b/packages/remix-eslint-config/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@remix-run/eslint-config",
-  "version": "1.19.3",
+  "version": "2.0.0-pre.0",
   "description": "ESLint configuration for Remix projects",
   "bugs": {
     "url": "https://github.com/remix-run/remix/issues"
diff --git a/packages/remix-express/CHANGELOG.md b/packages/remix-express/CHANGELOG.md
index ba9d9da5c45..f137358c363 100644
--- a/packages/remix-express/CHANGELOG.md
+++ b/packages/remix-express/CHANGELOG.md
@@ -1,5 +1,37 @@
 # `@remix-run/express`
 
+## 2.0.0-pre.0
+
+### Major Changes
+
+- Require Node >=18.0.0 ([#6939](https://github.com/remix-run/remix/pull/6939))
+- For preparation of using Node's built in fetch implementation, installing the fetch globals is now a responsibility of the app server. If you are using `remix-serve`, nothing is required. If you are using your own app server, you will need to install the globals yourself. ([#7009](https://github.com/remix-run/remix/pull/7009))
+
+  ```js filename=server.js
+  import { installGlobals } from "@remix-run/node";
+
+  installGlobals();
+  ```
+
+  source-map-support is now a responsibility of the app server. If you are using `remix-serve`, nothing is required. If you are using your own app server, you will need to install [`source-map-support`](https://www.npmjs.com/package/source-map-support) yourself.
+
+  ```sh
+  npm i source-map-support
+  ```
+
+  ```js filename=server.js
+  import sourceMapSupport from "source-map-support";
+  sourceMapSupport.install();
+  ```
+
+### Patch Changes
+
+- - Switch to `headers.entries()` instead of non-spec-compliant `headers.raw()` in `sendRemixResponse` ([#7150](https://github.com/remix-run/remix/pull/7150))
+  - Update to `@remix-run/web-fetch@4.3.7`
+- remove references to fetch polyfills in node and arc adapters ([#7230](https://github.com/remix-run/remix/pull/7230))
+- Updated dependencies:
+  - `@remix-run/node@2.0.0-pre.0`
+
 ## 1.19.3
 
 ### Patch Changes
diff --git a/packages/remix-express/package.json b/packages/remix-express/package.json
index e64eef2b982..a10f9c4311d 100644
--- a/packages/remix-express/package.json
+++ b/packages/remix-express/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@remix-run/express",
-  "version": "1.19.3",
+  "version": "2.0.0-pre.0",
   "description": "Express server request handler for Remix",
   "bugs": {
     "url": "https://github.com/remix-run/remix/issues"
@@ -14,7 +14,7 @@
   "main": "dist/index.js",
   "typings": "dist/index.d.ts",
   "dependencies": {
-    "@remix-run/node": "1.19.3"
+    "@remix-run/node": "2.0.0-pre.0"
   },
   "devDependencies": {
     "@types/express": "^4.17.9",
diff --git a/packages/remix-node/CHANGELOG.md b/packages/remix-node/CHANGELOG.md
index 9ab196a7761..35af048e498 100644
--- a/packages/remix-node/CHANGELOG.md
+++ b/packages/remix-node/CHANGELOG.md
@@ -1,5 +1,91 @@
 # `@remix-run/node`
 
+## 2.0.0-pre.0
+
+### Major Changes
+
+- Require Node >=18.0.0 ([#6939](https://github.com/remix-run/remix/pull/6939))
+- We have made a few important changes to the route `meta` API as reflected in the v1 implementation when using the `future.v2_meta` config option. ([#6958](https://github.com/remix-run/remix/pull/6958))
+
+  - The `meta` function should no longer return an object, but an array of objects that map to the HTML tag's respective attributes. This provides more flexibility and control over how certain tags are rendered, and the order in which they appear.
+  - In most cases, `meta` descriptor objects render a `<meta>` tag. There are a few notable exceptions:
+    - `{ title: "My app" }` will render `<title>My app</title>`.
+    - `{ 'script:ld+json': { /* ... */ } }` will render `<script type="application/ld+json">/* ... */</script>`, where the value is serialized to JSON and rendered inside the `<script>` tag.
+    - `{ tagName: 'link', ...attributes }` will render `<link {...attributes} />`
+      - This is useful for things like setting canonical URLs. For loading assets, we encourage you to use the `links` export instead.
+      - It's important to note that `tagName` may only accept `meta` or `link`, so other arbitrary elements will be ignored.
+  - `<Meta />` will no longer render the `meta` output from the entire route hierarchy. Only the output from the leaf (current) route will be rendered unless that route does not export a `meta` function, in which case the output from the nearest ancestor route with `meta` will be rendered.
+    - This change comes from user feedback that auto-merging meta made effective SEO difficult to implement. Our goal is to give you as much control as you need over meta tags for each individual route.
+    - Our suggested approach is to **only export a `meta` function from leaf route modules**. However, if you do want to render a tag from another matched route, `meta` now accepts a `matches` argument for you to merge or override parent route meta as you'd like.
+    ```tsx
+    export function meta({ matches }) {
+      return [
+        // render all ancestor route meta except for title tags
+        ...matches
+          .flatMap((match) => match.meta)
+          .filter((match) => !("title" in match)),
+        { title: "Override the title!" },
+      ];
+    }
+    ```
+  - The `parentsData` argument has been removed. If you need to access data from a parent route, you can use `matches` instead.
+    ```tsx
+    // before
+    export function meta({ parentsData }) {
+      return [{ title: parentsData["routes/some-route"].title }];
+    }
+    // after
+    export function meta({ matches }) {
+      return [
+        {
+          title: matches.find((match) => match.id === "routes/some-route").data
+            .title,
+        },
+      ];
+    }
+    ```
+
+- For preparation of using Node's built in fetch implementation, installing the fetch globals is now a responsibility of the app server. If you are using `remix-serve`, nothing is required. If you are using your own app server, you will need to install the globals yourself. ([#7009](https://github.com/remix-run/remix/pull/7009))
+
+  ```js filename=server.js
+  import { installGlobals } from "@remix-run/node";
+
+  installGlobals();
+  ```
+
+  source-map-support is now a responsibility of the app server. If you are using `remix-serve`, nothing is required. If you are using your own app server, you will need to install [`source-map-support`](https://www.npmjs.com/package/source-map-support) yourself.
+
+  ```sh
+  npm i source-map-support
+  ```
+
+  ```js filename=server.js
+  import sourceMapSupport from "source-map-support";
+  sourceMapSupport.install();
+  ```
+
+- Removed support for "magic exports" from the `remix` package. This package can be removed from your `package.json` and you should update all imports to use the source `@remix-run/*` packages: ([#6895](https://github.com/remix-run/remix/pull/6895))
+
+  ```diff
+  - import type { ActionArgs } from "remix";
+  - import { json, useLoaderData } from "remix";
+  + import type { ActionArgs } from "@remix-run/node";
+  + import { json } from "@remix-run/node";
+  + import { useLoaderData } from "@remix-run/react";
+  ```
+
+### Minor Changes
+
+- Re-export new `redirectDocument` method from React Router ([#7040](https://github.com/remix-run/remix/pull/7040), [#6842](https://github.com/remix-run/remix/pull/6842)) ([#7040](https://github.com/remix-run/remix/pull/7040))
+
+### Patch Changes
+
+- Export proper `ErrorResponse` type for usage alongside `isRouteErrorResponse` ([#7244](https://github.com/remix-run/remix/pull/7244))
+- ensures fetch() return is instanceof global Response by removing extended classes for NodeRequest and NodeResponse in favor of custom interface type cast. ([#7109](https://github.com/remix-run/remix/pull/7109))
+- remove recursion from stream utilities ([#7245](https://github.com/remix-run/remix/pull/7245))
+- Updated dependencies:
+  - `@remix-run/server-runtime@2.0.0-pre.0`
+
 ## 1.19.3
 
 ### Patch Changes
diff --git a/packages/remix-node/package.json b/packages/remix-node/package.json
index def114e1083..839fe10f577 100644
--- a/packages/remix-node/package.json
+++ b/packages/remix-node/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@remix-run/node",
-  "version": "1.19.3",
+  "version": "2.0.0-pre.0",
   "description": "Node.js platform abstractions for Remix",
   "bugs": {
     "url": "https://github.com/remix-run/remix/issues"
@@ -17,7 +17,7 @@
     "./install.js"
   ],
   "dependencies": {
-    "@remix-run/server-runtime": "1.19.3",
+    "@remix-run/server-runtime": "2.0.0-pre.0",
     "@remix-run/web-fetch": "^4.3.7",
     "@remix-run/web-file": "^3.0.3",
     "@remix-run/web-stream": "^1.0.4",
diff --git a/packages/remix-react/CHANGELOG.md b/packages/remix-react/CHANGELOG.md
index 3117a35c84c..796d02eca1c 100644
--- a/packages/remix-react/CHANGELOG.md
+++ b/packages/remix-react/CHANGELOG.md
@@ -1,5 +1,111 @@
 # `@remix-run/react`
 
+## 2.0.0-pre.0
+
+### Major Changes
+
+- Remove `imagesizes` & `imagesrcset` properties from `HtmlLinkDescriptor`, `LinkDescriptor` & `PrefetchPageDescriptor` types ([#6936](https://github.com/remix-run/remix/pull/6936))
+- remove deprecated REMIX_DEV_SERVER_WS_PORT env var ([#6965](https://github.com/remix-run/remix/pull/6965))
+
+  use `remix dev`'s '`--port`/`port` option instead
+
+- Drop React 17 support ([#7121](https://github.com/remix-run/remix/pull/7121))
+- Require Node >=18.0.0 ([#6939](https://github.com/remix-run/remix/pull/6939))
+- Remove `unstable_shouldReload`, which has been replaced by `shouldRevalidate` ([#6865](https://github.com/remix-run/remix/pull/6865))
+- We have made a few important changes to the route `meta` API as reflected in the v1 implementation when using the `future.v2_meta` config option. ([#6958](https://github.com/remix-run/remix/pull/6958))
+
+  - The `meta` function should no longer return an object, but an array of objects that map to the HTML tag's respective attributes. This provides more flexibility and control over how certain tags are rendered, and the order in which they appear.
+  - In most cases, `meta` descriptor objects render a `<meta>` tag. There are a few notable exceptions:
+    - `{ title: "My app" }` will render `<title>My app</title>`.
+    - `{ 'script:ld+json': { /* ... */ } }` will render `<script type="application/ld+json">/* ... */</script>`, where the value is serialized to JSON and rendered inside the `<script>` tag.
+    - `{ tagName: 'link', ...attributes }` will render `<link {...attributes} />`
+      - This is useful for things like setting canonical URLs. For loading assets, we encourage you to use the `links` export instead.
+      - It's important to note that `tagName` may only accept `meta` or `link`, so other arbitrary elements will be ignored.
+  - `<Meta />` will no longer render the `meta` output from the entire route hierarchy. Only the output from the leaf (current) route will be rendered unless that route does not export a `meta` function, in which case the output from the nearest ancestor route with `meta` will be rendered.
+    - This change comes from user feedback that auto-merging meta made effective SEO difficult to implement. Our goal is to give you as much control as you need over meta tags for each individual route.
+    - Our suggested approach is to **only export a `meta` function from leaf route modules**. However, if you do want to render a tag from another matched route, `meta` now accepts a `matches` argument for you to merge or override parent route meta as you'd like.
+    ```tsx
+    export function meta({ matches }) {
+      return [
+        // render all ancestor route meta except for title tags
+        ...matches
+          .flatMap((match) => match.meta)
+          .filter((match) => !("title" in match)),
+        { title: "Override the title!" },
+      ];
+    }
+    ```
+  - The `parentsData` argument has been removed. If you need to access data from a parent route, you can use `matches` instead.
+    ```tsx
+    // before
+    export function meta({ parentsData }) {
+      return [{ title: parentsData["routes/some-route"].title }];
+    }
+    // after
+    export function meta({ matches }) {
+      return [
+        {
+          title: matches.find((match) => match.id === "routes/some-route").data
+            .title,
+        },
+      ];
+    }
+    ```
+
+- promote config.future.v2_dev to config.dev ([#7002](https://github.com/remix-run/remix/pull/7002))
+- Remove `v2_errorBoundary` flag and `CatchBoundary` implementation ([#6906](https://github.com/remix-run/remix/pull/6906))
+- Remove back-compat layer for `useFetcher`/`useFetchers`. This includes a few small breaking changes: ([#6874](https://github.com/remix-run/remix/pull/6874))
+
+  - `fetcher.type` has been removed since it can be derived from other available information
+  - "Submission" fields have been flattened from `fetcher.submission` down onto the root `fetcher` object, and prefixed with `form` in some cases (`fetcher.submission.action` => `fetcher.formAction`)
+  - `<fetcher.Form method="get">` is now more accurately categorized as `state:"loading"` instead of `state:"submitting"` to better align with the underlying GET request
+
+- Removed support for "magic exports" from the `remix` package. This package can be removed from your `package.json` and you should update all imports to use the source `@remix-run/*` packages: ([#6895](https://github.com/remix-run/remix/pull/6895))
+
+  ```diff
+  - import type { ActionArgs } from "remix";
+  - import { json, useLoaderData } from "remix";
+  + import type { ActionArgs } from "@remix-run/node";
+  + import { json } from "@remix-run/node";
+  + import { useLoaderData } from "@remix-run/react";
+  ```
+
+- Remove `v2_normalizeFormMethod` future flag - all `formMethod` values will be normalized in v2 ([#6875](https://github.com/remix-run/remix/pull/6875))
+- Remove deprecated `useTransition` hook in favor of `useNavigation`. `useNavigation` is _almost_ identical with a few exceptions:\_ ([#6870](https://github.com/remix-run/remix/pull/6870))
+
+  - `useTransition.type` has been removed since it can be derived from other available information
+  - "Submission" fields have been flattened from `useTransition().submission` down onto the root `useNavigation()` object
+  - `<Form method="get">` is now more accurately categorized as `state:"loading"` instead of `state:"submitting"` to better align with the underlying GET navigation
+
+- Remove `v2_routeConvention` flag. The flat route file convention is now standard. ([#6969](https://github.com/remix-run/remix/pull/6969))
+- Remove `v2_headers` flag. It is now the default behavior to use the deepest `headers` function in the route tree. ([#6979](https://github.com/remix-run/remix/pull/6979))
+
+### Minor Changes
+
+- [REMOVE] Update to experimental react router version with Remix back compat code removed ([#7040](https://github.com/remix-run/remix/pull/7040))
+- Export the `Navigation` type returned from `useNavigation` ([#7136](https://github.com/remix-run/remix/pull/7136))
+- Update Remix to use React Router `route.lazy` for module loading ([#7133](https://github.com/remix-run/remix/pull/7133))
+
+### Patch Changes
+
+- Add error to meta params so you can render error titles, etc. ([#7105](https://github.com/remix-run/remix/pull/7105))
+
+  ```tsx
+  export function meta({ error }) {
+    return [{ title: error.message }];
+  }
+  ```
+
+- Deduplicate prefetch link tags ([#7060](https://github.com/remix-run/remix/pull/7060))
+- Skip preloading of stylesheets on client-side route transitions if the browser does not support `<link rel=preload>`. This prevents us from hanging on client-side navigations when we try to preload stylesheets and never receive a `load`/`error` event on the `link` tag. ([#7106](https://github.com/remix-run/remix/pull/7106))
+- Export proper `ErrorResponse` type for usage alongside `isRouteErrorResponse` ([#7244](https://github.com/remix-run/remix/pull/7244))
+- Use the hostname from `REMIX_DEV_ORIGIN` to connect to the live reload socket ([#6923](https://github.com/remix-run/remix/pull/6923))
+- Bump router to 1.9.0/6.16.0 prereleases ([#7283](https://github.com/remix-run/remix/pull/7283))
+- Use unique key for `script:ld+json` meta descriptors ([#6954](https://github.com/remix-run/remix/pull/6954))
+- Fix types for `useLoaderData` when using Yarn PnP ([#7137](https://github.com/remix-run/remix/pull/7137))
+- Updated dependencies:
+  - `@remix-run/server-runtime@2.0.0-pre.0`
+
 ## 1.19.3
 
 No significant changes to this package were made in this release. [See the releases page on GitHub](https://github.com/remix-run/remix/releases/tag/remix%401.19.3) for an overview of all changes in v1.19.3.
diff --git a/packages/remix-react/package.json b/packages/remix-react/package.json
index d529afbaaf9..3ef5ad5d5e4 100644
--- a/packages/remix-react/package.json
+++ b/packages/remix-react/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@remix-run/react",
-  "version": "1.19.3",
+  "version": "2.0.0-pre.0",
   "description": "React DOM bindings for Remix",
   "bugs": {
     "url": "https://github.com/remix-run/remix/issues"
@@ -17,7 +17,7 @@
   "module": "dist/esm/index.js",
   "dependencies": {
     "@remix-run/router": "1.9.0-pre.0",
-    "@remix-run/server-runtime": "1.19.3",
+    "@remix-run/server-runtime": "2.0.0-pre.0",
     "react-router-dom": "6.16.0-pre.0"
   },
   "devDependencies": {
diff --git a/packages/remix-serve/CHANGELOG.md b/packages/remix-serve/CHANGELOG.md
index 46d7dd2d9c1..5f85c6e0a75 100644
--- a/packages/remix-serve/CHANGELOG.md
+++ b/packages/remix-serve/CHANGELOG.md
@@ -1,5 +1,49 @@
 # `@remix-run/serve`
 
+## 2.0.0-pre.0
+
+### Major Changes
+
+- `remix-serve` picks an open port if 3000 is taken ([#7278](https://github.com/remix-run/remix/pull/7278))
+
+  - If `PORT` env var is set, `remix-serve` will use that port
+  - Otherwise, `remix-serve` picks an open port (3000 unless that is already taken)
+
+- integrate manual mode in remix-serve ([#7231](https://github.com/remix-run/remix/pull/7231))
+- Remove undocumented `createApp` Node API ([#7229](https://github.com/remix-run/remix/pull/7229))
+
+  `remix-serve` should a CLI, not a library
+
+- Require Node >=18.0.0 ([#6939](https://github.com/remix-run/remix/pull/6939))
+- promote config.future.v2_dev to config.dev ([#7002](https://github.com/remix-run/remix/pull/7002))
+- Default to serverModuleFormat esm, and update remix-serve to use dynamic import to support esm and cjs build outputs. ([#6949](https://github.com/remix-run/remix/pull/6949))
+- For preparation of using Node's built in fetch implementation, installing the fetch globals is now a responsibility of the app server. If you are using `remix-serve`, nothing is required. If you are using your own app server, you will need to install the globals yourself. ([#7009](https://github.com/remix-run/remix/pull/7009))
+
+  ```js filename=server.js
+  import { installGlobals } from "@remix-run/node";
+
+  installGlobals();
+  ```
+
+  source-map-support is now a responsibility of the app server. If you are using `remix-serve`, nothing is required. If you are using your own app server, you will need to install [`source-map-support`](https://www.npmjs.com/package/source-map-support) yourself.
+
+  ```sh
+  npm i source-map-support
+  ```
+
+  ```js filename=server.js
+  import sourceMapSupport from "source-map-support";
+  sourceMapSupport.install();
+  ```
+
+- Preserve dynamic imports in remix-serve for external bundle ([#7173](https://github.com/remix-run/remix/pull/7173))
+
+### Patch Changes
+
+- Updated dependencies:
+  - `@remix-run/node@2.0.0-pre.0`
+  - `@remix-run/express@2.0.0-pre.0`
+
 ## 1.19.3
 
 ### Patch Changes
diff --git a/packages/remix-serve/package.json b/packages/remix-serve/package.json
index 6af8dfca8ff..8c26cbad1d1 100644
--- a/packages/remix-serve/package.json
+++ b/packages/remix-serve/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@remix-run/serve",
-  "version": "1.19.3",
+  "version": "2.0.0-pre.0",
   "description": "Production application server for Remix",
   "bugs": {
     "url": "https://github.com/remix-run/remix/issues"
@@ -15,8 +15,8 @@
     "remix-serve": "dist/cli.js"
   },
   "dependencies": {
-    "@remix-run/express": "1.19.3",
-    "@remix-run/node": "1.19.3",
+    "@remix-run/express": "2.0.0-pre.0",
+    "@remix-run/node": "2.0.0-pre.0",
     "chokidar": "^3.5.3",
     "compression": "^1.7.4",
     "express": "^4.17.1",
diff --git a/packages/remix-server-runtime/CHANGELOG.md b/packages/remix-server-runtime/CHANGELOG.md
index d0448b17496..7399cc85736 100644
--- a/packages/remix-server-runtime/CHANGELOG.md
+++ b/packages/remix-server-runtime/CHANGELOG.md
@@ -1,5 +1,94 @@
 # `@remix-run/server-runtime`
 
+## 2.0.0-pre.0
+
+### Major Changes
+
+- Remove deprecated REMIX_DEV_HTTP_ORIGIN env var. ([#6963](https://github.com/remix-run/remix/pull/6963))
+
+  Use REMIX_DEV_ORIGIN instead.
+
+- Remove `imagesizes` & `imagesrcset` properties from `HtmlLinkDescriptor`, `LinkDescriptor` & `PrefetchPageDescriptor` types ([#6936](https://github.com/remix-run/remix/pull/6936))
+- Require Node >=18.0.0 ([#6939](https://github.com/remix-run/remix/pull/6939))
+- We have made a few important changes to the route `meta` API as reflected in the v1 implementation when using the `future.v2_meta` config option. ([#6958](https://github.com/remix-run/remix/pull/6958))
+
+  - The `meta` function should no longer return an object, but an array of objects that map to the HTML tag's respective attributes. This provides more flexibility and control over how certain tags are rendered, and the order in which they appear.
+  - In most cases, `meta` descriptor objects render a `<meta>` tag. There are a few notable exceptions:
+    - `{ title: "My app" }` will render `<title>My app</title>`.
+    - `{ 'script:ld+json': { /* ... */ } }` will render `<script type="application/ld+json">/* ... */</script>`, where the value is serialized to JSON and rendered inside the `<script>` tag.
+    - `{ tagName: 'link', ...attributes }` will render `<link {...attributes} />`
+      - This is useful for things like setting canonical URLs. For loading assets, we encourage you to use the `links` export instead.
+      - It's important to note that `tagName` may only accept `meta` or `link`, so other arbitrary elements will be ignored.
+  - `<Meta />` will no longer render the `meta` output from the entire route hierarchy. Only the output from the leaf (current) route will be rendered unless that route does not export a `meta` function, in which case the output from the nearest ancestor route with `meta` will be rendered.
+    - This change comes from user feedback that auto-merging meta made effective SEO difficult to implement. Our goal is to give you as much control as you need over meta tags for each individual route.
+    - Our suggested approach is to **only export a `meta` function from leaf route modules**. However, if you do want to render a tag from another matched route, `meta` now accepts a `matches` argument for you to merge or override parent route meta as you'd like.
+    ```tsx
+    export function meta({ matches }) {
+      return [
+        // render all ancestor route meta except for title tags
+        ...matches
+          .flatMap((match) => match.meta)
+          .filter((match) => !("title" in match)),
+        { title: "Override the title!" },
+      ];
+    }
+    ```
+  - The `parentsData` argument has been removed. If you need to access data from a parent route, you can use `matches` instead.
+    ```tsx
+    // before
+    export function meta({ parentsData }) {
+      return [{ title: parentsData["routes/some-route"].title }];
+    }
+    // after
+    export function meta({ matches }) {
+      return [
+        {
+          title: matches.find((match) => match.id === "routes/some-route").data
+            .title,
+        },
+      ];
+    }
+    ```
+
+- promote config.future.v2_dev to config.dev ([#7002](https://github.com/remix-run/remix/pull/7002))
+- Remove `v2_errorBoundary` flag and `CatchBoundary` implementation ([#6906](https://github.com/remix-run/remix/pull/6906))
+- Removed support for "magic exports" from the `remix` package. This package can be removed from your `package.json` and you should update all imports to use the source `@remix-run/*` packages: ([#6895](https://github.com/remix-run/remix/pull/6895))
+
+  ```diff
+  - import type { ActionArgs } from "remix";
+  - import { json, useLoaderData } from "remix";
+  + import type { ActionArgs } from "@remix-run/node";
+  + import { json } from "@remix-run/node";
+  + import { useLoaderData } from "@remix-run/react";
+  ```
+
+- Remove `v2_normalizeFormMethod` future flag - all `formMethod` values will be normalized in v2 ([#6875](https://github.com/remix-run/remix/pull/6875))
+- Remove `v2_routeConvention` flag. The flat route file convention is now standard. ([#6969](https://github.com/remix-run/remix/pull/6969))
+- Remove `v2_headers` flag. It is now the default behavior to use the deepest `headers` function in the route tree. ([#6979](https://github.com/remix-run/remix/pull/6979))
+
+### Minor Changes
+
+- detect built mode via `build.mode` ([#6964](https://github.com/remix-run/remix/pull/6964))
+
+  Prevents mode mismatch between built Remix server entry and user-land server.
+  Additionally, all runtimes (including non-Node runtimes) can use `build.mode` to determine if HMR should be performed.
+
+- [REMOVE] Update to experimental react router version with Remix back compat code removed ([#7040](https://github.com/remix-run/remix/pull/7040))
+- Update Remix to use React Router `route.lazy` for module loading ([#7133](https://github.com/remix-run/remix/pull/7133))
+- Re-export new `redirectDocument` method from React Router ([#7040](https://github.com/remix-run/remix/pull/7040), [#6842](https://github.com/remix-run/remix/pull/6842)) ([#7040](https://github.com/remix-run/remix/pull/7040))
+
+### Patch Changes
+
+- Fix `destroySession` for sessions using a `maxAge` cookie. The data in the cookie was always properly destroyed but when using `maxAge`, the cookie itself wasn't deleted because `Max-Age` takes precedence over `Expires` in the cookie spec. ([#7252](https://github.com/remix-run/remix/pull/7252))
+- Export proper `ErrorResponse` type for usage alongside `isRouteErrorResponse` ([#7244](https://github.com/remix-run/remix/pull/7244))
+- Ensure `maxAge`/`expires` options passed to `commitSession` take precedence over the original `cookie.expires` value ([#6598](https://github.com/remix-run/remix/pull/6598)) ([#7269](https://github.com/remix-run/remix/pull/7269))
+- Fix `handleError` method to correctly receive `ErrorResponse` instances on `?_data` and resource route requests. It now receives the `ErrorResponse` instance the same way a document request would. Users can leverage `isRouteErrorResponse`to detect these error instances and log accordingly. ([#7211](https://github.com/remix-run/remix/pull/7211))
+- Bump router to 1.9.0/6.16.0 prereleases ([#7283](https://github.com/remix-run/remix/pull/7283))
+- Update `createMemorySessionStorage` to use an internal hash value instead of an integer for the session `id` ([#7227](https://github.com/remix-run/remix/pull/7227))
+- Fix false-positive resource route classification on document requests for routes that only export an `ErrorBoundary` ([#7155](https://github.com/remix-run/remix/pull/7155))
+- correctly infer deferred types for top-level promises ([#7104](https://github.com/remix-run/remix/pull/7104))
+- construct request with duplex option ([#7234](https://github.com/remix-run/remix/pull/7234))
+
 ## 1.19.3
 
 No significant changes to this package were made in this release. [See the releases page on GitHub](https://github.com/remix-run/remix/releases/tag/remix%401.19.3) for an overview of all changes in v1.19.3.
diff --git a/packages/remix-server-runtime/package.json b/packages/remix-server-runtime/package.json
index 7e35babfd04..8080f0000da 100644
--- a/packages/remix-server-runtime/package.json
+++ b/packages/remix-server-runtime/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@remix-run/server-runtime",
-  "version": "1.19.3",
+  "version": "2.0.0-pre.0",
   "description": "Server runtime for Remix",
   "bugs": {
     "url": "https://github.com/remix-run/remix/issues"
diff --git a/packages/remix-testing/CHANGELOG.md b/packages/remix-testing/CHANGELOG.md
index 42f39821833..8fc5838b8a1 100644
--- a/packages/remix-testing/CHANGELOG.md
+++ b/packages/remix-testing/CHANGELOG.md
@@ -1,5 +1,81 @@
 # `@remix-run/testing`
 
+## 2.0.0-pre.0
+
+### Major Changes
+
+- Drop React 17 support ([#7121](https://github.com/remix-run/remix/pull/7121))
+- Require Node >=18.0.0 ([#6939](https://github.com/remix-run/remix/pull/6939))
+- We have made a few important changes to the route `meta` API as reflected in the v1 implementation when using the `future.v2_meta` config option. ([#6958](https://github.com/remix-run/remix/pull/6958))
+
+  - The `meta` function should no longer return an object, but an array of objects that map to the HTML tag's respective attributes. This provides more flexibility and control over how certain tags are rendered, and the order in which they appear.
+  - In most cases, `meta` descriptor objects render a `<meta>` tag. There are a few notable exceptions:
+    - `{ title: "My app" }` will render `<title>My app</title>`.
+    - `{ 'script:ld+json': { /* ... */ } }` will render `<script type="application/ld+json">/* ... */</script>`, where the value is serialized to JSON and rendered inside the `<script>` tag.
+    - `{ tagName: 'link', ...attributes }` will render `<link {...attributes} />`
+      - This is useful for things like setting canonical URLs. For loading assets, we encourage you to use the `links` export instead.
+      - It's important to note that `tagName` may only accept `meta` or `link`, so other arbitrary elements will be ignored.
+  - `<Meta />` will no longer render the `meta` output from the entire route hierarchy. Only the output from the leaf (current) route will be rendered unless that route does not export a `meta` function, in which case the output from the nearest ancestor route with `meta` will be rendered.
+    - This change comes from user feedback that auto-merging meta made effective SEO difficult to implement. Our goal is to give you as much control as you need over meta tags for each individual route.
+    - Our suggested approach is to **only export a `meta` function from leaf route modules**. However, if you do want to render a tag from another matched route, `meta` now accepts a `matches` argument for you to merge or override parent route meta as you'd like.
+    ```tsx
+    export function meta({ matches }) {
+      return [
+        // render all ancestor route meta except for title tags
+        ...matches
+          .flatMap((match) => match.meta)
+          .filter((match) => !("title" in match)),
+        { title: "Override the title!" },
+      ];
+    }
+    ```
+  - The `parentsData` argument has been removed. If you need to access data from a parent route, you can use `matches` instead.
+    ```tsx
+    // before
+    export function meta({ parentsData }) {
+      return [{ title: parentsData["routes/some-route"].title }];
+    }
+    // after
+    export function meta({ matches }) {
+      return [
+        {
+          title: matches.find((match) => match.id === "routes/some-route").data
+            .title,
+        },
+      ];
+    }
+    ```
+
+- promote config.future.v2_dev to config.dev ([#7002](https://github.com/remix-run/remix/pull/7002))
+- Remove `v2_errorBoundary` flag and `CatchBoundary` implementation ([#6906](https://github.com/remix-run/remix/pull/6906))
+- Removed support for "magic exports" from the `remix` package. This package can be removed from your `package.json` and you should update all imports to use the source `@remix-run/*` packages: ([#6895](https://github.com/remix-run/remix/pull/6895))
+
+  ```diff
+  - import type { ActionArgs } from "remix";
+  - import { json, useLoaderData } from "remix";
+  + import type { ActionArgs } from "@remix-run/node";
+  + import { json } from "@remix-run/node";
+  + import { useLoaderData } from "@remix-run/react";
+  ```
+
+- Remove `v2_normalizeFormMethod` future flag - all `formMethod` values will be normalized in v2 ([#6875](https://github.com/remix-run/remix/pull/6875))
+- Remove `v2_routeConvention` flag. The flat route file convention is now standard. ([#6969](https://github.com/remix-run/remix/pull/6969))
+- Remove `v2_headers` flag. It is now the default behavior to use the deepest `headers` function in the route tree. ([#6979](https://github.com/remix-run/remix/pull/6979))
+
+### Minor Changes
+
+- - `unstable_createRemixStub` now supports adding `meta`/`links` functions on stubbed Remix routes ([#7186](https://github.com/remix-run/remix/pull/7186))
+  - ⚠️ `unstable_createRemixStub` no longer supports the `element`/`errorElement` properties on routes. You must use `Component`/`ErrorBoundary` to match what you would export from a Remix route module.
+- Update Remix to use React Router `route.lazy` for module loading ([#7133](https://github.com/remix-run/remix/pull/7133))
+
+### Patch Changes
+
+- Fix types for `StubRouteObject` `children` property ([#7098](https://github.com/remix-run/remix/pull/7098))
+- Bump router to 1.9.0/6.16.0 prereleases ([#7283](https://github.com/remix-run/remix/pull/7283))
+- Updated dependencies:
+  - `@remix-run/react@2.0.0-pre.0`
+  - `@remix-run/node@2.0.0-pre.0`
+
 ## 1.19.3
 
 ### Patch Changes
diff --git a/packages/remix-testing/package.json b/packages/remix-testing/package.json
index 78545580012..74722c19dd7 100644
--- a/packages/remix-testing/package.json
+++ b/packages/remix-testing/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@remix-run/testing",
-  "version": "1.19.3",
+  "version": "2.0.0-pre.0",
   "description": "Testing utilities for Remix apps",
   "homepage": "https://remix.run",
   "bugs": {
@@ -16,8 +16,8 @@
   "typings": "./dist/index.d.ts",
   "module": "./dist/esm/index.js",
   "dependencies": {
-    "@remix-run/node": "1.19.3",
-    "@remix-run/react": "1.19.3",
+    "@remix-run/node": "2.0.0-pre.0",
+    "@remix-run/react": "2.0.0-pre.0",
     "@remix-run/router": "1.9.0-pre.0",
     "react-router-dom": "6.16.0-pre.0"
   },
diff --git a/packages/remix/package.json b/packages/remix/package.json
index 6aff5208ec6..e62bc0ab74b 100644
--- a/packages/remix/package.json
+++ b/packages/remix/package.json
@@ -1,6 +1,6 @@
 {
   "name": "remix",
-  "version": "1.19.3",
+  "version": "2.0.0-pre.0",
   "description": "A framework for building better websites",
   "homepage": "https://remix.run",
   "bugs": {