chore: fast-forward main to v0.40-dev#365
Merged
Merged
Conversation
* docs: add branching guide * ci: harden testnet smoke timeout
* feat: support fee profiles in contract commands * test: make fee profile deploy test portable
* feat: add staking validators discovery * feat: epoch-aware validator listing with below-min indicator * fix(staking): account-less client for read-only staking queries getReadOnlyStakingClient threw 'Account not found' on fresh installs; listings and other reads don't need a local account.
* feat: add vesting commands * feat(vesting): validator subcommands — create/join, deposit, exit, claim, operator-transfer, set-identity, list/status Drives the CON-607 Vesting.sol validator leg through the SDK's named vestingValidator* actions; list/status enumerate getValidatorWallets with per-wallet deposited principal.
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Selecting Gemini during `genlayer init` failed with:
Requested providers '{'geminiai'}' do not match any stored providers.
The selected provider id is forwarded verbatim to
sim_createRandomValidators, but the backend's llm_provider table stores
Gemini as "google". Rename the provider id geminiai -> google so it
matches. Display name ("Gemini") and env var (GEMINI_API_KEY) are
unchanged.
Since "geminiai" never resolved to a valid provider, no working
configuration relied on it.
Fixes #271
Co-authored-by: Edgars Nemše <edgars@genlayerlabs.com>
The sync-docs workflow rsynced the generated category-based docs/api-references/_meta.json into genlayer-docs and then immediately overwrote it with a hardcoded heredoc containing the pre-grouping flat command list (init, up, deploy, ...). Those keys no longer match the directory layout, so the genlayer-docs sidebar rendered broken entries on every sync (fixed manually in genlayer-docs#426; this removes the cause). Also make the generated root meta complete: - add "index": "Overview" for the generated index.mdx - append ungrouped top-level commands (estimate-fees, finalize, finalize-batch) so they get explicit nav entries instead of relying on Nextra's implicit append Snapshot under docs/api-references regenerated against current main (picks up the new estimate-fees command and latest help text). Co-authored-by: Albert Castellana <albert@genlayer.com> Co-authored-by: Claude Fable 5 <noreply@anthropic.com> Co-authored-by: Edgars <edgars@entropicsolutions.io>
getSlashingAddress() was removed from the genlayer-js SDK (v0.39+/v2-dev), causing `genlayer staking validator-history` to crash with `client.getSlashingAddress is not a function` before any history is fetched. Resolve the idleness (slashing) contract address dynamically via viem readContract against consensusMainContract.getIdlenessAddress(), falling back to the staking contract address if resolution fails so reward events still display. Port of #344 (by @ygd58) from the dead v0.39 line to v0.40-dev. Supersedes #344. Fixes #341 Co-authored-by: Edgars <edgars@entropicsolutions.io>
) * feat(network): custom network profiles with deployment-file import genlayer network add <alias> --base <built-in> [--deployment <json>] [--rpc <url>] [--consensus-main|--consensus-data|--staking|--fee-manager |--rounds-storage|--appeals <addr>] [--chain-id <n>] [--deployment-key <path>] Profiles persist as base + address overrides only; resolveNetwork loads the base chain fresh from genlayer-js and applies overrides, so ABIs never go stale. network set/list/info/remove and StakingAction --network accept custom aliases. The consensus deployments.json shape is parsed by walking the tree for ContractName->address leaves (ConsensusMain, ConsensusData, GenStaking/Staking, FeeManager, Rounds/RoundsStorage, Appeals); flags take precedence over the file. Adds a prepare script so npm install from a git ref builds dist. Verified: 576 vitest tests, full manual smoke (add/list/set/info/remove with a deployment file). * chore(deps): bump genlayer-js to v2-dev tip for vesting actions The locked v2-dev SHA (28e99fbc) predates the vesting client actions; vestingValidatorJoin and friends land at 666d1156. Verified live: vesting validator create succeeds against a #1162-branch consensus deployment. * docs(cli): regenerate API references; fix option placeholder regex The docs generator's option regex only matched <word> placeholders, so flags with dots or hyphens in the value name (--base <built-in-alias>, --deployment <path.json>, --deployment-key <dot.path>) were silently dropped from the options tables. Widen to <[^>]+> and regenerate: adds the network add/remove pages and the previously undocumented vesting command section (validator create/deposit/exit/claim, operator-transfer, set-identity, delegate/undelegate/claim/withdraw/list). * fix(vesting): resolve validator wallet address in create output The join receipt does not carry the new wallet address, so the output printed validatorWallet: undefined. Read getValidatorWallets from the vesting contract after the join and report the newest entry. Verified live against a #1162-branch deployment.
* fix: make git install build script self contained * chore: refresh genlayer-js lockfile * fix: make keychain dependency optional * fix: restore git prepare build * fix: include build dependency for git installs * chore: keep esbuild as dev dependency
* ci: add clarke cli tarball release * ci: publish prereleases to npm dist tags
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (113)
📝 WalkthroughWalkthroughThis PR adds fee-profile support to deploy/write/estimate-fees commands, introduces custom network profile management (add/remove), adds a staking validators discovery command with explorer enrichment, and implements a full vesting CLI feature (delegator and validator operations). It also updates publish/smoke CI workflows, build scripts, and documentation. ChangesFee Profile Support
Custom Network Profiles
Staking Validators Discovery
Vesting CLI Feature
CI/Publish Workflow, Build Scripts, and Small Fixes
Estimated code review effort: 4 (Complex) | ~75 minutes Sequence Diagram(s)sequenceDiagram
participant CLI
participant ResolveTransactionFees
participant FeeProfileFile
participant GenLayerClient
CLI->>ResolveTransactionFees: deploy/write/estimate-fees(options)
ResolveTransactionFees->>FeeProfileFile: read fee-profile.json
FeeProfileFile-->>ResolveTransactionFees: profile entries
ResolveTransactionFees->>GenLayerClient: estimateTransactionFees(request)
GenLayerClient-->>ResolveTransactionFees: distribution + feeValue
ResolveTransactionFees-->>CLI: transaction fees
sequenceDiagram
participant CLI
participant ValidatorsAction
participant StakingClient
participant ExplorerAPI
CLI->>ValidatorsAction: staking validators --explorer-url
ValidatorsAction->>StakingClient: fetch validator sets + epoch info
ValidatorsAction->>ExplorerAPI: fetch performance/delegator data
ExplorerAPI-->>ValidatorsAction: merged performance metrics
ValidatorsAction-->>CLI: JSON or table output
Possibly related PRs
Suggested reviewers: ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Warning There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure. 🔧 ESLint
scripts/generate-cli-docs.mjsParsing error: "parserOptions.project" has been provided for scripts/run-esbuild.mjsParsing error: "parserOptions.project" has been provided for 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
3 participants
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.
Moves main to the current active dev branch state so default-branch tooling sees the latest workflow files.\n\nWhy now:\n- The auto fast-forward workflow cannot push to main because repo rules require PRs.\n- publish.yml prerelease safety needs to exist on the default branch before dispatching v0.40.0-rc1.\n\nThis PR is intended to be a fast-forward alias update; v0.40-dev remains the active development branch.
Summary by CodeRabbit
New Features
Bug Fixes
Documentation