Skip to content

chore: release v4.4.5#3406

Open
github-actions[bot] wants to merge 2 commits intomainfrom
changeset-release/main
Open

chore: release v4.4.5#3406
github-actions[bot] wants to merge 2 commits intomainfrom
changeset-release/main

Conversation

@github-actions
Copy link
Copy Markdown
Contributor

@github-actions github-actions bot commented Apr 17, 2026

Summary

1 new feature, 9 improvements, 4 bug fixes.

Improvements

  • Truncate large error stacks and messages to prevent OOM crashes. Stack traces are capped at 50 frames (keeping top 5 + bottom 45 with an omission notice), individual stack lines at 1024 chars, and error messages at 1000 chars. Applied in parseError, sanitizeError, and OTel span recording. (#3405)

Server changes

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

  • Vercel integration option to disable auto promotions (#3376)

  • Make it clear in the admin that feature flags are global and should rarely be changed. (#3408)

  • Admin worker groups API: add GET loader and expose more fields on POST. (#3390)

  • Add 60s fresh / 60s stale SWR cache to getEntitlement in platform.v3.server.ts. Eliminates a synchronous billing-service HTTP round trip on every trigger. Reuses the existing platformCache (LRU memory + Redis) pattern already used for limits and usage. Cache key is ${orgId}. Errors return a permissive { hasAccess: true } fallback (existing behavior) and are also cached to prevent thundering-herd on billing outages. (#3388)

  • Show a MicroVM badge next to the region name on the regions page. (#3407)

  • Increase default maximum project count per organization from 10 to 25 (#3409)

  • Merge execution snapshot creation into the dequeue taskRun.update transaction, reducing 2 DB commits to 1 per dequeue operation (#3395)

  • Stop creating TaskRunTag records and _TaskRunToTaskRunTag join table entries during task triggering. The denormalized runTags string array on TaskRun already stores tag names, making the M2M relation redundant write overhead. (#3369)

  • Replace the expensive DISTINCT query for task filter dropdowns with a dedicated TaskIdentifier registry table backed by Redis. Environments migrate automatically on their next deploy, with a transparent fallback to the legacy query for unmigrated environments. Also fixes duplicate dropdown entries when a task changes trigger source, and adds active/archived grouping for removed tasks. Moves BackgroundWorkerTask reads in the trigger hot path to the read replica. (#3368)

  • Batch items that hit the environment queue size limit now fast-fail without
    retries and without creating pre-failed TaskRuns. (#3352)

  • Fix Redis connection leak in realtime streams and broken abort signal propagation.

    Redis connections: Non-blocking methods (ingestData, appendPart, getLastChunkIndex) now share a single Redis connection instead of creating one per request. streamResponse still uses dedicated connections (required for XREAD BLOCK) but now tears them down immediately via disconnect() instead of graceful quit(), with a 15s inactivity fallback.

    Abort signal: request.signal is broken in Remix/Express due to a Node.js undici GC bug (Request signal isn't aborted after garbage collection nodejs/node#55428) that severs the signal chain when Remix clones the Request internally. Added getRequestAbortSignal() wired to Express res.on("close") via httpAsyncStorage, which fires reliably on client disconnect. All SSE/streaming routes updated to use it. (#3399)

  • Prevent dashboard crash (React error Fix issue with zod schemas getting serialized through loaders and causing errors #31) when span accessory item text is not a string. Filters out malformed accessory items in SpanCodePathAccessory instead of passing objects to React as children. (#3400)

  • Upgrade Remix packages from 2.1.0 to 2.17.4 to address security vulnerabilities in React Router (#3372)

Raw changeset output

Releases

@trigger.dev/[email protected]

Patch Changes

[email protected]

Patch Changes

@trigger.dev/[email protected]

Patch Changes

  • Truncate large error stacks and messages to prevent OOM crashes. Stack traces are capped at 50 frames (keeping top 5 + bottom 45 with an omission notice), individual stack lines at 1024 chars, and error messages at 1000 chars. Applied in parseError, sanitizeError, and OTel span recording. (#3405)

@trigger.dev/[email protected]

Patch Changes

@trigger.dev/[email protected]

Patch Changes

@trigger.dev/[email protected]

Patch Changes

@trigger.dev/[email protected]

Patch Changes

@trigger.dev/[email protected]

Patch Changes

@trigger.dev/[email protected]

Patch Changes

@github-actions github-actions bot changed the title chore: release chore: release v4.4.5 Apr 17, 2026
Copy link
Copy Markdown
Contributor

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

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.

Open in Devin Review

@github-actions github-actions bot changed the title chore: release v4.4.5 chore: release Apr 17, 2026
@github-actions github-actions bot force-pushed the changeset-release/main branch from 7359fb6 to 78ff2ec Compare April 17, 2026 12:41
@github-actions github-actions bot changed the title chore: release chore: release v4.4.5 Apr 17, 2026
@github-actions github-actions bot changed the title chore: release v4.4.5 chore: release Apr 17, 2026
@github-actions github-actions bot force-pushed the changeset-release/main branch from aa6eb0c to a3ec40f Compare April 17, 2026 12:50
@github-actions github-actions bot changed the title chore: release chore: release v4.4.5 Apr 17, 2026
@github-actions github-actions bot changed the title chore: release v4.4.5 chore: release Apr 17, 2026
@github-actions github-actions bot force-pushed the changeset-release/main branch from 9ecddb5 to 394b6e0 Compare April 17, 2026 15:07
@github-actions github-actions bot changed the title chore: release chore: release v4.4.5 Apr 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants