Repository navigation
test(genvm): Pin test contracts to the v0.4 runners ✅ - #1823
Merged
Merged
Conversation
Contributor
|
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
|
kp2pml30
force-pushed
the
feat/genvm-create2-salted-deploys
branch
from
November 11, 2026 22:33
558019a to
dc3ab56
Compare
Base automatically changed from
feat/genvm-create2-salted-deploys
to
v0.123-dev
November 12, 2026 09:08
kp2pml30
force-pushed
the
chore/gvm-v04-runner-hashes
branch
2 times, most recently
from
November 12, 2026 09:15
1a90146 to
ce0b470
Compare
- py-genlayer: babwp9t3... -> kzybg95x... - py-genlayer-multi: 2f6ynxqm... -> ys9w7shp... - v0.1 and v0.2 pins in the legacy executor selection tests are left as they are
kp2pml30
force-pushed
the
chore/gvm-v04-runner-hashes
branch
from
November 12, 2026 10:34
ce0b470 to
4e59dd4
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Delivery Context
Related to GVM-378: follow-up that moves the test contracts to the v0.4 runners
Review layer stacked on #1821. Do not post
/mergehere; after #1821 lands, retarget this PR tov0.123-devProblem and Outcome
GenVM
v0.6.0-rc12ships executor line v0.4 next to v0.3. The test contracts still pinned the v0.3 runnersEvery test contract now pins the v0.4 runner of the same name:
py-genlayer:babwp9t3…becomespy-genlayer:kzybg95x…, andpy-genlayer-multi:2f6ynxqm…becomespy-genlayer-multi:ys9w7shp…Expected to fail integration tests at first: the studio network schedules v0.4 as
neverin the GenVM chainforks, so these contracts cannot run there until that schedule changesImplementation and Validation
py-genlayerpins and themulti_file_contractrunner.jsontest_legacy_executor_selection.pyandtest_deploy_reroute_to.py, and thepy-genlayer:latestload-test archive