Repository navigation
docs: GenVM version lines on Studio v0.123 and v0.2 to v0.3 migration - #880
Draft
danieljrc888 wants to merge 2 commits into
Draft
danieljrc888 wants to merge 2 commits into
danieljrc888 wants to merge 2 commits into
Conversation
Contributor
|
Important Draft PR not reviewedDraft PRs are not automatically reviewed by default.
To automatically review draft PRs, update your CodeRabbit configuration: reviews:
auto_review:
drafts: true
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. |
✅ Deploy Preview for genlayer-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
This branch has not been deployed
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.
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
pages/developers/genvm-version-lines.mdx, in the nav after "Consensus v0.6 Migration":gl.storage.Rootlayout), with a warning against using the upgradability mechanism to cross lines.backend/node/genvm/executor_selection.pyin #1822): a first-line# v0.2.xheader (#,//,--), or a runner spec (ziprunner.json, else the leading comment block) whoseDependsnames a runner only v0.2 ships. A leading version line such as# v0.1.0is skipped when readingDepends. Aliases and unknown hashes go to the newest line. Same rules for fee estimates, schema reads and contract-deployed children. Three examples.py-genlayer:babwp9t3...(v0.3.0-rc11 changelog), test, deploy at a new address, move state, repoint clients, retire the old contract.runner malformed: causes and fixes table.consensus-v06-migration.mdx: short "GenVM v0.2 and v0.3" section and a checklist item linking the new page.Checks
@mdx-js/mdxcompiles both pages.scripts/lint-code-examples.py: all 99 snippets parse; no new issues.check-protocol-docsandcheck-v06-release-docspass.Coordination with open PRs
# v0.3.0withpy-genlayer:9b8kjyda...andpy-lib-genlayer-embeddings:kr2rb2dc.... Neither hash is in the v0.3.0-rc11 changelog (current:py-genlayer:babwp9t3...,py-lib-genlayer-embeddings:hqpree1t...). Under the rules on this page an unknown hash goes to the newest line, which rejects it withrunner malformed. Worth flagging on docs: fix Vector Store / embeddings API docs #449 rather than fixing here.gl.vm.UserError): no overlap.Other stale spots (fix separately, not in this PR)
pages/developers/intelligent-contracts/first-contract.mdxlines 11-16: "Version Comment" presents the v0.2py-genlayer:1jb45aa8...hash as the one to use.py-genlayer:1jb45aa8...(20 occurrences acrossstorage.mdx,introduction.mdx,first-intelligent-contract.mdx,features/debugging.mdx,features/vector-storage.mdx,features/upgradability.mdxandexamples/*.mdx). They deploy on v0.2 during the window and will fail once v0.2 deploys close.pages/developers/intelligent-contracts/features/upgradability.mdxlines 34-35: example header# v0.1.0+ v0.2 hash.genlayerlabs/skills:plugins/genlayer-dev/skills/write-contract/SKILL.mdline 24 (v0.2 hash) andplugins/genlayer-dev/skills/genvm-lint/SKILL.mdline 79 (genvm-lint download --version v0.2.12).genlayerlabs/genlayer-project-boilerplate:contracts/football_bets.pyline 1 (v0.2 hash).Open questions for review
# v0.2.xheader is required.babwp9t3...) or replaced with the stable v0.3.0 hash on promotion day?