You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
bug: kit e and kit f should allow any historical version #410
Describe the bug kit e and kit f populate only the most recent versions for use. Instead they should display only the most recent versions, but allow any valid version.
$ kit e --help
Boot a real node
Usage: kit boot-real-node [OPTIONS] --home <HOME> [-- <ARGS>...]
Arguments:
[ARGS]... Additional arguments to pass to the node (i.e. to Hyperdrive)
Options:
-r, --runtime-path <PATH> Path to Hyperdrive repo (overrides --version)
-v, --version <VERSION> Version of Hyperdrive to use (overridden by --runtime-path) [default: latest] [possible values: latest, v1.9.0, v1.8.2, v1.8.1]
-p, --port <NODE_PORT> The port to run the real node on [default: 8080]
-o, --home <HOME> Path to home directory for real node
--rpc <RPC_ENDPOINT> Ethereum Base mainnet RPC endpoint (wss://)
--release If set and given --runtime-path, compile release build [default: debug build]
--verbosity <VERBOSITY> Verbosity of node: higher is more verbose [default: 0]
-h, --help Print help
Activity