Skip to content

chore: release v4.8.6 - #5109

Open
github-actions[bot] wants to merge 1 commit into
mainfrom
changeset-release/main
Open

github-actions[bot] wants to merge 1 commit into
mainfrom
changeset-release/main

Conversation

@github-actions

@github-actions github-actions Bot commented Nov 10, 2026 •

Copy link
Copy Markdown
Contributor

Summary

11 new features, 17 improvements, 17 bug fixes.

Highlights

  • Allow an explicit audience when signing and verifying JWTs and user-actor tokens. (01337977e)

Improvements

  • Deploys on the bun-1.4 runtime now compile the run worker and your task files into a Bun executable with bytecode, so runs start faster. import.meta.url and __dirname still point at your files under /app, so files you read next to your code must be in the image as before (e.g. with additionalFiles). Set build.bunBytecode: false in trigger.config.ts to turn compilation off. (8130e5e73)
  • trigger dev and trigger deploy no longer crash with spawn ... ENOENT on bun runtimes when Bun isn't installed at ~/.bun. The CLI now falls back to bun on your PATH (Homebrew, mise and similar installs), and if Bun still can't be started, trigger dev reports a readable error and trigger deploy skips local skill discovery with a warning and carries on. (15797c9f2)
  • Bundled task files now keep their project layout (for example /app/src/trigger/tasks.mjs) when the CLI runs from outside the project, such as npx trigger.dev deploy. Before, they could land under a path containing the project's location, away from the files additionalFiles copies next to them, so reads relative to import.meta.url failed. (0c03b59b9)
  • Show CLI command errors in the same error format as other CLI errors, and keep them visible with --log-level error. (c515c3f74)
  • Deploys now report a warmup command that loads your config and task files offline without running any task, so the platform can prepare faster run starts for your deployment. (5479177af)
  • Generate the machine ID and the managed run controller ID on first use instead of at import, so importing these modules draws no randomness and a process restored from a warm start does not reuse IDs drawn before it was saved. (a8ac49cd3)
  • Deploys on the node-24 and node-26 runtimes now build a Node compile cache for your bundled code during the image build, so runs spend less time compiling your tasks and their dependencies before they start. node-22 deploys are unchanged. (cb1e7362f)
  • Report a run whose process the kernel killed for running out of memory as TASK_PROCESS_OOM_KILLED, rather than as a generic exit after SIGKILL, when the out-of-memory kill is counted in the run's cgroup. (7a2a7dc80)
  • Deployed task processes now receive secret environment variables only with the run, instead of also in the environment the process starts with. (489a6dff3)
  • Deployed task processes now start with the environment variables that Node, OpenSSL, libuv or the dynamic loader read only at startup (such as LD_PRELOAD, OPENSSL_CONF, NODE_ICU_DATA, TZ and UV_*), and the run's logs warn, by name only, about other startup-only variables (such as NODE_OPTIONS, MALLOC_* or GLIBC_TUNABLES) that arrive too late to take effect. (60d1774df)
  • webhooks.notion() endpoints accept Notion's verification request. While the endpoint has no signing secret, the verification_token Notion sends is stored as its signing secret, so you can paste it back into Notion and later deliveries verify with it. Redeploy with this version for existing Notion endpoints to pick it up. (4288ea912)
  • Support scoped run tokens without an environment key, including offloaded task inputs and stream waits. Explain why a run has no usable credential for an operation. (ed0147895)
  • concurrencyKey now also takes an object, so one run can be limited by two limits keyed by different things, like a cap per session and a cap per organization. default is the run's own key and every other entry gives a named limit its own key: concurrencyKey: { default: sessionId, [orgLimit.name]: orgId }. A string key works as before. (4961fc474)

Bug fixes

  • Fix child_process.fork() and spawn(process.execPath, ...) in compiled bun-1.4 deploys. They started the run worker again instead of Bun, so the child never ran and the task hung. process.execPath now points at the image's bun binary, as it does in uncompiled deploys. (d63b49ef3)
  • Fix webhook verification for webhooks.brex(), which now reads the webhook-id, webhook-timestamp and webhook-signature headers Brex sends instead of svix-* headers, and for webhooks.composio(), which now keys the signature with the secret's raw text as Composio does instead of base64-decoding it. PagerDuty, Sentry, Vercel, Zendesk, Attio, DocuSign and Intercom endpoints now default to pasting the provider-issued signing secret, and Linear and Calendly offer both generating and pasting one. Redeploy with this version for existing endpoints to pick up the change. (b5b311407)

Server changes

