Skip to content

0.40.3 — slow Seedance 2.5 jobs finish, and the poll budget stays inside its authorization - #112

Merged
VickyXAI merged 1 commit into
mainfrom
release/0.40.3
Aug 28, 2026
Merged

VickyXAI merged 1 commit into
mainfrom
release/0.40.3

Conversation

@VickyXAI

Copy link
Copy Markdown
Contributor

Release 0.40.3. Ships the two video polling fixes already on main (#110, #111) — this PR only bumps the version and writes the changelog, which is what wakes publish.yml.

What users get

blockrun_video no longer gives up on slow Seedance 2.5 jobs. Production 30s clips measured 479s, 400s and 275s against a 300s client-side cap, so two of three failed on a limit that had nothing to do with the gateway. Budget is now 540s.

The follow-up matters as much: a 540s budget under a 600s payment authorization only looks like it leaves a minute of margin. The deadline check bounds when a poll may start, not when it finishes, so the 5s interval plus the 90s poll timeout pushed the last poll to 635s — 35s past validBefore. Settlement happens server-side on the completed poll, so that tail would fail settlement for a video that actually rendered. The loop now clamps its last poll to the remaining budget, pinning worst-case wall time at exactly 540s.

Scope

Version + changelog only. No source changes — src/ landed in #110 and #111.

Deliberately excluded: the in-progress keychain / wallet work in the local tree. That's unrelated to this fix and unreviewed, so it isn't riding along.

Validation

npm run build, npm run typecheck, npm test (343 passed) all clean on this branch — the same gate publish.yml runs before publishing.

After merge

publish.yml fires on the package.json change and handles all four targets: npm publish, MCP registry (mcp-publisher), v0.40.3 tag, and the GitHub release. Each is independently version-gated, so a partial re-run is safe.

@VickyXAI
VickyXAI merged commit f80b287 into main Aug 28, 2026
1 check passed
@VickyXAI
VickyXAI deleted the release/0.40.3 branch August 28, 2026 04:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants