Skip to content

fix(ci): pre-cache genvm v0.2.16 to bypass upstream asset rename — GHB-202#111

Merged
Gastonfoncea merged 1 commit into
mainfrom
gastonfoncea09/ghb-202-ci-python-falla-en-todos-los-prs-genvm-v030-rc0-renombro
May 21, 2026
Merged

fix(ci): pre-cache genvm v0.2.16 to bypass upstream asset rename — GHB-202#111
Gastonfoncea merged 1 commit into
mainfrom
gastonfoncea09/ghb-202-ci-python-falla-en-todos-los-prs-genvm-v030-rc0-renombro

Conversation

@Gastonfoncea
Copy link
Copy Markdown
Collaborator

Summary

  • Workaround for GHB-202: the Python CI job has been red on every PR since 2026-05-20 because genlayer-test resolves the genvm version at runtime via releases/latest, and GenLayer Labs marked v0.3.0-rc0 (which removed genvm-universal.tar.xz) as latest.
  • Pre-seeds ~/.cache/gltest-direct/ with the v0.2.16 tarball so gltest's loader picks it up before consulting GitHub.
  • 14 lines added to .github/workflows/ci.yml, no Python code changes.

Why this approach (and not the others)

  • Pinning the genlayer-test PyPI package doesn't help — the genvm version is resolved by an HTTP HEAD at runtime, not from package metadata.
  • Adapting to the new per-platform asset names (genvm-linux-amd64.tar.xz) would require patching gltest upstream; not in scope for a hotfix.
  • Pre-cache is the minimum change that flips CI back to green and is fully reversible once upstream stabilizes.

Test plan

  • CI passes on this PR — both JS/TS and Python (GenLayer contracts) should be green.
  • The new step "Pre-cache genvm v0.2.16 (GHB-202)" appears in the run log and downloads the tarball successfully.
  • After merge, the next unrelated PR should not regress the Python job.

Follow-up

  • Remove the workaround step once GenLayer Labs restores genvm-universal.tar.xz for newer releases, or once gltest learns to download platform-specific assets.

🤖 Generated with Claude Code

…B-202

GenLayer Labs published genvm v0.3.0-rc0 on 2026-05-20 and dropped the
`genvm-universal.tar.xz` asset in favor of per-platform builds. Since
`genlayer-test` resolves the genvm version at runtime via a HEAD to
`releases/latest`, every CI run since has hit 404 trying to download
the old asset path from the new release.

Pre-seeding `~/.cache/gltest-direct/` with v0.2.16 makes
`list_cached_versions()` return it before the "latest" lookup, so the
test runner uses the last known-good genvm.

Remove this step once upstream restores a universal tarball or `gltest`
gains support for platform-specific assets.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@Gastonfoncea Gastonfoncea requested a review from tomazzi14 as a code owner May 21, 2026 23:30
@vercel
Copy link
Copy Markdown

vercel Bot commented May 21, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
gh-bounty-frontend Ready Ready Preview, Comment May 21, 2026 11:32pm
ghbounty-mcp Ready Ready Preview, Comment May 21, 2026 11:32pm

@Gastonfoncea Gastonfoncea merged commit 2c12467 into main May 21, 2026
5 checks passed
@Gastonfoncea Gastonfoncea deleted the gastonfoncea09/ghb-202-ci-python-falla-en-todos-los-prs-genvm-v030-rc0-renombro branch May 21, 2026 23:35
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