feat: prepare v0.19 Studio preview and RC release - #113
Merged
Conversation
|
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 configurationConfiguration used: defaults Review profile: CHILL Plan: Team Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
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. Comment |
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
Follow-up release-preparation layer on the landed Consensus v0.6 / Studio v0.123 train. There is no direct cross-repository code dependency:
studio-dev.genlayer.comand chain ID61997already identify the preview environment, whilestudio-nextremains a browser-only alias.Open PR #111 overlaps
_prepare_transactionand its tests for an unrelated gas-override feature. To keep today’s release cut small and already-qualified, this PR intentionally excludes #111 and should land first; #111 can then rebase and retainis_studio_chain(...)in its edited transaction builder.Problem and outcome
The Python SDK had no dedicated Studio-dev preset, and its Studio routing relied on the stable Studio/local chain ID
61999. A naïve61997preset would therefore have sent lifecycle, fee, simulation, and appeal operations down the deployed-Consensus path. The release automation also could not safely create an RC fromv0.19-dev: its pinned semantic-release command used an unsupported positional version, its branch config matched onlymain, missing CI was allowed, and the publish workflow did not prove tag ownership or mark GitHub prereleases.This PR:
studio_devnetfor canonical RPChttps://studio-dev.genlayer.com/api, chain ID61997, and explorerhttps://explorer-studio-dev.genlayer.com;studionetunchanged athttps://studio.genlayer.com/api, chain ID61999;vX.Y.Z-rc.Nonly throughvX.Y-devand final releases only throughvX.Y;--dry-run;Implementation and validation
uv build: source distribution and universal wheel built successfully.shellcheck scripts/release.sh,actionlint .github/workflows/publish.yml, bytecode compilation, generated-doc reproducibility, andgit diff --check: passed.scripts/release.sh --allow-major 0.19.0-rc.1was exercised against a disposable local remote with a fake green CI result. It created the expected release commit and annotatedv0.19.0-rc.1tag, pushed only to that disposable remote, and the publish guard confirmed the tag andv0.19-devhead peeled to the same commit.0.18.0; no GitHub tag or PyPI publication was created during validation.Risk and rollback
The Studio classification change preserves the behavior stable
studionetalready received through its shared61999ID while extending it to preview ID61997. Direct tests lock both preview coordinates and stable-network non-drift. RC publication is still tag-driven and PyPI-only in CI; the workflow now fails closed on an unowned or stale tag. Rollback is the three commits in this PR; no external release state exists yet.