Repository navigation
Comparing changes
Open a pull request
base repository: triggerdotdev/trigger.dev
base: 1ca7cfd
head repository: triggerdotdev/trigger.dev
compare: bd2a14e
- 10 commits
- 176 files changed
- 7 contributors
Commits on Oct 23, 2026
-
feat(webapp): label database spans with the Prisma client they use
Database query spans from the webapp now carry a db.client_type attribute naming the database client that ran the query, the same name used on the webapp's database metrics. Query latency can now be broken down by query type (INSERT, UPDATE, SELECT, ...) for each client. Mono-RevId: 6dead141fe60243a6f6b7bb9ea4847920dd288fb
Configuration menu - View commit details
-
Copy full SHA for 2e4dd94 - Browse repository at this point
Copy the full SHA 2e4dd94View commit details -
docs: rework the introduction around chat.agent, webhooks and production
Reworked the docs introduction around building agents with `chat.agent`, webhooks, and running in production, with an expanded FAQ. Mono-RevId: b79d3f40d91d699c56406a750855012dca05262b
Configuration menu - View commit details
-
Copy full SHA for d5e9e26 - Browse repository at this point
Copy the full SHA d5e9e26View commit details -
Alerts can now watch the result of a query: raise when a value crosses a threshold, when matching rows stop appearing, or when new matching rows appear — with the observed values charted on the alert detail page. Mono-RevId: 6fef942e47bcf26a8a9d707149d99033858687d2
Configuration menu - View commit details
-
Copy full SHA for c5b123d - Browse repository at this point
Copy the full SHA c5b123dView commit details -
fix(webapp): send keyless canary runs to the stable container lane
Fixed an issue where some runs from deployments without a prebuilt template could stay queued instead of starting. Mono-RevId: 2a8e5c624437ab80277ea56bb7b97ea6cb932230
Configuration menu - View commit details
-
Copy full SHA for b88c7ff - Browse repository at this point
Copy the full SHA b88c7ffView commit details -
fix(webapp): report a template key that was not written as failed
The admin template-builds route now reports a deployment as failed, with a reason, when the template key could not be stored. Mono-RevId: 52d799b6e54eefe3ba3a9c2125092dbf697ee5ed
Configuration menu - View commit details
-
Copy full SHA for 8fbc76f - Browse repository at this point
Copy the full SHA 8fbc76fView commit details -
docs: 4.8.0 follow-ups for agent examples, MCP secrets and self-hoste…
…d webhooks Docs updates for 4.8.0: `chat.agent` examples use the `streamText` passed to `run()`, the webhook secret MCP tools document `previousSecretTtlSeconds`, self-hosting docs cover turning on webhooks and `KUBERNETES_POD_RESERVED_SOURCE_PORTS`, and the agents overview introduces channels. Mono-RevId: 3eb1ed33ef2e0e21cd1197391b71a3a7c57e9785
Configuration menu - View commit details
-
Copy full SHA for 1ea559a - Browse repository at this point
Copy the full SHA 1ea559aView commit details -
refactor(webapp): extract the ensure-run-then-append helper from the …
…session append route Internal refactor of the session append endpoint. No behaviour change: appending to a session's input channel now goes through one shared server helper that other server code can reuse. Mono-RevId: c5c64aad40d4a1b19f2e8e383ff359276b97229f
Configuration menu - View commit details
-
Copy full SHA for 3cacfa4 - Browse repository at this point
Copy the full SHA 3cacfa4View commit details -
fix(webapp): show stored org values for locked flags in the admin fla…
…gs dialog The admin org flags dialog now shows an org's own value for read-only flags, and says what that value does: it overrides the global value, it's stored but ignored, or it's a server-written stamp. Stored org flags are now read one key at a time, so a single invalid value no longer makes the dialog and the admin API treat the org as having no flags. Saves keep stored values they didn't change, including keys the running version doesn't know yet. Mono-RevId: 061e76440f3462887e0b63d75b556a70ae02c480
Configuration menu - View commit details
-
Copy full SHA for a7f0f90 - Browse repository at this point
Copy the full SHA a7f0f90View commit details -
fix(cli): keep custom base images' own trust store
Fixes `trigger deploy` failing on self-hosted instances that set custom base images with `DEPLOY_BASE_IMAGES` or `DEPLOY_BUILD_BASE_IMAGES` (#5054). The deploy step that distrusts compromised emSign certificate authorities assumed the published root Debian images, so it broke on non-root or non-Debian bases such as Chainguard's. Stages built on a custom image now skip that step and keep the certificate settings the image ships with. Stages on the published images are unchanged. The self-hosting docs now state that a custom base image owns its own security hardening. Mono-RevId: 5de0cdda76e9b57d7b076d52c6ab8c763934e2d3
Configuration menu - View commit details
-
Copy full SHA for b5ed66b - Browse repository at this point
Copy the full SHA b5ed66bView commit details -
## Summary 1 new feature, 1 bug fix. ## Bug fixes - Fix `trigger deploy` failing on self-hosted instances with custom base images. Stages built on a custom image now keep the trust store that image ships with. ([`b5ed66b74`](b5ed66b)) ## Server changes These changes affect the self-hosted Docker image and Trigger.dev Cloud: - Alerts can now watch the result of any supported query: raise when a value crosses a threshold, when matching rows stop appearing, or when new matching rows appear. Create them from the Query page, the Dashboard Agent or the API, and see the alert's values charted on its page. <details> <summary>Raw changeset output</summary> # Releases ## @trigger.dev/build@4.8.1 ### Patch Changes - Updated dependencies: - `@trigger.dev/core@4.8.1` ## trigger.dev@4.8.1 ### Patch Changes - Fix `trigger deploy` failing on self-hosted instances with custom base images. Stages built on a custom image now keep the trust store that image ships with. ([`b5ed66b74`](b5ed66b)) - Updated dependencies: - `@trigger.dev/build@4.8.1` - `@trigger.dev/core@4.8.1` - `@trigger.dev/schema-to-json@4.8.1` ## @trigger.dev/linear@4.8.1 ### Patch Changes - Updated dependencies: - `@trigger.dev/core@4.8.1` - `@trigger.dev/sdk@4.8.1` ## @trigger.dev/python@4.8.1 ### Patch Changes - Updated dependencies: - `@trigger.dev/build@4.8.1` - `@trigger.dev/core@4.8.1` - `@trigger.dev/sdk@4.8.1` ## @trigger.dev/react-hooks@4.8.1 ### Patch Changes - Updated dependencies: - `@trigger.dev/core@4.8.1` ## @trigger.dev/redis-worker@4.8.1 ### Patch Changes - Updated dependencies: - `@trigger.dev/core@4.8.1` ## @trigger.dev/rsc@4.8.1 ### Patch Changes - Updated dependencies: - `@trigger.dev/core@4.8.1` ## @trigger.dev/schema-to-json@4.8.1 ### Patch Changes - Updated dependencies: - `@trigger.dev/core@4.8.1` ## @trigger.dev/slack@4.8.1 ### Patch Changes - Updated dependencies: - `@trigger.dev/core@4.8.1` - `@trigger.dev/sdk@4.8.1` ## @trigger.dev/sdk@4.8.1 ### Patch Changes - Updated dependencies: - `@trigger.dev/core@4.8.1` ## @trigger.dev/core@4.8.1 </details> Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Configuration menu - View commit details
-
Copy full SHA for bd2a14e - Browse repository at this point
Copy the full SHA bd2a14eView commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff 1ca7cfd...bd2a14e