Skip to content

feat(genvm): disable the v0.3 executor on the studio network - #1825

Merged
kp2pml30 merged 2 commits into
v0.123-devfrom
feat/studio-disable-v03
Nov 13, 2026
Merged

kp2pml30 merged 2 commits into
v0.123-devfrom
feat/studio-disable-v03

Conversation

@kp2pml30

@kp2pml30 kp2pml30 commented Nov 12, 2026 •

Copy link
Copy Markdown
Member

Delivery Context

Depends-On: genlayerlabs/genlayer-e2e#818

Hub of the set: genlayer-e2e#818 repins the v0.6 E2E contracts off the v0.3 runner this PR disables. /run-e2e and /merge go here.

Problem and Outcome

Studio runs every non-legacy contract on the v0.4 executor and keeps v0.2 only for legacy text contracts, yet its chainforks schedule still activated v0.3 and with it the v0.3-only runners (py-genlayer:babwp9t3…, py-genlayer-multi:2f6ynxqm…, py-lib-genlayer-std:z7fv8bqp…).

  • The studio network now schedules genvm/executor/v0.3 as never; cross-major calls cross between v0.2 and v0.4 only
  • GenVM is pinned to the v0.6.0-rc14 release (same commit 9b98991 as the previous feat/host-chainforks source pin), so release backend builds get an immutable tag again

Implementation and Validation

  • Major-0 resolution already picked v0.4 over v0.3; the visible effects are that re:^v0\.3\. selectors no longer resolve and v0.3-only runners become unavailable.
  • No studio test or example contract references a v0.3-only runner (test(genvm): Pin test contracts to the v0.4 runners ✅ #1823 moved them to v0.4)
  • Unit tests: 1871 passed; test_release_backend_builds_use_an_immutable_genvm_release is green again with the release pin
  • Cross-major v0.4 ↔ v0.2 coverage: tests/integration/test_deploy_reroute_to.py in backend CI

Studio runs v0.4 for every contract and keeps v0.2 only for legacy text contracts, so v0.3 and its runners are scheduled `never`. Cross-major calls now cross between v0.2 and v0.4 only.
@kp2pml30 kp2pml30 self-assigned this Nov 12, 2026
@coderabbitai

coderabbitai Bot commented Nov 12, 2026

Copy link
Copy Markdown
Contributor

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

Run configuration

  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: defaults
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: f494f963-446d-48dd-97d1-deb267eb42a5

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • Trigger review
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

@kp2pml30

Copy link
Copy Markdown
Member Author

/run-e2e all

@ci-core-e2e-runner

Copy link
Copy Markdown
Contributor

E2E status was updated. Follow the current E2E and merge checks on this PR. Detailed diagnostics are available internally.

@kp2pml30

Copy link
Copy Markdown
Member Author

/run-e2e all

@ci-core-e2e-runner

Copy link
Copy Markdown
Contributor

E2E status was updated. Follow the current E2E and merge checks on this PR. Detailed diagnostics are available internally.

@genlayerlabs genlayerlabs deleted a comment from ci-core-e2e-runner Bot Nov 13, 2026
@genlayerlabs genlayerlabs deleted a comment from ci-core-e2e-runner Bot Nov 13, 2026
@kp2pml30
kp2pml30 merged commit ef5cd27 into v0.123-dev Nov 13, 2026
25 checks passed
@kp2pml30
kp2pml30 deleted the feat/studio-disable-v03 branch November 13, 2026 08:30
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