@trigger.dev/sdk 4.7.3 → 4.7.4

package/docs/troubleshooting-alerts.mdx

@@ -243,13 +243,17 @@ This webhook is sent when a run fails. The payload is available on the `object`
 </ParamField>
 
 <ParamField path="object.environment.type" type="string">
-  Environment type (STAGING or PRODUCTION)
+  Environment type (`PRODUCTION`, `STAGING`, or `PREVIEW`)
 </ParamField>
 
 <ParamField path="object.environment.slug" type="string">
   Environment slug
 </ParamField>
 
+<ParamField path="object.environment.branchName" type="string">
+  Environment branch name (optional)
+</ParamField>
+
 <ParamField path="object.organization.id" type="string">
   Organization ID
 </ParamField>
@@ -311,7 +315,7 @@ This webhook is sent when a deployment succeeds. The payload is available on the
 </ParamField>
 
 <ParamField path="object.environment.type" type="string">
-  Environment type (STAGING or PRODUCTION)
+  Environment type (`PRODUCTION`, `STAGING`, or `PREVIEW`)
 </ParamField>
 
 <ParamField path="object.environment.slug" type="string">
@@ -346,6 +350,54 @@ This webhook is sent when a deployment succeeds. The payload is available on the
   Project name
 </ParamField>
 
+<ParamField path="object.git" type="object">
+  Git metadata for the deployment (optional). When present, `branch`, `commitSha`, `commitMessage`, `commitUrl` and `branchUrl` are always set.
+</ParamField>
+
+<ParamField path="object.git.branch" type="string">
+  Git branch
+</ParamField>
+
+<ParamField path="object.git.commitSha" type="string">
+  Short commit SHA (first 7 characters)
+</ParamField>
+
+<ParamField path="object.git.commitMessage" type="string">
+  Commit message (empty string if unavailable)
+</ParamField>
+
+<ParamField path="object.git.commitUrl" type="string">
+  URL of the commit
+</ParamField>
+
+<ParamField path="object.git.branchUrl" type="string">
+  URL of the branch
+</ParamField>
+
+<ParamField path="object.git.pullRequestNumber" type="number">
+  Pull request number (optional)
+</ParamField>
+
+<ParamField path="object.git.pullRequestTitle" type="string">
+  Pull request title (optional)
+</ParamField>
+
+<ParamField path="object.git.pullRequestUrl" type="string">
+  Pull request URL (optional)
+</ParamField>
+
+<ParamField path="object.git.provider" type="string">
+  Git provider (optional)
+</ParamField>
+
+<ParamField path="object.vercel" type="object">
+  Vercel metadata for the deployment (optional)
+</ParamField>
+
+<ParamField path="object.vercel.deploymentUrl" type="string">
+  URL of the deployment in the Vercel dashboard
+</ParamField>
+
 ### Deployment Failed Alert
 
 This webhook is sent when a deployment fails. The payload is available on the `object` property:
@@ -391,7 +443,7 @@ This webhook is sent when a deployment fails. The payload is available on the `o
 </ParamField>
 
 <ParamField path="object.environment.type" type="string">
-  Environment type (STAGING or PRODUCTION)
+  Environment type (`PRODUCTION`, `STAGING`, or `PREVIEW`)
 </ParamField>
 
 <ParamField path="object.environment.slug" type="string">
@@ -426,6 +478,53 @@ This webhook is sent when a deployment fails. The payload is available on the `o
   Project name
 </ParamField>
 
+<ParamField path="object.git" type="object">
+  Git metadata for the deployment (optional). When present, `branch`, `commitSha`, `commitMessage`, `commitUrl` and `branchUrl` are always set.
+</ParamField>
+
+<ParamField path="object.git.branch" type="string">
+  Git branch
+</ParamField>
+
+<ParamField path="object.git.commitSha" type="string">
+  Short commit SHA (first 7 characters)
+</ParamField>
+
+<ParamField path="object.git.commitMessage" type="string">
+  Commit message (empty string if unavailable)
+</ParamField>
+
+<ParamField path="object.git.commitUrl" type="string">
+  URL of the commit
+</ParamField>
+
+<ParamField path="object.git.branchUrl" type="string">
+  URL of the branch
+</ParamField>
+
+<ParamField path="object.git.pullRequestNumber" type="number">
+  Pull request number (optional)
+</ParamField>
+
+<ParamField path="object.git.pullRequestTitle" type="string">
+  Pull request title (optional)
+</ParamField>
+
+<ParamField path="object.git.pullRequestUrl" type="string">
+  Pull request URL (optional)
+</ParamField>
+
+<ParamField path="object.git.provider" type="string">
+  Git provider (optional)
+</ParamField>
+
+<ParamField path="object.vercel" type="object">
+  Vercel metadata for the deployment (optional)
+</ParamField>
+
+<ParamField path="object.vercel.deploymentUrl" type="string">
+  URL of the deployment in the Vercel dashboard
+</ParamField>
 
 ### Error Group Alert
 

package/docs/troubleshooting.mdx

@@ -251,7 +251,7 @@ If runs are staying in the `QUEUED` state for extended periods, check your concu
 **Solutions:**
 
 - **Increase concurrency limits** - If you're on a paid plan, increase your environment concurrency limit via the dashboard
-- **Review queue concurrency limits** - Check if individual queues have restrictive `concurrencyLimit` settings
+- **Review concurrency settings** - Check if your tasks have restrictive `concurrency` settings, or your queues a restrictive legacy `concurrencyLimit`. See [Concurrency](/concurrency)
 - **Check for stuck runs** - See if stalled runs are blocking new executions
 
 ### Runs queued because a billing limit was reached

package/docs/upgrading-packages.mdx

@@ -39,12 +39,12 @@ You can deploy using [GitHub Actions](/github-actions). We recommend that you lo
 
 <Steps>
   <Step title="Find your workflow file">
-    In your `.githubs/workflows` folder you can find your workflow yml files. You may have a prod
+    In your `.github/workflows` folder you can find your workflow yml files. You may have a prod
     and staging one.
   </Step>
   <Step title="Update the version for the run command">
     In the steps you'll see a `run` command. It will run the trigger.dev deploy CLI command. Make
-    sure to update this version to the latest version (e.g. `npx trigger.dev@3.0.0 deploy`).
+    sure to update this version to the latest version (e.g. `npx trigger.dev@4.7.3 deploy`).
   </Step>
 </Steps>
 
@@ -57,7 +57,7 @@ For example:
 ```json
 {
   "devDependencies": {
-    "trigger.dev": "3.0.0"
+    "trigger.dev": "4.7.3"
   }
 }
 ```

package/docs/vercel-integration.mdx

@@ -129,7 +129,17 @@ The integration sets this up for you:
 - It passes your commit SHA as the deployment's external id.
 - `VERCEL_GIT_COMMIT_SHA` is available at runtime on Vercel, so the SDK finds the matching id with no work from you.
 
-There is nothing to enable, and it works in production, staging and preview alike. Nothing is gated: your Vercel deployment is never held back.
+There is nothing to enable, and it works in production, staging and preview alike.
+
+### Production waits for your tasks
+
+A production deployment from a push to the branch Trigger.dev builds for production gets a blocking **Trigger.dev Build** check. Vercel holds the deployment until the task build for the same commit finishes, then assigns your production domains as usual. If the task build fails or is canceled, the check fails and the Vercel deployment doesn't go live, so your app never ships against tasks that didn't build.
+
+If no task build for the commit has started within 10 minutes, the check fails too.
+
+To retry after a failed build, re-run the **Trigger.dev deployment** check on the commit in GitHub. Once that build succeeds, redeploy from Vercel or push a new commit.
+
+A production deployment with no task build to wait for is never held: its check is marked skipped. That covers deployments from the Vercel CLI, from a branch that isn't your production branch in Trigger.dev, and from projects without a connected GitHub repository. Preview and staging deployments aren't held either: their check passes straight away, and version skew protection makes their runs wait for the matching task build instead.
 
 <Note>
   Version skew protection requires the `@trigger.dev/sdk` release that introduces external
@@ -146,8 +156,8 @@ To opt out, set `TRIGGER_AUTOMATIC_SKEW_VERSION_PROTECTION` to `0` on your Verce
 <Warning>
   **Automatic atomic deployments are deprecated.** Use [version skew
   protection](/deployment/atomic-deployment) instead — it needs no second Vercel deployment,
-  never gates your app's deploy, doesn't touch `Auto-assign Custom Production Domains`, and covers
-  staging and preview as well as production.
+  doesn't touch `Auto-assign Custom Production Domains`, and covers staging and preview as well as
+  production. Production deployments still wait for your task build through the blocking check.
 
   Nothing is being switched off. The setting stays in your project's Vercel settings, keeps working,
   and remains the way to hold your Vercel deployment back until your tasks have built. New

package/docs/versioning.mdx

@@ -51,7 +51,7 @@ Because your application and your tasks deploy separately, a release of your app
 
 ## Retries and reattempts
 
-When a task has an uncaught error it will [retry](/errors-retrying), assuming you have not set `maxAttempts` to 0. Retries are locked to the original version of the run.
+When a task has an uncaught error it will [retry](/errors-retrying), if the task has retries configured (the `retry` option or `retries.default` in your config). Retries are locked to the original version of the run.
 
 ## Replays
 

package/docs/wait-for-token.mdx

@@ -135,7 +135,7 @@ Create a waitpoint token.
 The `createToken` function accepts an object with the following properties:
 
 <ParamField query="timeout" type="string" optional>
-  The maximum amount of time to wait for the token to be completed. Defaults to "10m".
+  The maximum amount of time to wait for the token to be completed. If omitted, the token has no timeout. Accepts a duration string like `"30s"` or `"4w"`, or a `Date`.
 </ParamField>
 
 <ParamField query="idempotencyKey" type="string" optional>
@@ -144,7 +144,7 @@ The `createToken` function accepts an object with the following properties:
 </ParamField>
 
 <ParamField query="idempotencyKeyTTL" type="string" optional>
-  The time to live for the idempotency key. Defaults to "1h".
+  The time to live for the idempotency key. If omitted, the key does not expire.
 </ParamField>
 
 <ParamField query="tags" type="string[]" optional>
@@ -380,7 +380,7 @@ The `listTokens` function accepts an object with the following properties:
 </ParamField>
 
 <ParamField query="period" type="string" optional>
-  The period to filter by. Can be one of: `1h`, `1d`, `7d`, `30d`.
+  The period to filter by, as a duration string such as `1h`, `1d`, `7d` or `30d`.
 </ParamField>
 
 <ParamField query="from" type="Date | number" optional>

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@trigger.dev/sdk",
-  "version": "4.7.3",
+  "version": "4.7.4",
   "description": "trigger.dev Node.JS SDK",
   "license": "MIT",
   "publishConfig": {
@@ -69,7 +69,7 @@
   "dependencies": {
     "@opentelemetry/api": "1.9.1",
     "@opentelemetry/semantic-conventions": "1.41.1",
-    "@trigger.dev/core": "4.7.3",
+    "@trigger.dev/core": "4.7.4",
     "uncrypto": "^0.1.3"
   },
   "devDependencies": {