[github-actions]

Release the worker-recovery and timer delivery fixes from #15 and #25.

Existing SQL stores must apply 0001_fair_timer_claims.sql before upgrading the runtime, or run ensureSchema() during deployment. Custom stores must implement fair timer claims and ownership-checked timer lease release. Delivery callers should handle the new version-mismatch result and retry after the required workflow version is available.

AI review notes:
Regenerated the release with Changesets from current main, preserving the existing release branch history through a normal merge and commit. This avoids the release action's force-push, which repository rules reject.
Versions: core0.0.5, runtime0.0.4, Cloudflare0.0.4, Railway0.0.4, Netlify0.0.5, Vercel0.0.5, D1store0.0.5, Postgresstore0.0.6.
The diff against main contains only version bumps, changelogs and consumed changesets. Local test:ci passed all10projects. CI is pending on b2e4d5e. Publication and downloaded npm artifact verification follow this PR's merge, issue23 stays open until then.

[mandrews]

@tannerlinsley would you be able to merge this release? We're evaluating
TanStack Workflow for durable, human-in-the-loop runs on Postgres, and the
expired-run recovery and lease heartbeats from #15 are what make it usable for
us: on the published core 0.0.4 / runtime 0.0.3, a process that dies mid-step
leaves the run in running with nothing able to resume it. We built main
(b928717) locally and confirmed sweep() recovers the run and the heartbeat
keeps a long step from being reclaimed. A published 0.0.5 / 0.0.4 would let us
pin to npm instead of a git SHA. Thanks!

[mandrews]

Hi @tannerlinsley — would you be able to merge this release? The expired-run recovery and lease heartbeats from #15 are what make durable human-in-the-loop runs usable on Postgres; on the published core 0.0.4 / runtime 0.0.3 a process that dies mid-step leaves the run stuck in running. Details and a minimal repro in #23. A published 0.0.5 / 0.0.4 would let us pin to npm instead of a git SHA. Thanks!

[coderabbitai]

Pre-merge checks: 2

Failed checks: 2 inconclusive

Check name	Status	Explanation	Resolution
Title check		This assessment has not completed. The check will be retried on the next pre-merge check run.
Description check		This assessment has not completed. The check will be retried on the next pre-merge check run.

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

• X
• Mastodon
• Reddit
• LinkedIn

[github-actions]

🚀 Changeset Version Preview

No changeset entries found. Merging this PR will not cause a version bump for any packages.

[pkg-pr-new]

More templates

• tanstack-workflow-cloudflare-poc
• tanstack-workflow-cloudflare-d1-poc
• tanstack-workflow-netlify-poc
• tanstack-workflow-vercel-poc

@tanstack/workflow-cloudflare

npm i https://pkg.pr.new/@tanstack/workflow-cloudflare@16

@tanstack/workflow-core

npm i https://pkg.pr.new/@tanstack/workflow-core@16

@tanstack/workflow-netlify

npm i https://pkg.pr.new/@tanstack/workflow-netlify@16

@tanstack/workflow-railway

npm i https://pkg.pr.new/@tanstack/workflow-railway@16

@tanstack/workflow-runtime

npm i https://pkg.pr.new/@tanstack/workflow-runtime@16

@tanstack/workflow-store-cloudflare-d1

npm i https://pkg.pr.new/@tanstack/workflow-store-cloudflare-d1@16

@tanstack/workflow-store-drizzle-postgres

npm i https://pkg.pr.new/@tanstack/workflow-store-drizzle-postgres@16

@tanstack/workflow-vercel

npm i https://pkg.pr.new/@tanstack/workflow-vercel@16

commit: b2e4d5e