Repository navigation
Conversation
… only for the workspace template odra-wasm-client's build script no longer panics when WASM_CLIENT_SK is unset: the key is empty and signing fails with a clear error, so a workspace-wide cargo clippy needs no secret; the lint job also exports the key like the other jobs. cargo odra generate-client only supports workspace projects (cargo-odra #104), so the template recipe runs it for the workspace template only. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
…odule cfg (#617, #321) An Odra.toml entry whose first segment is a crate (fqn = "odra_modules::erc20::Erc20") builds that crate's contract from the current project: ODRA_MODULE reaches every Odra crate's build script, and the no_mangle entry points of a dependency link into the host's build binary. The examples build Erc20 and Cep18 this way instead of copying them from modules/wasm. The wasm parts are gated by cfg(any(odra_module = "Struct", odra_module = "crate::Struct")) so cargo odra can pass the crate-qualified name and same-named structs in two crates no longer clash; odra_build::schema names the file from the struct part. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
…aries Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Closed
Contributor
Author
|
Closing: the 3.0.0 party goes back to a single pull request, #664. The commits here are the same work, so nothing is lost. |
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.
Layer 6 of 6 of the 3.0.0 party stack (bottom-up: 1 → 2 → 3 → 4 → 5 → 6, bottom is #668). Each layer targets the branch below; merge from the bottom. The top of the stack is the tree verified on OdraVM, CasperVM and NCTL; docs are in odradev/odradev.github.io#58 and #59, the migration guide covers every breaking change.
Closes #617, closes #321. Supersedes #664, which carried the whole party as one PR; the history here is the same commits, linearized (the two merges of
release/3.0.0dropped, the tree is identical).fqn = "odra_modules::erc20::Erc20"inOdra.tomlbuilds that crate's wasm and schema from the current project; the examples buildErc20/Cep18this way instead of copying them. The wasm parts are gated bycfg(any(odra_module = "Struct", odra_module = "crate::Struct"))and cargo-odra (Contracts from dependency crates and crate-qualified ODRA_MODULE cargo-odra#105) passes the qualified form, so same-named structs in two crates no longer clash (Allow for building wasms from other repos. #617, Allow for transitive modules usingmodule_path!macro. #321).WASM_CLIENT_SKandodra-wasm-clientbuilds without it;generate-clientruns only for the workspace template (cargo-odra#104).Verification of the whole stack
Workspace clippy
-D warningsand fmt; unit tests of every crate;odra-modulesandexamplessuites on OdraVM and CasperVM;just test-livenetend to end on NCTL (livenet_tests, validators, upgrade, and the CLI deploy plus every scenario). All CI jobs green on the pre-stack branch.🤖 Generated with Claude Code