Skip to content

ci: retry transient pinned tool downloads - #288

Merged
ael-dev3 merged 1 commit into
mainfrom
codex/0.4-retry-pinned-download-20260917
Sep 17, 2026
Merged

ael-dev3 merged 1 commit into
mainfrom
codex/0.4-retry-pinned-download-20260917

Conversation

@ael-dev3

Copy link
Copy Markdown
Owner

Problem

The post-merge Verify run for 255744e1d5e9bcebf88f483baff03d084916570e failed in spacetimedb-module before verification because the pinned CLI download ended with curl: (35) Recv failure: Connection reset by peer.

Change

  • retry pinned release downloads on all curl transient errors with a bounded delay
  • apply the same behavior to Verify and Pages paths
  • keep checksum validation and pinned versions unchanged

No runtime, game, data, or asset behavior changes.

Local validation

  • npm test -- tests/workflowSecurity.test.ts (18/18)

@ael-dev3
ael-dev3 force-pushed the codex/0.4-retry-pinned-download-20260917 branch from fe6b997 to 5f6d61d Compare September 17, 2026 18:56
@ael-dev3
ael-dev3 merged commit b4e1e0d into main Sep 17, 2026
8 checks passed
@ael-dev3
ael-dev3 deleted the codex/0.4-retry-pinned-download-20260917 branch September 17, 2026 19:50
ael-dev3 added a commit that referenced this pull request Sep 17, 2026
## Problem\nActive 0.4 handoff and release notes still pointed agents at
historical checkpoint 9d9328d and stale CI receipts.\n\n## Change\n-
Align nine active source, evidence, and operations docs to the last
runtime-bearing protected checkpoint b4e1e0d.\n- Record Verify
35267250826, CodeQL 35267250817, Pages classifier 35272164921, and the
PR #288 retry-all-errors fix with Verify 35261832713.\n- Preserve
historical source families and clearly separate moving documentation
commits from the runtime source.\n\n## Validation\n- npm test --
tests/desktopHandoff.test.ts tests/visualFoundationContract.test.ts
tests/workflowSecurity.test.ts (26/26)\n- git diff --check\n-
Documentation-only; no runtime, asset, provider, or deployment behavior
changes.
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