Skip to content

docs: GenVM version lines on Studio v0.123 and v0.2 to v0.3 migration - #880

Draft
danieljrc888 wants to merge 2 commits into
mainfrom
docs/genvm-version-lines
Draft

danieljrc888 wants to merge 2 commits into
mainfrom
docs/genvm-version-lines

Conversation

@danieljrc888

@danieljrc888 danieljrc888 commented Nov 10, 2026 •

Copy link
Copy Markdown
Contributor

Description

Draft, do not merge. This should merge on the Studio v0.123 promotion day, after genlayerlabs/genlayer-studio#1822 (rc.12) lands. The page describes rc.12 behavior.

Nothing in the docs explains project-level GenVM migration today: sdk.genlayer.com has the API migration guide, but nothing covers which executor line a deploy lands on, what happens to deployed contracts, how to move one to v0.3, or the v0.2 deploy cutoff.

Changes

  • New page pages/developers/genvm-version-lines.mdx, in the nav after "Consensus v0.6 Migration":
    • Two lines on Studio v0.123: retained v0.2.x and newest v0.3.x. Deployed contracts stay on their line; no in-place upgrade (different gl.storage.Root layout), with a warning against using the upgradability mechanism to cross lines.
    • How Studio picks the line for a new deploy (per backend/node/genvm/executor_selection.py in #1822): a first-line # v0.2.x header (#, //, --), or a runner spec (zip runner.json, else the leading comment block) whose Depends names a runner only v0.2 ships. A leading version line such as # v0.1.0 is skipped when reading Depends. Aliases and unknown hashes go to the newest line. Same rules for fee estimates, schema reads and contract-deployed children. Three examples.
    • Migration as redeploy: port with the SDK migration guide, switch to py-genlayer:babwp9t3... (v0.3.0-rc11 changelog), test, deploy at a new address, move state, repoint clients, retire the old contract.
    • Minimal-downtime migration: parallel deploy, backfill, short write freeze for the delta, address switch; copy state instead of replaying non-deterministic writes; multi-contract ordering.
    • runner malformed: causes and fixes table.
    • v0.2 deploy window: deploys close per Studio later (date to be announced); execution of deployed v0.2 contracts never ends.
  • consensus-v06-migration.mdx: short "GenVM v0.2 and v0.3" section and a checklist item linking the new page.

Checks

  • @mdx-js/mdx compiles both pages.
  • scripts/lint-code-examples.py: all 99 snippets parse; no new issues.
  • check-protocol-docs and check-v06-release-docs pass.
  • No em or en dashes in the new text.

Coordination with open PRs

Other stale spots (fix separately, not in this PR)

  • pages/developers/intelligent-contracts/first-contract.mdx lines 11-16: "Version Comment" presents the v0.2 py-genlayer:1jb45aa8... hash as the one to use.
  • Every docs example pinning py-genlayer:1jb45aa8... (20 occurrences across storage.mdx, introduction.mdx, first-intelligent-contract.mdx, features/debugging.mdx, features/vector-storage.mdx, features/upgradability.mdx and examples/*.mdx). They deploy on v0.2 during the window and will fail once v0.2 deploys close.
  • pages/developers/intelligent-contracts/features/upgradability.mdx lines 34-35: example header # v0.1.0 + v0.2 hash.
  • genlayerlabs/skills: plugins/genlayer-dev/skills/write-contract/SKILL.md line 24 (v0.2 hash) and plugins/genlayer-dev/skills/genvm-lint/SKILL.md line 79 (genvm-lint download --version v0.2.12).
  • genlayerlabs/genlayer-project-boilerplate: contracts/football_bets.py line 1 (v0.2 hash).

Open questions for review

  1. Does rc.12 (#1822) ship in v0.123 stable as-is? If not, the "How Studio picks the line" section must say a # v0.2.x header is required.
  2. Scope: the page is Studio-only. Do Bradbury/testnets accept the same lines and pins, or need their own note?
  3. Cutoff details: will closing v0.2 deploys also block deploys made by v0.2 contracts (child deploys)? The page only says "a deploy that selects v0.2 is rejected".
  4. Should the v0.3 example hash be pinned to rc11 (babwp9t3...) or replaced with the stable v0.3.0 hash on promotion day?
  5. Is a recommended way to check which line a deploy landed on (RPC field or Studio UI) worth documenting?

@danieljrc888 danieljrc888 self-assigned this Nov 10, 2026
@coderabbitai

coderabbitai Bot commented Nov 10, 2026

Copy link
Copy Markdown
Contributor

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

  • Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true
  • 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

@netlify

netlify Bot commented Nov 10, 2026 •

Copy link
Copy Markdown

✅ Deploy Preview for genlayer-docs ready!

Name Link
🔨 Latest commit 22497dd
🔍 Latest deploy log https://app.netlify.com/projects/genlayer-docs/deploys/6af38b8299f21859367e1e65
😎 Deploy Preview https://deploy-preview-880--genlayer-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

This branch has not been deployed

No deployments
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