Skip to content

fix(provider): resolve OPY releases through R2 - #287

Draft
Teakowa wants to merge 2 commits into
mainfrom
codex/issue-286-provider-r2
Draft

fix(provider): resolve OPY releases through R2#287
Teakowa wants to merge 2 commits into
mainfrom
codex/issue-286-provider-r2

Conversation

@Teakowa

@Teakowa Teakowa commented Sep 8, 2026

Copy link
Copy Markdown
Contributor

Summary

  • resolve the current first-party OPY provider version from releases.wrightkit.dev/opy-rs/latest/version
  • download provider archives/checksums only from immutable opy-rs/releases/<version>/... paths
  • update the existing local provider regression server so wrong R2 path shapes return 404 instead of silently passing

Verification

  • existing offline reuse and failed-integrity preservation behavior remains unchanged
  • R2-shaped clean-bootstrap and Windows provider tests require exactly one latest pointer request plus archive/checksum requests under /opy-rs/releases/
  • ablation: restoring either the GitHub JSON parser or /v<version>/ artifact path causes the R2-shaped regression server to fail

Dependency

Blocked on wrightkit/opy-rs#229 / PR #230 publishing the owner-side opy-rs/latest/version contract. Production clean-bootstrap smoke should remain red until that pointer exists; do not bypass it with a test-only provider injection.

Fixes #286

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Development

Successfully merging this pull request may close these issues.

Resolve first-party OPY provider releases through R2

1 participant