Adds corepack bug and workaround

Author: samejr

docs/deployment/overview.mdx

@@ -4,6 +4,8 @@ sidebarTitle: "Overview"
 description: "Learn how to deploy your tasks to Trigger.dev."
 ---
 
+import CorepackError from "/snippets/corepack-error.mdx";
+
 Before you can run production workloads on Trigger.dev, you need to deploy your tasks. The only way to do this at the moment is through the [deploy CLI command](/cli-deploy):
 
 <CodeGroup>
@@ -231,3 +233,4 @@ export default defineConfig({
   },
 });
 ```
+<CorepackError />

docs/snippets/corepack-error.mdx

@@ -0,0 +1,8 @@
+### `Cannot find matching keyid`
+
+This error occurs when using Node.js v22 with corepack, as it's not yet compatible with the latest package manager signatures. To fix this, either:
+
+1. Downgrade to Node.js v20 (LTS), or
+2. Install corepack globally: `npm i -g corepack@latest`
+
+The corepack bug and workaround are detailed in [this issue](https://github.com/npm/cli/issues/8075).

docs/troubleshooting.mdx

@@ -6,6 +6,7 @@ description: "Some common problems you might experience and their solutions"
 import NextjsTroubleshootingMissingApiKey from "/snippets/nextjs-missing-api-key.mdx";
 import NextjsTroubleshootingButtonSyntax from "/snippets/nextjs-button-syntax.mdx";
 import RateLimitHitUseBatchTrigger from "/snippets/rate-limit-hit-use-batchtrigger.mdx";
+import CorepackError from "/snippets/corepack-error.mdx";
 
 ## Development
 
@@ -71,6 +72,9 @@ export default defineConfig({
 
 If you see this error, add pino (and any other associated packages) to your `external` build settings in your `trigger.config.ts` file. Learn more about the `external` setting in the [config docs](/config/config-file#external).
 
+<CorepackError />
+
+
 ## Project setup issues
 
 ### `The requested module 'node:events' does not provide an export named 'addAbortListener'`