Workflow and Build Automation Release Notes

Updates for workflow automation, background jobs, continuous integration, and build tools.

Get this feed:

Products (9)

Latest Workflow and Build Automation Updates

Nov 11, 2026
Date parsed from source:
Nov 11, 2026

First seen by Releasebot:
Nov 11, 2026
Trigger.dev

Custom access and saved presets for API keys

Trigger.dev upgrades API keys with granular permissions, reusable team presets, usage-based access reviews, and IP allowlists, giving teams more control over key access. New keys also expire after 90 days by default, with other expiry options available.
Choose exactly what each API key can do, save presets for your team, and see what each key uses.

We have made some upgrades to API keys: the keys that connect your backend, CI and scripts to Trigger.dev to trigger tasks, read runs and deploy.

Here's what's new:

Set access per permission area (a group of API endpoints, like runs)

Combine presets (named permission bundles) in one key

Save your own presets for your organization

See and edit each key's access

Limit keys by IP

All of this is available on every Trigger.dev Cloud plan, including Free and Hobby.

Custom access

If no single preset fits, set a level for each of 15 areas, like Runs, Deployments and Webhooks. The levels depend on the area, from None and Read up to Read and write or Manage. The custom access docs list them all.

Custom access for a CI key: Operator plus Deploy only, set area by area.

Saved presets

Save custom access as a preset for your organization (up to 50). It appears in every project and environment, so your team creates each kind of key the same way.

See and edit a key's access

Each key now shows when it last used each area.

Click Edit access to change what any active key can do, except the root key (each environment's default full-access key), and see what it gains and loses before saving.

Narrow to what it used

Once a key has at least 7 days of usage, you can click Narrow to what it used to trim the access to what it needed in the past 30 days, or since it was created if the key is newer than that. You review the change before saving, and it applies without a redeploy.

A key's details: when it last used each area, and Narrow to what it used.

IP allowlists

Limit a key to up to 50 IP addresses or CIDR ranges, like your CI runners or servers.

Changes to expiry

New keys expire after 90 days by default, or you can pick 30 days, 1 year or a custom date. Existing keys don't change.

Learn more

Create a key on the dashboard's API keys page. The API keys docs and custom access docs cover every preset and area.
Original source
Nov 11, 2026
Date parsed from source:
Nov 11, 2026

First seen by Releasebot:
Nov 11, 2026
Windmill by Windmill Labs

v1.868.0

Windmill releases updates that add Tailwind CSS v4 support for raw app bundles and improve job polling, deploy comparisons, and Claude structured outputs. The release also refines workspace and run-list behavior, treats skipped jobs as successful, and updates CLI dependencies past security advisories.
1.868.0 (2026-11-11)

Features

compile tailwind css v4 in raw app bundles (#12346) (18556fd)

Bug Fixes

back off job polling to 2s after 100 polls (#12344) (abede3a)

bump cli bundled minimatch, yaml and fast-uri past advisories (#12337) (f7f2eee)

carry every compared field through fork deploy and diff (#12348) (f9cf596)

force the structured output tool on claude 3 and 4 again (#12349) (9c76c79)

hide your own empty user space with the hide empty folders option (#12345) (d37dcca)

keep the runs list scrollbar and column labels unclipped (#12347) (d1e97ef)

treat skipped jobs as successful in result and wait paths (#12340) (9d9875c)

Performance Improvements

build the ee debug file in the same depot build as the image (#12339) (2688493)

Original source
All of your release notes in one feed

Join Releasebot and get updates from Trigger.dev and hundreds of other software products.

Create account
Get updates with:
Nov 10, 2026
Date parsed from source:
Nov 10, 2026

First seen by Releasebot:
Nov 11, 2026
Trigger.dev

Trigger.dev v4.8.4

Trigger.dev releases outbound OIDC for task authentication and GitHub Actions trusted publishing, alongside a major API key management overhaul with granular access, expiry, and IP restrictions. The update also improves alerts, credentials, and deployment reliability, with fixes for log ingestion and more.
Outbound OIDC for tasks, inbound trusted publishing from GitHub Actions, and an API keys management overhaul.

1 new feature, 10 improvements, 1 bug fix, and 23 server changes.

Highlights

OIDC for tasks and trusted publishing for deployments

Use short-lived identity tokens in both directions: tasks authenticate to external services, and GitHub Actions authenticates to Trigger.dev to deploy.

Outbound: workload identity. Your tasks can access services such as AWS, Anthropic, and Infisical without storing long-lived credentials. Configure the service to trust your organization's OIDC issuer and grant access to specific project environments. See the OIDC docs.

For example, a task can assume an AWS IAM role to access S3 without a stored AWS access key. Enable sessionTags: true on awsCredentialProvider to attach verified run identity tags and restrict IAM permissions by task. This requires sts:TagSession in the role's trust policy; existing integrations remain untagged unless you opt in. See the AWS guide.

Inbound: trusted publishing. Deploy from GitHub Actions without storing a Trigger.dev API key or personal access token. Configure which repository and branches, tags, or GitHub Environments can publish, then use GitHub's OIDC identity to authorize the CLI. Builds run on Trigger.dev's build server without granting the CLI access to environment variables. Trusted publishing also supports Preview branch cleanup and deployment promotion. See the trusted publishing guide.

Improvements

CLI and MCP server logins now expire after 7 days of inactivity. When an idle login expires, the CLI and MCP server start a new login flow instead of failing with an auth error. In CI, the CLI prompts you to log in again. Self-hosted instances can configure the window with CLI_LOGIN_IDLE_TIMEOUT_DAYS, or set it to 0 to disable for new logins. Logins created before this change are not affected.

Add infisicalAccessToken from @trigger.dev/sdk/oidc/infisical to authenticate tasks with Infisical using OIDC instead of stored credentials. Supports US, EU, and self-hosted Infisical instances, with custom audiences and organization scoping.

Deploy from GitHub Actions using Trusted Publishing and GitHub OIDC, without storing a Trigger.dev API key. Deployments run entirely on the build server and do not grant the CLI access to environment variables.

preview archive and promote now support GitHub Actions Trusted Publishing without storing API keys. Preview deploys for closed or merged pull requests now archive their branch. preview archive also accepts Preview environment API keys via TRIGGER_ACCESS_TOKEN. Failed archive operations now exit with an error; concurrent cleanup jobs succeed when another job has already archived the same branch generation.

Add a bundled Convex agent skill for integrating Trigger.dev with Convex, covering transactional triggering, Realtime progress, recovery, and scoped-token safety. Install it manually from the package; it is not included in the CLI skills installer.

Self-hosted supervisors running tasks in microVMs can now delete finished run suspend snapshots from shared storage, instead of leaving them behind.

Browser realtime subscriptions now resume reliably after the tab is hidden and shown again, via an upgrade to @electric-sql/client 1.3.0. Apps that already depend on 1.3.0 can share a single copy with the SDK.

Run credentials now work for run results, rescheduling, schedules, and environment-variable operations inside tasks. Run credentials stay scoped to the current environment: shared schedules cannot be changed, and parent environment variables cannot be written.

chat.agent now accepts only user messages and answers to tool calls from chat clients. Tool approvals and outputs are merged onto the stored call they answer and run with the input from the agent's own history, so a client cannot inject tool calls or change a call's input. chat.headStart drops tool calls from client-provided history; upsertIncomingMessage only adds user messages.

Create public tokens without scopes from inside tasks using run credentials, without requiring an environment secret key.

Bug fixes

Fix logs and spans with large numeric object keys failing to ingest, which dropped the rest of their batch.

Server changes

These changes are included in the v4.8.4 Docker image and are already live on Trigger.dev Cloud:

API keys now support custom per-area access (Runs, Deployments, etc.), optionally scoped to specific tasks. Edit access on an existing key without rotating it; the API keys page marks keys whose access differs from their preset.

API keys can expire on a custom date. Pick a day from a calendar; the key stops working at the end of that day in your local timezone.

Restrict an API key to a list of IP addresses. Configure the list when creating or edit it later; the API keys page now shows the IP address each key was last used from.

Organizations can save custom API key access as named presets and reuse them when creating keys across any project.

Clicking an API key opens a detail panel showing its access, when it last used each area, and its metadata. From there you can narrow the key's access to only what it used in the last 30 days, without changing its secret.

Choose an API key's expiry from presets or a calendar in a unified picker, with date previews and expiration at the end of the chosen day in UTC.

The API keys page now shows when each key expires and when it was revoked. The "How to set env vars" dialog no longer shows the secret key. Custom access is now displayed as a table of permission levels per area, with disabled options shown with the reason.

Dashboard-created personal access tokens now expire after the lifetime you choose (30, 90, or 365 days by default). Expired tokens return an error showing when it expired and where to create a new one.

An email goes out 7 days before a personal access token expires, and again when it has, so a CI deploy using it doesn't break by surprise. Set PERSONAL_ACCESS_TOKEN_EXPIRY_EMAILS_ENABLED=false to disable.

Alerts can be grouped: select multiple alerts and create a group that fires when any or all of them fire, with its own channels and expiry. Groups can be created via the API with their members in one call. Alert members keep evaluating independently but notify only through the group.

Health alerts can now watch a subset of checks (flow, execution, liveness) instead of always watching all three.

Alerts now require at least one notification channel (email, Slack, or webhook). The Dashboard Agent chat notification option has been removed.

Admins and Developers can now delete alerts. Health metric charts now use straight line segments.

The Environment variables page now filters by environment, opening on the environment you're currently in, with a picker for preview branches. Deleting a variable asks for confirmation.

The side menu has a new Security section above Manage, grouping API keys, Environment variables, Trusted Publishing, and OIDC.

Project JWT minting now rejects expiration times longer than 24 hours.

Dashboard sessions past their deadline now end on their next request, including background data requests and form submissions, not only on page navigation.

Restore duration wait details and the Skip waitpoint action in the dashboard.

Fix the Logs page redirecting to Tasks when Logs is visible in the sidebar.

Fix a new project's first deploys failing with "Failed to get deployment image ref" when two deploys start at the same time.

Triggering a task with a payload over the offload threshold from inside a running task works again.

Stop runs waiting for capacity from being requeued and started a second time while their first attempt is still pending.

Long GitHub organization and repository names on the Trusted Publishing page now truncate to one line, with the full name shown on hover.

How to upgrade

Update the trigger.dev/* packages to v4.8.4 using your package manager:

npx trigger.dev@latest update # npm pnpm dlx trigger.dev@latest update # pnpm yarn dlx trigger.dev@latest update # yarn bunx trigger.dev@latest update # bun

Self-hosted users: update your Docker image to ghcr.io/triggerdotdev/trigger.dev:v4.8.4.
Original source
Nov 10, 2026
Date parsed from source:
Nov 10, 2026

First seen by Releasebot:
Nov 11, 2026
Dagger

v1.0.0-beta.27: Merge pull request #15134 from dagger/gate-post-beta25-api-impl

Dagger updates core to serve the v1.0.0-beta.25 view as beta.25 did.

core: serve the v1.0.0-beta.25 view as beta.25 did
Original source
Nov 10, 2026
Date parsed from source:
Nov 10, 2026

First seen by Releasebot:
Nov 11, 2026
n8n

2.48.0

n8n releases a feature-rich update with improved Apps previews and bindings, deeper Assistant integration, a new Work IQ OAuth2 credential, and agent and migration enhancements. It also fixes issues across workflows, integrations, security, and installation reliability.
Bug Fixes

ai-builder: Return the raw body when fetch-url reads JSON, XML, CSV or YAML (#42949) (6640010)

Align workflow history header dividers (#43167) (73698d6)

Compression Node: Preserve custom gzip file names (#42063) (a196d7d)

core: Apply the redaction policy to log streaming, telemetry and error reports (#42905) (c4c66d3)

core: Decode webhook bodies in the declared charset (#42037) (71ea718)

core: Exclude Nano Banana models from Gemini chat model pickers (#43082) (5038878)

core: Keep Anthropic thinking valid in agents after prompt rewrites and web search (#43160) (92b6fea)

core: Keep observational memory running after a user stops a HITL card (#43192) (cf28f65)

core: Keep retry backoff when a trigger fails right after reactivation (#43105) (b43750c)

core: Keep the OAuth JWKS available when a retired signing key cannot be read (#42465) (7a15776)

core: Keep the warning level of sub-workflow errors rebuilt for the parent (#42727) (4dcbe9e)

core: Only allow users who can edit a workflow to own its migration findings (#43091) (1faa2fa)

core: Retire stale scheduled tasks in repeated batches in each reaper pass (#43076) (505c0c0)

core: Settle abandoned tool calls when an Agents runtime turn starts (#43194) (75b8ea0)

core: Subscribe Telegram agent channels to button clicks (#43221) (4cff3b3)

editor: Keep the API settings empty state in the header column (#43219) (c3ba6a3)

editor: Polish skill files and version history (#43180) (4b7b145)

editor: Update favicon and preview image branding (#43214) (c2ea734)

editor: Use the current Assistant icon across the editor (#42441) (5ee06d3)

Exit with distinct codes for failed and incomplete community package scans (CE-3548) (#42780) (0db6d6b)

Extract document IDs from Drive URLs (#42478) (fe45950

Honor Continue On Fail for initial connection errors (#41118) (ce23494)

Make npm install of n8n work on all platforms again (#43028) (01c87f9)

Preserve API version headers regardless of case (#42473) (d49b632)

RabbitMQ Node: Await queue bindings before returning channel (#43033) (e87308e)

Show the credential redaction cause without sharing permission (#42711) (b3a40ee)

Update Multer to 2.5.0 and preserve upload cleanup (#43157) (731c17c)

Use the workflow's owning project for node parameter lookups (#43179) (8823b65)

Features

Add an ability to select an element in Apps preview (#42930) (b85c9d7)

ai-builder: Bump the default Assistant model to Claude Opus 5.5 (#42990) (44bc5b0)

App bindings UI (#42986) (2509674)

core: Add Microsoft Work IQ OAuth2 credential (#43172) (a3ef7d9)

core: Emit telemetry and audit events when a user logs out (#42413) (612d1d3)

core: Hide archived workflows in the migration report by default (#42781) (a070476)

core: Stop agent runs when the Gateway credits wallet is empty (#41473) (5dbef9a)

editor: Create Listbox primitive for Design System (#42754) (588918d)

editor: Link Apps to n8n Assistant chats (#42969) (5339f0c)

editor: Show a message when the migration report takes long to load (#42996) (c1420c6)

editor: Show a restriction callout in the credential modal (#42678) (38666b6)

editor: Unify chat messages and Markdown rendering (#42315) (5e38fe6)

Node operation annotations for engine (#41835) (b3ecad1)

Open the migration report filtered to the recipient from notification emails (#43089) (010f33c)

Paddle Node: Rename node to Paddle Classic (#43042) (ddabd54)

Original source
Nov 10, 2026
Date parsed from source:
Nov 10, 2026

First seen by Releasebot:
Nov 11, 2026
Windmill by Windmill Labs

v1.867.0

Windmill releases updates to AI sessions, public app access, and tool-call visibility, alongside workflow and editor fixes, improved diagram rendering and log streaming, and faster release builds.
1.867.0 (2026-11-10)

Features

fold sidebar AI chats and sessions inactive for over a week (#12314) (466885f)

gate public apps on cloud plans and unpublish them on archive (#12321) (a9f5a9c)

reveal the failed call from a tool group's failed badge (#12320) (0e1464e)

Bug Fixes

build Azure block upload URLs from the account endpoint (#12333) (38e7463)

cut long item summaries in the session composer placeholder (#12312) (abfa6b1)

drop renamed and deleted items from Home recent list (#12317) (c144738)

explain why a fork folder deploy can leave a lasting conflict (#12323) (6a11d30)

keep siblings in place when editing an EditableInput (#12318) (5e89ba1)

keep the sessions sidebar icons stable until the workspace list loads (#12322) (9d7adef)

load mermaid diagrams without source flashes or layout jumps (#12319) (fecc8a6)

mark delete and discard tool confirmations as destructive (#12324) (949ef23)

name agents in session chat tool call labels (#12313) (80e2be5)

python: give folder modules an empty path so relative imports resolve to workspace scripts (#12307) (0323310)

read dedicated worker entries with the runnable parser (#12326) (df6a61c)

send AI session requests with their own workspace's AI config (#12330) (e8d48b1)

stop forcing the structured output tool for Claude AI agents (#12331) (5b4f918)

stream logs of a selected step nested in a subflow or loop (#12334) (841cc3e)

tighten forwarded http trigger headers and route resolution (#12298) (c3adae1)

worker: wait up to 3 min for migrations before exiting (#12316) (a2685ef)

Performance Improvements

cut release CI wall time and build windmill-extra on its own release (#12329) (7ec64ab)

Original source
Nov 10, 2026
Date parsed from source:
Nov 10, 2026

First seen by Releasebot:
Nov 11, 2026
Windmill by Windmill Labs

v1.866.0

Windmill releases configurable columns and CSV, JSON, and XLSX exports on the runs page, adds job start times to AI session details, and improves flow reliability and audit log performance.
1.866.0 (2026-11-10)

Features

configurable columns and csv/json/xlsx export on the runs page (#12302) (47005d5)

show when each job started in the ai session jobs popover (#12301) (8b40416)

Bug Fixes

keep flow nodes on rename and stop masking flow load errors (#12303) (3bf4864)

never break running flows when their flow is deleted (#12306) (e3ff8be)

pin rsa to 0.9 so the lock refresh stops pulling 0.10 (#12299) (188b6cc)

read the git sync callback script with the runnable parser (#12304) (2e422b4)

Performance Improvements

list audit logs by timestamp so only recent partitions are read (#12309) (a6ec7d0)

Original source
Nov 10, 2026
Date parsed from source:
Nov 10, 2026

First seen by Releasebot:
Nov 11, 2026
Trigger.dev

trigger.dev v4.8.4

Trigger.dev releases v4.8.4 with stronger security controls, including customizable and IP-restricted API keys, GitHub OIDC trusted publishing, and AWS session tags. The update also improves task credentials, alerts, browser realtime reliability, and dashboard workflows, alongside numerous fixes.
trigger.dev v4.8.4

Upgrade

npx trigger.dev@latest update # npm pnpm dlx trigger.dev@latest update # pnpm yarn dlx trigger.dev@latest update # yarn bunx trigger.dev@latest update # bun

Self-hosted Docker image: ghcr.io/triggerdotdev/trigger.dev:v4.8.4

Release notes

Read the full release notes: https://trigger.dev/changelog/v4-8-4

Highlights

Add opt-in AWS session tags with awsCredentialProvider({ sessionTags: true }) for task-level IAM restrictions and attribute-based permissions. Tags come from the verified run identity. Update the role trust policy to allow sts:TagSession before enabling them; existing integrations remain untagged. (c8ae1ffb5)

Improvements

Logins made with trigger.dev login or the MCP server now stop working after 7 days without use. When that happens, the CLI and the MCP server start a new login instead of failing with an auth error, and in CI the CLI says to log in again. Self-hosted instances can change the window with CLI_LOGIN_IDLE_TIMEOUT_DAYS, or set it to 0 to turn it off for new logins. Logins made before this change aren't affected. (c8ee9e309)

Add infisicalAccessToken at @trigger.dev/sdk/oidc/infisical to authenticate tasks with Infisical using OIDC instead of stored credentials. Supports US, EU, and self-hosted instances, custom audiences, and Infisical organization scoping. (63b58f329)

Deploy from GitHub Actions using Trusted publishing and GitHub OIDC without storing a Trigger.dev API key. These deployments run entirely on the build server and do not grant the CLI access to environment variables. (9aafe6989)

Use GitHub Actions trusted publishing with preview archive and promote, without storing API keys. Preview deploys for closed or merged pull requests now archive their branch. preview archive also supports Preview environment API keys through TRIGGER_ACCESS_TOKEN. (d9172638a)

Failed Preview archive operations now exit with an error for API-key and personal-token authentication too, including automatic cleanup during deploys. CI cleanup jobs that previously passed despite an archive failure will now fail. Concurrent cleanup jobs succeed when another job has already archived the same branch generation.

Add a bundled agent skill for integrating Trigger.dev with Convex, including transactional triggering, Realtime progress, recovery, and scoped-token safety. Install it manually from the package; it is not part of the CLI skills installer. (9422dc65d)

Self-hosted supervisors that run tasks in microVMs can now have a finished run's suspend snapshots deleted from shared storage, instead of leaving them behind. The server-only checkpoint client gains a deleteSnapshots call for this. (95f4cbbad)

Browser realtime subscriptions now resume reliably after the tab is hidden and shown again. This comes from upgrading @electric-sql/client to 1.3.0, which also lets apps that depend on 1.3.0 share a single copy with the SDK. (3900d8906)

Use run credentials for run results, rescheduling, schedules, and environment-variable operations inside tasks. Run credentials remain limited to the current environment: shared schedules cannot be changed, and parent environment variables cannot be written. (cd58c750b)

chat.agent now accepts only two kinds of message from a chat client: user messages, and answers to tool calls the agent made. A tool approval or tool output is merged onto the stored call it answers and runs with the input from the agent's own history, so a client can't add tool calls or change a call's input. chat.headStart drops tool calls from the history the client sends, and upsertIncomingMessage only adds user messages. (44feaaff6)

Create public tokens without scopes from inside tasks using run credentials, without requiring an environment secret key. (306d960ca)

Bug fixes

Fix logs and spans with large numeric object keys failing to ingest and dropping the rest of their batch. (99a626aa3)

Server changes

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

API keys can have custom access: combine access presets or set a level for each area, such as Runs or Deployments, optionally limited to selected tasks. Edit access changes what an existing key can do without rotating it, and the API keys page marks keys whose access differs from their preset today.

New API keys can expire on a custom date. Pick Custom date in the Expires menu and choose a day from the calendar; the key stops working at the end of that day in your local time zone.

Restrict an API key to a list of IP addresses so requests using it from anywhere else are rejected. Set the list when creating a key or edit it later from the API keys page, which now also shows the IP address each key was last used from.

Organizations can save custom API key access as a preset and reuse it when creating keys in any project. Saved presets appear under Your presets in the access picker, and organization Owners and Admins can save and delete them.

Click an API key to see its access, when it last used each area, and its details in a side panel. From there you can narrow a key to what it used in the last 30 days, without changing its secret.

Alerts can be grouped: select alerts in the list and create a group that raises when any or all of them fire, with its own channels and expiry. Members keep evaluating but notify only through the group. Groups can also be created through the API, with their members in one call.

Health alerts can now watch a chosen subset of checks — flow, execution and liveness — instead of all three.

Email the owner of a dashboard-created personal access token 7 days before it expires, and again when it has, so a CI deploy using it doesn't break by surprise. Set PERSONAL_ACCESS_TOKEN_EXPIRY_EMAILS_ENABLED=false to turn them off.

Personal access tokens created on the dashboard now expire after the lifetime you choose (30, 90 or 365 days by default). Requests made with an expired token get an error that says when it expired and where to create a new one. Existing tokens keep working as before.

Alerts now require at least one channel (email, Slack or webhook). The option to notify the Dashboard Agent chat has been removed.

Choose an API key's expiry from presets or a calendar in one picker, with date previews and expiration at the end of the chosen day in UTC.

The API keys page shows when each key expires and when it was revoked, and the "How to set env vars" dialog no longer displays your secret key. Custom access is now a table of levels for each area, and options a key can't use are shown disabled with the reason.

The Environment variables page now filters by environment, opening on the environment you're in, with a picker for preview branches. Deleting a variable asks for confirmation first.

The side menu has a new Security section, just above Manage, that groups API keys, Environment variables, Trusted publishing and OIDC.

Alerts: Admins and Developers can delete alerts; health metric charts use straight segments.

Alert charts and alert evaluation are no longer limited by the plan's query period.

Project JWT minting now rejects expiration times longer than 24 hours.

Dashboard sessions past their deadline now end on their next request, including background data requests and form submissions, not only on page navigation.

Restore duration wait details and the Skip waitpoint action in the dashboard.

Fix the Logs page redirecting to Tasks when Logs is visible in the sidebar.

Fix a new project's first deploys failing with "Failed to get deployment image ref" when two of them start at the same time.

Triggering a task with a payload over the offload threshold from inside a running task works again. Run-scoped tokens and restricted API keys upload offloaded payloads into their own namespace and may only trigger with payloads they uploaded, while pointers at other runs' stored payloads or outputs are still rejected.

Stop runs that wait a long time for capacity from being requeued and started a second time while their first start is still pending.

Long GitHub organization and repository names on the Trusted publishing page now stay on one line and truncate, with the full name shown on hover.

All packages: v4.8.4

@trigger.dev/build, @trigger.dev/convex, @trigger.dev/core, @trigger.dev/linear, @trigger.dev/python, @trigger.dev/react-hooks, @trigger.dev/redis-worker, @trigger.dev/rsc, @trigger.dev/schema-to-json, @trigger.dev/sdk, @trigger.dev/slack, trigger.dev

Contributors

Eric Allam, Chris Arderne, @d-cs, @nicktrn, Wes Mason, Katia Bulatova, Oskar Otwinowski, Matt Aitken, Paul Cioanca, @isshaddad, James Ritchie, github-actions[bot], claude[bot], João Dias, @D-K-P, pullfrog[bot]

Full changelog: v4.8.3...v4.8.4
Original source
Nov 10, 2026
Date parsed from source:
Nov 10, 2026

First seen by Releasebot:
Nov 11, 2026
Inngest

v1.52.0

Inngest adds live event subscriptions for running workflows, app sync history through its v2 API, and a CLI command to deploy apps from inngest.toml. The release also fixes several dashboard and Insights issues, including stale run details and quoted JSON string values.
Release Notes

#5149 feat(executor): step.subscribe inboxes

Adds executor support for step.subscribe, so a run can receive and read matching events while it runs.

#5163 feat(api): get app sync history via v2 api

read app sync history with GET /v2/apps/{appId}/syncs and GET /v2/apps/{appId}/syncs/{syncId}. also available through inngest api list-app-syncs / get-app-sync and the list_app_syncs / get_app_sync mcp tools. the dev server returns 501 for both history endpoints; use GetApp.latestSync for its current state.

#5201 fix(ui): Don't report dev server flags as ready before they load

Fix the dev server's Insights and Sessions pages redirecting to Runs when running w/ --duckdb.

#5222 fix(ui): reset run-scoped state when navigating between runs

Run details no longer show the previous run's selected step after navigating to another run.

#5225 fix(insights): Show a JSON column's string values unquoted

Insights shows string values from JSON fields without surrounding quotes.

#5226 feat(cli): add inngest deploy for apps in inngest.toml (INF-801)

Adds inngest deploy, which builds an app described in inngest.toml and deploys it to Inngest compute. inngest deploy example-config prints an example config. Requires compute access.

Migration Notes

#5163 feat(api): get app sync history via v2 api
Testing
focused api, cli, and dev server tests passed. the api suites cover pagination, validation, error mapping, and 501 responses without a sync-history provider.

#5171 feat(dashboard): show webhook health

Ship after the monorepo GraphQL fields are deployed.

Changelog

🚀 Features

(api) Get app sync history via v2 api (#5163)

(executor) Step.subscribe inboxes (#5149)

(cli) Add inngest deploy for apps in inngest.toml (INF-801) (#5226)

🐛 Bug Fixes

(ui) Don't report dev server flags as ready before they load (#5201)

(ui) Reset run-scoped state when navigating between runs (#5222)

(executor) Don't emit lifecycle events for runs triggered by function.cancelled (#5220)

(insights) Show a JSON column's string values unquoted (#5225)

🧪 Testing

(insights) Loosen the deep nesting transpile budget to 2s (#5233)

⚙️ Miscellaneous Tasks

(duckdb) Remove cmd/duckdbbench (#5228)

Original source
Nov 10, 2026
Date parsed from source:
Nov 10, 2026

First seen by Releasebot:
Nov 10, 2026
Dagger

v1.0.0-beta.26: Merge pull request #15124 from dagger/sipsma/module-defaults-and-wolfi

Dagger now serves modules from their owning clients and reads directory modules’ default paths from the directory.

Serve modules from the client that holds them, and read a directory module's default paths from its directory
Original source

Workflow and Build Automation Release Notes

Products (9)

Latest Workflow and Build Automation Updates

Custom access and saved presets for API keys

Custom access

Saved presets

See and edit a key's access

Narrow to what it used

IP allowlists

Changes to expiry

Learn more

v1.868.0

1.868.0 (2026-11-11)

Features

Bug Fixes

Performance Improvements

Trigger.dev v4.8.4

Highlights

OIDC for tasks and trusted publishing for deployments

Improvements

Bug fixes

Server changes

How to upgrade

v1.0.0-beta.27: Merge pull request #15134 from dagger/gate-post-beta25-api-impl

2.48.0

Bug Fixes

Features

v1.867.0

1.867.0 (2026-11-10)

Features

Bug Fixes

Performance Improvements

v1.866.0

1.866.0 (2026-11-10)

Features

Bug Fixes

Performance Improvements

trigger.dev v4.8.4

trigger.dev v4.8.4

Upgrade

Release notes

Highlights

Improvements

Bug fixes

Server changes

All packages: v4.8.4

Contributors

v1.52.0

Release Notes

#5149 feat(executor): step.subscribe inboxes

#5163 feat(api): get app sync history via v2 api

#5201 fix(ui): Don't report dev server flags as ready before they load

#5222 fix(ui): reset run-scoped state when navigating between runs

#5225 fix(insights): Show a JSON column's string values unquoted

#5226 feat(cli): add inngest deploy for apps in inngest.toml (INF-801)

Migration Notes

#5163 feat(api): get app sync history via v2 api

#5171 feat(dashboard): show webhook health

Changelog

🚀 Features

🐛 Bug Fixes

🧪 Testing

⚙️ Miscellaneous Tasks

v1.0.0-beta.26: Merge pull request #15124 from dagger/sipsma/module-defaults-and-wolfi