Skip to content

release: 0.7.4 — correct the 0.7.2 n-bound claim (docs only)#25

Merged
VickyXAI merged 1 commit into
mainfrom
release/0.7.4
Jul 16, 2026
Merged

release: 0.7.4 — correct the 0.7.2 n-bound claim (docs only)#25
VickyXAI merged 1 commit into
mainfrom
release/0.7.4

Conversation

@VickyXAI

Copy link
Copy Markdown
Contributor

Documentation only. Runtime code is byte-identical to 0.7.3 — released so the corrected record ships with the package instead of sitting unreleased on main.

0.7.2's changelog claimed an out-of-range n "took payment, then 400'd at the provider and lost the prepaid USDC". That is false. BlockRun's gateways settle on success, so a request that dies at the provider settles nothing.

Verified on every path this time, including the async one I hadn't checked: the poll endpoint answers payment_status: "not_charged""Upstream generation failed. No payment was taken." — for failed jobs, and settlePaymentWithRetry only ever runs in the completed branch.

The n bound stays; it just was never about money. Root cause was the SDK's "API error after payment" wording (fixed in BlockRunAI/blockrun-llm#25).

277 tests pass; version consistency guard green.

@VickyXAI
VickyXAI merged commit a00a000 into main Jul 16, 2026
@VickyXAI
VickyXAI deleted the release/0.7.4 branch July 16, 2026 05:33
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.

1 participant