chore(deps): bump tsdown from 0.22.12 to 0.22.14

[dependabot]

Bumps tsdown from 0.22.12 to 0.22.14.

Release notes

Sourced from tsdown's releases.

v0.22.14

   🚀 Features

• Add CLI build concurrency option  -  by @​sxzz and Jeroen Zwartepoorte (8a14c)

    View changes on GitHub

v0.22.13

   🚀 Features

• deps: Support neverBundle: true to externalize all dependencies  -  by @​sxzz (d30a7)

   🐞 Bug Fixes

• Prevent tinyexec from modifying PATH  -  by @​sxzz (d84c5)

    View changes on GitHub

Commits

• ff3bdbd chore: release v0.22.14
• 8a14c35 feat: add CLI build concurrency option
• 0525465 docs: add note about cjsDefault only applying to explicit entry modules
• a3a3551 refactor: fix lint
• 3dec506 refactor: use native Promise.withResolvers
• e0266c1 docs: add tsdown users image
• a733505 refactor: upgrade verkit, simplify version parse
• e5fe2ca style: format
• 3e1fc63 chore: release v0.22.13
• a6c8734 chore: upgrade deps
• Additional commits viewable in compare view

[alexpate]

Holding this for now. tsdown 0.22.14 calls Promise.withResolvers (Node 22+), so it cannot run on Node 20 — matrix (20) fails at pnpm build.

Note this is not a regression in this bump: both 0.22.12 and 0.22.14 already declare engines: { node: "^22.18.0 || >=24.11.0" }. Node 20 was never supported upstream; 0.22.14 just started actually using a Node 22 API.

Skipping the matrix job's pnpm build step alone would not fix it — turbo.json has test.dependsOn: ["build"], so pnpm test re-triggers tsdown on Node 20 anyway.

Unblocking this needs one of:

• dropping test.dependsOn: ["build"] (tests import from src/, never dist/, so Node 20 coverage does not need a build), or
• dropping Node 20 from the matrix and raising engines to >=22 (Node 20 reached EOL in April 2026).

Deferred pending a decision on whether to keep claiming Node 20 support.

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.