Skip to content

Contributions

19 PRs merged across 8 upstream repos. Plus a public patches repo with drop-in fixes shipped before merge in Bun, npm, pnpm, and Yarn formats. The workflow: find the bug, file the upstream PR, drop the patch into the repo so my projects (and anyone else hitting the same thing) can ship without waiting. When the fix lands in a release, I bump the dep and delete the patch. Every merged PR listed here shipped as a patch first.

Merged PRs

Patches

Open (PRs still awaiting upstream merge):

Released (PR merged; patch either still active until the next release, already dropped, or tracked without a local patch file):

Active, awaiting next release:

Dropped after release (detailed descriptions in the Merged PRs section above):

No patch, tracked in the patches repo for completeness because the upstream change can’t be applied locally: napi-rs/napi-rs#3189 (CLI bundles to dist), shadcn-ui/ui#9331 (docs site JSON), App-Store-Connect-CLI#784 (Swift binary), TanStack/db#17 (README only).

Closed (patches dropped after upstream fixed the underlying issue a different way, or docs-only PRs I closed myself):

Issues I filed upstream

- Ray