Repository navigation
feat(genvm): disable the v0.3 executor on the studio network - #1825
Conversation
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.
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the
|
|
/run-e2e all |
|
E2E status was updated. Follow the current E2E and merge checks on this PR. Detailed diagnostics are available internally. |
|
/run-e2e all |
|
E2E status was updated. Follow the current E2E and merge checks on this PR. Detailed diagnostics are available internally. |
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-e2eand/mergego 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…).studionetwork now schedulesgenvm/executor/v0.3asnever; cross-major calls cross between v0.2 and v0.4 onlyv0.6.0-rc14release (same commit9b98991as the previousfeat/host-chainforkssource pin), so release backend builds get an immutable tag againImplementation and Validation
re:^v0\.3\.selectors no longer resolve and v0.3-only runners become unavailable.test_release_backend_builds_use_an_immutable_genvm_releaseis green again with the release pintests/integration/test_deploy_reroute_to.pyin backend CI