Merge branch 'canary' into mischnic/pack-3139-got-external-test

Author: mischnic

.github/.react-version

@@ -1 +1 @@
-19.0.0-rc-6230622a1a-20240610
+19.0.0-rc-76002254-20240724

.github/actions/next-integration-stat/package.json

@@ -23,5 +23,5 @@
   "engines": {
     "node": ">=18.18.0"
   },
-  "packageManager": "pnpm@9.5.0"
+  "packageManager": "pnpm@9.6.0"
 }

.github/actions/next-stats-action/package.json

@@ -20,5 +20,5 @@
   "engines": {
     "node": ">=18.18.0"
   },
-  "packageManager": "pnpm@9.5.0"
+  "packageManager": "pnpm@9.6.0"
 }

.github/actions/upload-turboyet-data/package.json

@@ -14,5 +14,5 @@
   "engines": {
     "node": ">=18.18.0"
   },
-  "packageManager": "pnpm@9.5.0"
+  "packageManager": "pnpm@9.6.0"
 }

.github/workflows/build_and_deploy.yml

@@ -9,7 +9,7 @@ on:
 
 env:
   NAPI_CLI_VERSION: 2.16.2
-  TURBO_VERSION: 2.0.7
+  TURBO_VERSION: 2.0.9
   NODE_LTS_VERSION: 20
   CARGO_PROFILE_RELEASE_LTO: 'true'
   TURBO_TEAM: 'vercel'

.github/workflows/build_and_test.yml

@@ -8,7 +8,7 @@ on:
 
 env:
   NAPI_CLI_VERSION: 2.14.7
-  TURBO_VERSION: 2.0.7
+  TURBO_VERSION: 2.0.9
   NODE_MAINTENANCE_VERSION: 18
   NODE_LTS_VERSION: 20
   TEST_CONCURRENCY: 8

.github/workflows/code_freeze.yml

@@ -17,7 +17,7 @@ name: Code Freeze
 
 env:
   NAPI_CLI_VERSION: 2.14.7
-  TURBO_VERSION: 2.0.7
+  TURBO_VERSION: 2.0.9
   NODE_LTS_VERSION: 20
 
 jobs:

.github/workflows/pull_request_stats.yml

@@ -6,7 +6,7 @@ name: Generate Pull Request Stats
 
 env:
   NAPI_CLI_VERSION: 2.14.7
-  TURBO_VERSION: 2.0.7
+  TURBO_VERSION: 2.0.9
   NODE_LTS_VERSION: 20
   TEST_CONCURRENCY: 6
 

.github/workflows/trigger_release.yml

@@ -35,7 +35,7 @@ name: Trigger Release
 
 env:
   NAPI_CLI_VERSION: 2.14.7
-  TURBO_VERSION: 2.0.7
+  TURBO_VERSION: 2.0.9
   NODE_LTS_VERSION: 20
 
 jobs:

docs/02-app/01-building-your-application/01-routing/05-error-handling.mdx

@@ -211,6 +211,8 @@ export default function Error({ error, reset }) {
 }
 ```
 
+If you want errors to bubble up to the parent error boundary, you can `throw` when rendering the `error` component.
+
 ### Handling Errors in Nested Routes
 
 Errors will bubble up to the nearest parent error boundary. This allows for granular error handling by placing `error.tsx` files at different levels in the [route hierarchy](/docs/app/building-your-application/routing#component-hierarchy).