Vouch please: how to become a contributor

[matt-aitken]

Want to contribute to Trigger.dev? Request a vouch by leaving a comment below before opening your first pull request. PRs from unvouched contributors are automatically closed.

Important: Because Trigger.dev is production infrastructure, every external change needs a security review and verification by our team. Your vouch request is extremely unlikely to be accepted unless you are already known to the Trigger.dev team in some way, either as a customer or self-hoster or some other reason we’d be familiar with your work.

We really appreciate bug reports or feature requests. A good reproduction always gets fixed faster than a PR would get merged. You can even suggest the architecture of the fix in the bug report under "Suggested fix".

Please include:

• What you’d like to work on, with a link to the issue if there is one.
• A little about your background, with links to relevant projects or previous contributions if available.

A maintainer will review your request and let you know once you’ve been added to the vouched contributors list. Please don’t open a separate issue or discussion to request a vouch.

Once approved, follow our contributing guidelines and open your PR as a draft first.

Being vouched lets you submit PRs; it does not guarantee that a particular change will be accepted.

[61465]

Hi — would like to request vouching so I can open a PR for an existing issue.

What I'd like to work on:
#4819 — batchTrigger returns stale failed runs as isCached: true instead of re-triggering when the idempotency key points to a dead run. The single-trigger path handles this correctly via shouldIdempotencyKeyBeCleared; the batch path at batchTriggerV3.server.ts:450 was missing the status check because PostgresRunStore.findRunsByIdempotencyKeys never selected the status column.

I already wrote the fix as a courtesy draft before realising the vouching workflow — PR #5014 (auto-closed by check-vouch). It's 4 files: adds status to the SQL + IdempotencyKeyRunMatch type, imports shouldIdempotencyKeyBeCleared into #prepareRunData, and adds a postgres regression test covering PENDING / CRASHED / COMPLETED_WITH_ERRORS / COMPLETED_SUCCESSFULLY. Full credit to the reporter @Jaimin2687 for the RCA. Happy to re-open as a draft once vouched, or to abandon it entirely if you'd prefer the fix to come from the team.

Background:

• Prior contribution to this repo: GHSA-65rr-73jq-6qhf — accepted by @crofty on 2026-10-07.
• Other recent OSS work: PostHog #5083 (merged), Supabase storage #1488 / #1499 / #1500, Supabase auth #2863.
• GitHub: @61465.

Thanks for considering.