These changes affect the self-hosted Docker image and Trigger.dev Cloud:

  • Ask the Dashboard Agent to watch something, such as a deploy, a task or a model, and it proposes alerts you confirm one by one. When the alerts belong together, it offers to create them as one grouped alert in a single click.
  • Select up to 100 environment variable values on the Environment variables page and delete them together. The confirmation lists every value and its environment, and asks you to type a word before anything is removed.
  • Compare the environment variables of two environments on the Environment variables page and see only the keys that differ, with secrets shown as the same or different but never revealed. Copy values from one environment to the other, one key or up to 100 at a time.
  • Click a key on the environment variables page to see its value in every environment and preview branch in a side panel, with edit and delete in place. A list showing a single environment can also be sorted by last updated. The edit dialog now starts in the value field, and archived preview branches are no longer accepted as targets.
  • Environment variables page: a new Needs attention page lists the keys in one environment that are empty, missing compared with your other environments, changed in the last day, or replaceable with OIDC, with copy, delete and ignore actions. The OIDC page is now a grid of providers with setup in a side panel, it points at environment variables OIDC could replace, and there are setup guides for Azure, Google Cloud, HashiCorp Vault, Doppler, Snowflake and Databricks.
  • Add opt-in per-environment encryption keys for runtime and build environment variables, with rotation and migration support.
  • Add "Ignored branches" to the Git settings: pull requests from branches matching these patterns no longer get a preview deployment. Patterns are globs matched against the whole branch name, like dependabot/**.
  • The OIDC page lists Hugging Face and OpenRouter, and the environment variables page suggests OIDC for their API keys. Each has a setup guide in the docs.
  • Organization owners can now require multi-factor authentication for every member, and ask for a fresh MFA check before members view environment variables, create personal access tokens or change the organization's security settings. Find both under Organization settings → Security.
  • Add a hosted MCP server so AI clients can work with your projects and runs. It is opt-in per deployment.
  • The allowed IP addresses field on API keys now turns each address or CIDR range into its own pill as you type, checks it right away with the same rules used on save, and lets you remove entries one at a time. A "Test an IP" button checks whether an address would be allowed by the current list before you save.
  • Environment variables page: after adding a variable, the list switches to the environment you saved it in and opens the page that holds the new key, with a toast naming where it went. The env filter in the URL also accepts development, staging and production. The compare view has a copy button on each key, and each row's edit and delete buttons are named after the key and environment for screen readers.
  • Personal access tokens created on the dashboard can now expire on a custom date, picked from a calendar alongside the preset lifetimes. A token expires at the end of the chosen day (UTC), up to the longest offered lifetime.
  • Runs start faster when the platform is busy.
  • The alert group page now shows its header and member list right away, and member charts fill in as they load.
  • The alert wizard now highlights the suggested option on choice steps instead of the first row.
  • The alerts list now shows its rows before the activity sparklines load, and the sparklines load faster.
  • Alerts created from the Dashboard Agent are now limited to 200 active alerts per project, with bounded names, scopes and notification channels.
  • The dashboard agent now asks you to confirm before resolving an alert.
  • The Dashboard Agent can now look up runs, deployments and queries in non-development environments for members whose role can see them but can't view API keys.
  • Help links (?aiHelp=, /ai-help) now prefill the chat composer instead of sending.
  • Fix dashboard pages that open as a dialog (such as adding environment variables or a new alert) re-rendering the whole page when loaded directly or reloaded.
  • Saving an environment variable that someone else deletes at the same moment now shows a clear message asking you to try again instead of a database error, and the API answers with a 409. Deleting a value can no longer remove a value that was being added to the same variable at that moment.
  • Runs that exhaust their dequeue attempts while the run or its environment can't be read now fail with TASK_RUN_DEQUEUED_MAX_RETRIES instead of staying queued forever.
  • Fix waitpoint callback URLs returning authentication errors when created inside preview branch runs, including previously issued URLs.
  • An organization's only Owner can no longer leave or be removed while other members remain, so the organization always keeps someone who can manage members, billing and roles.
  • Revoking or expiring a personal access token now also ends the environment JWTs exchanged from it and the run, batch and session tokens minted with them.
  • Runs triggered in the seconds after a deploy no longer get stuck waiting for a version until the next deploy.
  • A task that returns while its run is resuming from a wait it did not await (for example a wait raced against a timeout or an abort signal) can now fail right away with an error that says so. Before, the run stayed in an executing state until its heartbeat timed out, and could then be reported as out of memory. This is off by default: set RUN_ENGINE_STALE_COMPLETION_MODE=enforce on the webapp to switch it on.
Raw changeset output

Releases

@trigger.dev/build@4.8.6

Patch Changes

  • Updated dependencies:
    • @trigger.dev/core@4.8.6

trigger.dev@4.8.6

Patch Changes

  • Deploys on the bun-1.4 runtime now compile the run worker and your task files into a Bun executable with bytecode, so runs start faster. import.meta.url and __dirname still point at your files under /app, so files you read next to your code must be in the image as before (e.g. with additionalFiles). Set build.bunBytecode: false in trigger.config.ts to turn compilation off. (8130e5e73)
  • Fix child_process.fork() and spawn(process.execPath, ...) in compiled bun-1.4 deploys. They started the run worker again instead of Bun, so the child never ran and the task hung. process.execPath now points at the image's bun binary, as it does in uncompiled deploys. (d63b49ef3)
  • trigger dev and trigger deploy no longer crash with spawn ... ENOENT on bun runtimes when Bun isn't installed at ~/.bun. The CLI now falls back to bun on your PATH (Homebrew, mise and similar installs), and if Bun still can't be started, trigger dev reports a readable error and trigger deploy skips local skill discovery with a warning and carries on. (15797c9f2)
  • Bundled task files now keep their project layout (for example /app/src/trigger/tasks.mjs) when the CLI runs from outside the project, such as npx trigger.dev deploy. Before, they could land under a path containing the project's location, away from the files additionalFiles copies next to them, so reads relative to import.meta.url failed. (0c03b59b9)
  • Show CLI command errors in the same error format as other CLI errors, and keep them visible with --log-level error. (c515c3f74)
  • Deploys now report a warmup command that loads your config and task files offline without running any task, so the platform can prepare faster run starts for your deployment. (5479177af)
  • Generate the machine ID and the managed run controller ID on first use instead of at import, so importing these modules draws no randomness and a process restored from a warm start does not reuse IDs drawn before it was saved. (a8ac49cd3)
  • Deploys on the node-24 and node-26 runtimes now build a Node compile cache for your bundled code during the image build, so runs spend less time compiling your tasks and their dependencies before they start. node-22 deploys are unchanged. (cb1e7362f)
  • Report a run whose process the kernel killed for running out of memory as TASK_PROCESS_OOM_KILLED, rather than as a generic exit after SIGKILL, when the out-of-memory kill is counted in the run's cgroup. (7a2a7dc80)
  • Deployed task processes now receive secret environment variables only with the run, instead of also in the environment the process starts with. (489a6dff3)
  • Deployed task processes now start with the environment variables that Node, OpenSSL, libuv or the dynamic loader read only at startup (such as LD_PRELOAD, OPENSSL_CONF, NODE_ICU_DATA, TZ and UV_*), and the run's logs warn, by name only, about other startup-only variables (such as NODE_OPTIONS, MALLOC_* or GLIBC_TUNABLES) that arrive too late to take effect. (60d1774df)
  • Updated dependencies:
    • @trigger.dev/core@4.8.6
    • @trigger.dev/build@4.8.6
    • @trigger.dev/schema-to-json@4.8.6

@trigger.dev/core@4.8.6

Patch Changes

  • Deploys on the bun-1.4 runtime now compile the run worker and your task files into a Bun executable with bytecode, so runs start faster. import.meta.url and __dirname still point at your files under /app, so files you read next to your code must be in the image as before (e.g. with additionalFiles). Set build.bunBytecode: false in trigger.config.ts to turn compilation off. (8130e5e73)
  • trigger dev and trigger deploy no longer crash with spawn ... ENOENT on bun runtimes when Bun isn't installed at ~/.bun. The CLI now falls back to bun on your PATH (Homebrew, mise and similar installs), and if Bun still can't be started, trigger dev reports a readable error and trigger deploy skips local skill discovery with a warning and carries on. (15797c9f2)
  • Deploys now report a warmup command that loads your config and task files offline without running any task, so the platform can prepare faster run starts for your deployment. (5479177af)
  • Allow an explicit audience when signing and verifying JWTs and user-actor tokens. (01337977e)
  • Generate the machine ID and the managed run controller ID on first use instead of at import, so importing these modules draws no randomness and a process restored from a warm start does not reuse IDs drawn before it was saved. (a8ac49cd3)
  • Deploys on the node-24 and node-26 runtimes now build a Node compile cache for your bundled code during the image build, so runs spend less time compiling your tasks and their dependencies before they start. node-22 deploys are unchanged. (cb1e7362f)
  • webhooks.notion() endpoints accept Notion's verification request. While the endpoint has no signing secret, the verification_token Notion sends is stored as its signing secret, so you can paste it back into Notion and later deliveries verify with it. Redeploy with this version for existing Notion endpoints to pick it up. (4288ea912)
  • Support scoped run tokens without an environment key, including offloaded task inputs and stream waits. Explain why a run has no usable credential for an operation. (ed0147895)
  • Fix webhook verification for webhooks.brex(), which now reads the webhook-id, webhook-timestamp and webhook-signature headers Brex sends instead of svix-* headers, and for webhooks.composio(), which now keys the signature with the secret's raw text as Composio does instead of base64-decoding it. PagerDuty, Sentry, Vercel, Zendesk, Attio, DocuSign and Intercom endpoints now default to pasting the provider-issued signing secret, and Linear and Calendly offer both generating and pasting one. Redeploy with this version for existing endpoints to pick up the change. (b5b311407)

@trigger.dev/linear@4.8.6

Patch Changes

  • Updated dependencies:
    • @trigger.dev/core@4.8.6
    • @trigger.dev/sdk@4.8.6

@trigger.dev/python@4.8.6

Patch Changes

  • Updated dependencies:
    • @trigger.dev/core@4.8.6
    • @trigger.dev/sdk@4.8.6
    • @trigger.dev/build@4.8.6

@trigger.dev/react-hooks@4.8.6

Patch Changes

  • Updated dependencies:
    • @trigger.dev/core@4.8.6

@trigger.dev/redis-worker@4.8.6

Patch Changes

  • Updated dependencies:
    • @trigger.dev/core@4.8.6

@trigger.dev/rsc@4.8.6

Patch Changes

  • Updated dependencies:
    • @trigger.dev/core@4.8.6

@trigger.dev/schema-to-json@4.8.6

Patch Changes

  • Updated dependencies:
    • @trigger.dev/core@4.8.6

@trigger.dev/slack@4.8.6

Patch Changes

  • Updated dependencies:
    • @trigger.dev/core@4.8.6
    • @trigger.dev/sdk@4.8.6

@trigger.dev/sdk@4.8.6

Patch Changes

  • concurrencyKey now also takes an object, so one run can be limited by two limits keyed by different things, like a cap per session and a cap per organization. default is the run's own key and every other entry gives a named limit its own key: concurrencyKey: { default: sessionId, [orgLimit.name]: orgId }. A string key works as before. (4961fc474)
  • webhooks.notion() endpoints accept Notion's verification request. While the endpoint has no signing secret, the verification_token Notion sends is stored as its signing secret, so you can paste it back into Notion and later deliveries verify with it. Redeploy with this version for existing Notion endpoints to pick it up. (4288ea912)
  • Support scoped run tokens without an environment key, including offloaded task inputs and stream waits. Explain why a run has no usable credential for an operation. (ed0147895)
  • Fix webhook verification for webhooks.brex(), which now reads the webhook-id, webhook-timestamp and webhook-signature headers Brex sends instead of svix-* headers, and for webhooks.composio(), which now keys the signature with the secret's raw text as Composio does instead of base64-decoding it. PagerDuty, Sentry, Vercel, Zendesk, Attio, DocuSign and Intercom endpoints now default to pasting the provider-issued signing secret, and Linear and Calendly offer both generating and pasting one. Redeploy with this version for existing endpoints to pick up the change. (b5b311407)
  • Updated dependencies:
    • @trigger.dev/core@4.8.6

@trigger.dev/convex@4.8.6

@github-actions github-actions Bot changed the title chore: release chore: release v4.8.5 Nov 10, 2026
@coderabbitai

coderabbitai Bot commented Nov 10, 2026 •

Copy link
Copy Markdown
Contributor

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

Run configuration

  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Repository UI
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 39f89857-5a88-4912-b64c-2f5c6c809cd5

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • Trigger review
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

@devin-ai-integration devin-ai-integration Bot left a comment •

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Note

Newer findings are available below. Devin Review posted a newer report on this PR, in addition to the findings presented here.

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no bugs or issues to report.

Devin Review

@github-actions github-actions Bot changed the title chore: release v4.8.5 chore: release Nov 11, 2026
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from c798009 to c2ba28c Compare November 11, 2026 11:24
@github-actions github-actions Bot changed the title chore: release chore: release v4.8.5 Nov 11, 2026
@github-actions github-actions Bot changed the title chore: release v4.8.5 chore: release Nov 11, 2026
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from c2ba28c to 8dcdb5a Compare November 11, 2026 12:26
@github-actions github-actions Bot changed the title chore: release chore: release v4.8.5 Nov 11, 2026
@github-actions github-actions Bot changed the title chore: release v4.8.5 chore: release Nov 11, 2026
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 8dcdb5a to 438977c Compare November 11, 2026 13:03
@github-actions github-actions Bot changed the title chore: release chore: release v4.8.5 Nov 11, 2026
@github-actions github-actions Bot changed the title chore: release v4.8.5 chore: release Nov 11, 2026
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 438977c to 4b947cf Compare November 11, 2026 13:58
@github-actions github-actions Bot changed the title chore: release chore: release v4.8.5 Nov 11, 2026
@github-actions github-actions Bot changed the title chore: release v4.8.5 chore: release Nov 11, 2026
@github-actions
github-actions Bot force-pushed the changeset-release/main branch 2 times, most recently from 712829d to 56ad770 Compare November 11, 2026 15:29
@github-actions github-actions Bot changed the title chore: release chore: release v4.8.5 Nov 11, 2026
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 56ad770 to 9f298dc Compare November 11, 2026 15:38
@github-actions github-actions Bot changed the title chore: release v4.8.5 chore: release Nov 11, 2026
@github-actions github-actions Bot changed the title chore: release chore: release v4.8.5 Nov 11, 2026
@github-actions github-actions Bot changed the title chore: release v4.8.5 chore: release Nov 11, 2026
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 9f298dc to 8cc2efd Compare November 11, 2026 16:16
@github-actions github-actions Bot changed the title chore: release chore: release v4.8.5 Nov 11, 2026
@github-actions github-actions Bot changed the title chore: release v4.8.5 chore: release Nov 11, 2026
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 8cc2efd to 78303ba Compare November 11, 2026 17:20
@github-actions github-actions Bot changed the title chore: release chore: release v4.8.5 Nov 11, 2026
@github-actions github-actions Bot changed the title chore: release v4.8.5 chore: release Nov 11, 2026
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 78303ba to dd547b0 Compare November 11, 2026 18:12
@github-actions github-actions Bot changed the title chore: release chore: release v4.8.5 Nov 11, 2026
@github-actions github-actions Bot changed the title chore: release v4.8.5 chore: release Nov 11, 2026
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from dd547b0 to 04e8df7 Compare November 11, 2026 21:53
@github-actions github-actions Bot changed the title chore: release chore: release v4.8.5 Nov 11, 2026
@github-actions github-actions Bot changed the title chore: release v4.8.5 chore: release Nov 11, 2026
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 04e8df7 to daaab13 Compare November 11, 2026 23:47
@github-actions github-actions Bot changed the title chore: release chore: release v4.8.5 Nov 11, 2026
@github-actions github-actions Bot changed the title chore: release v4.8.5 chore: release Nov 12, 2026
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from daaab13 to ac01d64 Compare November 12, 2026 10:57
@github-actions github-actions Bot changed the title chore: release chore: release v4.8.6 Nov 12, 2026
@matt-aitken
matt-aitken disabled auto-merge November 12, 2026 13:37
@github-actions

github-actions Bot commented Nov 12, 2026 •

Copy link
Copy Markdown
Contributor Author

🧭 Helm Chart Prerelease Published

Version: 4.8.6-pr5109.301388f

Install:

helm upgrade --install trigger \
  oci://ghcr.io/triggerdotdev/charts/trigger \
  --version "4.8.6-pr5109.301388f"

⚠️ This is a prerelease for testing. Do not use in production.

@github-actions github-actions Bot changed the title chore: release v4.8.6 chore: release Nov 12, 2026
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from ac01d64 to 301388f Compare November 12, 2026 14:04
@github-actions github-actions Bot changed the title chore: release chore: release v4.8.6 Nov 12, 2026
@matt-aitken
matt-aitken added this pull request to the merge queue Nov 12, 2026
@github-merge-queue
github-merge-queue Bot removed this pull request from the merge queue due to failed status checks Nov 12, 2026
@github-actions github-actions Bot changed the title chore: release v4.8.6 chore: release Nov 16, 2026
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 301388f to 90830c0 Compare November 16, 2026 17:00
@github-actions github-actions Bot changed the title chore: release chore: release v4.8.6 Nov 16, 2026

@devin-ai-integration devin-ai-integration Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no bugs or issues to report.

Devin Review

@github-actions github-actions Bot changed the title chore: release v4.8.6 chore: release Nov 16, 2026
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 90830c0 to 10e18c5 Compare November 16, 2026 17:44
@github-actions github-actions Bot changed the title chore: release chore: release v4.8.6 Nov 16, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants