Skip to content

Conversation

@CalvinAllen
Copy link
Contributor

Summary

  • When --version is provided with R2 credentials, the gap detector now checks R2 for existing builds and only outputs platforms that are actually missing
  • Without R2 credentials, --version still falls back to outputting all platforms (for local testing)
  • Always pass R2 credentials in the workflow, regardless of whether --version is set

This prevents unnecessary build attempts for platforms that already have binaries in R2 (e.g., Windows builds from RubyInstaller).

Test plan

  • Dispatch with version: 3.2.10 and verify Windows platforms are excluded from the matrix (since RubyInstaller builds already exist in R2)
  • Dispatch without version input and verify auto-detect still works correctly
  • Run locally with --version=3.2.10 (no R2 creds) and verify all platforms are output as fallback

Previously, --version bypassed the R2 check entirely and output all 6
platforms unconditionally. This caused unnecessary build attempts for
platforms that already have binaries in R2 (e.g., Windows via
RubyInstaller). Now --version checks R2 when credentials are available
and only outputs platforms that are actually missing.
@CalvinAllen CalvinAllen merged commit a6fa386 into main Feb 9, 2026
2 checks passed
@CalvinAllen CalvinAllen deleted the fix/ci/gap-detector-r2-check branch February 9, 2026 22:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant