Skip to content

test(genvm): Pin test contracts to the v0.4 runners ✅ - #1823

Merged
kp2pml30 merged 1 commit into
v0.123-devfrom
chore/gvm-v04-runner-hashes
Nov 12, 2026
Merged

kp2pml30 merged 1 commit into
v0.123-devfrom
chore/gvm-v04-runner-hashes

Conversation

@kp2pml30

Copy link
Copy Markdown
Member

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 /merge here; after #1821 lands, retarget this PR to v0.123-dev

Problem and Outcome

GenVM v0.6.0-rc12 ships executor line v0.4 next to v0.3. The test contracts still pinned the v0.3 runners

Every test contract now pins the v0.4 runner of the same name: py-genlayer:babwp9t3… becomes py-genlayer:kzybg95x…, and py-genlayer-multi:2f6ynxqm… becomes py-genlayer-multi:ys9w7shp…

Expected to fail integration tests at first: the studio network schedules v0.4 as never in the GenVM chainforks, so these contracts cannot run there until that schedule changes

Implementation and Validation

  • 37 py-genlayer pins and the multi_file_contract runner.json
  • Left alone on purpose: the legacy v0.1/v0.2 pins in test_legacy_executor_selection.py and test_deploy_reroute_to.py, and the py-genlayer:latest load-test archive

@kp2pml30 kp2pml30 self-assigned this Nov 11, 2026
@coderabbitai

coderabbitai Bot commented Nov 11, 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: 22cb8101-f773-42de-aba1-13519928a4fb

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
kp2pml30 force-pushed the feat/genvm-create2-salted-deploys branch from 558019a to dc3ab56 Compare November 11, 2026 22:33
Base automatically changed from feat/genvm-create2-salted-deploys to v0.123-dev November 12, 2026 09:08
@kp2pml30
kp2pml30 force-pushed the chore/gvm-v04-runner-hashes branch 2 times, most recently from 1a90146 to ce0b470 Compare November 12, 2026 09:15
- 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
kp2pml30 force-pushed the chore/gvm-v04-runner-hashes branch from ce0b470 to 4e59dd4 Compare November 12, 2026 10:34
@kp2pml30
kp2pml30 merged commit 29b89bb into v0.123-dev Nov 12, 2026
20 of 21 checks passed
@kp2pml30
kp2pml30 deleted the chore/gvm-v04-runner-hashes branch November 12, 2026 11:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant