[waleedlatif1]

Summary

• Drop the four temporary Trigger.dev entries from minimumReleaseAgeExcludes in bunfig.toml; the 4.8.3 packages they let through early have now cleared the 7-day release-age gate
• Trigger.dev installs are back under the same supply-chain gate as every other dependency; only the Next.js pins stay exempt

Type of Change

• Chore

Testing

• bun install --frozen-lockfile passes with no lockfile change
• bunx trigger.dev@4.8.3 --version resolves (the CLI version CI uses to deploy and promote)
• Lint, audits, type-check, and tests run in CI

Checklist

• Code follows project style guidelines
• Self-reviewed my changes
• Tests added/updated and passing (new tests pass the test-audit authoring gate)
• No new warnings introduced
• I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
docs	Building	Preview	Nov 9, 2026 10:04pm UTC

[cubic-dev-ai]

No issues found across 1 file

Confidence score: 5/5

• Automated review surfaced no issues in the provided summaries.
• No files require special attention.

_{Turn on auto-fix | Re-trigger cubic}

[greptile-apps]

Confidence Score: 5/5

[Medium impact] This change appears safe to merge.

Summary

Removes the four temporary Trigger.dev entries from minimumReleaseAgeExcludes in bunfig.toml and deletes their expired explanation.

• Trigger.dev packages now follow the seven-day release-age check.

_{Reviews (1) · Last reviewed commit: "chore(deps): drop the expired Trigger.de..." · Reviewed by Greptile}