@trigger.dev/sdk
4.8.8 · 20 Nov 2026MIT1.7M / weekRepositoryHomepagenpmAtom feed
Upgrading @trigger.dev/sdk From 4.8.3 to 4.8.4
1 release in betweenevery note read
Release by release
- New
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 allowsts:TagSessionbefore enabling them; existing integrations remain untagged. - New
Logins made with
trigger.dev loginor 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 withCLI_LOGIN_IDLE_TIMEOUT_DAYS, or set it to0to turn it off for new logins. Logins made before this change aren't affected. - New
Add
infisicalAccessTokenat@trigger.dev/sdk/oidc/infisicalto authenticate tasks with Infisical using OIDC instead of stored credentials. Supports US, EU, and self-hosted instances, custom audiences, and Infisical organization scoping. - New
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.
- New
19 other lines we could not sort, mostly version bumps
- 4.8.4
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.
- 4.8.4
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.
- 4.8.4
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.
- 4.8.4
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.
- 4.8.4
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.
- 4.8.4
Health alerts can now watch a chosen subset of checks — flow, execution and liveness — instead of all three.
- 4.8.4
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=falseto turn them off. - 4.8.4
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.
- 4.8.4
Alerts now require at least one channel (email, Slack or webhook). The option to notify the Dashboard Agent chat has been removed.
- 4.8.4
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.
A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.