@mysten-incubation/devstack@0.8.0

Minor Changes

• 78eebac: Add suiToolsRef (and the DEVSTACK_SUI_TOOLS_REF env var) to sui() local and fork
  modes to choose the mysten/sui-tools build the validator image is based on. Fork mode uses it to
  run the sui-fork binary shipped in sui-tools (commit 892d777c onward, v1.80 release tags)
  instead of compiling it from source, turning a ten-minute first boot into an image pull. The
  default fork path is unchanged; image: { pull } and DEVSTACK_SUI_FORK_IMAGE still work for
  complete prebuilt images. Move codegen runs sui move summary in the same toolchain the stack
  publishes with; the stack-free devstack codegen verb fails when the host sui CLI is a
  different release than an explicitly pinned toolchain.

@mysten-incubation/walrus-console-mcp@0.1.0-beta.0

Minor Changes

• 3b48e5d: Initial release of the Walrus Console MCP server: bucket and file management
  against the Walrus Console API with Seal-encrypted private files, client-side
  transaction validation (owner/manager/roster pins on sponsored create-bucket
  PTBs), a path-sandboxed filesystem surface, and a guided credential installer.
  Runs against Walrus Console on mainnet by default; testnet is available via
  CONSOLE_API_BASE_URL=https://api.testnet.console.walrus.xyz.

@mysten-incubation/devstack@0.7.2

Patch Changes

• e6ebe4a: Route native Sui gRPC traffic through the devstack router over h2c while keeping grpc-web
  and JSON-RPC working on the same public RPC URL.

@mysten-incubation/devstack@0.7.1

Patch Changes

• 8119fac: Scrub Move Published.toml files from staged unpublished builds and make the Move build
  environment configurable internally.
• 8119fac: Expose dev-wallet allowed origins to the injected adapter, reject forbidden page origins
  with a browser-visible diagnostic, and allow same-stack routed app endpoints without allowing raw
  loopback origins.
• 8119fac: Preserve valid explicit MVR placeholders, make cached local package publishes adopt the
  current placeholder, and refuse live apply when the running supervisor was booted from a stale
  stack graph.

@mysten-incubation/dev-wallet@0.5.1

Patch Changes

• 8119fac: Expose dev-wallet allowed origins to the injected adapter, reject forbidden page origins
  with a browser-visible diagnostic, and allow same-stack routed app endpoints without allowing raw
  loopback origins.

@mysten-incubation/devstack@0.7.0

Minor Changes

• 03f646f: Add Walrus upload relay support.

@mysten-incubation/devstack@0.6.0

Minor Changes

• 86726c1: Start the release-provided Walrus publisher and aggregator services by default in local
  mode. Local Walrus bindings now point publisherUrl and aggregatorUrl at app-facing /v1/blobs
  service containers instead of aliasing both URLs to the first storage node.

@mysten-incubation/devstack@0.5.0

Minor Changes

• 4fc3586: Align known/live-network config with the built-in @mysten/* SDK constants, and unify
  the per-service factory ergonomics.

  • Known-network ids now come from the SDK (no drift). DeepBook's known deployments derive from
    @mysten/deepbook-v3 (testnet/mainnetPackageIds, …PythConfigs) and Walrus's from
    @mysten/walrus (TESTNET/MAINNET_WALRUS_PACKAGE_CONFIG) instead of hand-copied literals. This
    fixes a stale mainnet DeepBook packageId and means future SDK bumps flow through
    automatically. Walrus known mode now defaults systemObjectId/stakingPoolId/exchangeIds
    from the SDK, so a caller only supplies nodes.
  • Unified factory shape. Known/live networks use per-network methods across all plugins:
    deepbookFor(net).testnet()/.mainnet(),
    walrusFor(net).testnet({ nodes })/.mainnet({ nodes }),
    sealFor(net).testnet()/.mainnet(). The redundant network-in-.known({ network }) path is
    removed; .known(...)/.custom(...) are now raw-id overrides only.
  • Seal committee support. Live/fork-known modes now model both independent and decentralized
    (committee) key servers with the current Mysten object IDs. sealFor(net).testnet() resolves to
    both Mysten testnet independent servers (zero-config, no API key);
    .testnet({ server: 'committee' }) and .mainnet({ server: 'committee', apiKeyName }) select
    the committee (mainnet requires the non-secret apiKeyName — a factory-time error if missing).
    The stale seal-keyserver.testnet.mystenlabs.com URL is removed (object IDs are the source of
    truth). SealKeyServerEntry is now a true structural mirror of the SDK's KeyServerConfig
    (adds apiKeyName/apiKey), guarded by a real compile-time drift check, and verifyKeyServers
    is surfaced (defaults on for live; local-keygen keeps it off for self-signed servers).
    devstack never carries the secret committee apiKey value — the committed seal.ts and the
    world-readable deployment.json would both expose it. devstack emits only the non-secret
    apiKeyName plus the committee serverConfigs; a verbatim serverConfigs override that embeds
    an apiKey is rejected, and codegen strips any apiKey from the emitted config as
    defense-in-depth. The app injects the secret apiKey into serverConfigs at runtime (keyed by
    apiKeyName) when it constructs SealClient.

@mysten-incubation/devstack@0.4.0

Minor Changes

• efa3ab6: Multi-network deployment config.

  • devstack: renamed the persisted id-config/ids layer to deployment
    (NetworkDeployment/DevstackDeployment, loadDeployment, dump-deployment). Added
    multi-network support — per-network service buckets via forNetwork(network), typed committed
    deployments/<net>.ts files (dump-deployment --network <net>), and a deployment envelope
    merged at the Vite layer (committed networks for a prod build, the live local stack overlaid on
    vite dev). Removed the legacy resolve*() config-runtime shims and the
    @devstack-dev/generated-extras subsystem.
  • dev-wallet: the injected dev wallet now operates across the full network set — it advertises
    every configured network as the wallet-standard chain sui:<name> (including fork/custom
    names), routes a per-network faucet, and stays registered across a dApp Kit switchNetwork.
    createDevstackAdapterFromManifest accepts an optional networks set so manifest-built
    adapters advertise the same chains.
  • create-devstack-app: templates reshaped around the deployment API and multi-network
    deployments (typed deployments/<net>.ts authoring surface, dApp Kit wired to the generated
    network set).

@mysten-incubation/dev-wallet@0.5.0

Minor Changes

• efa3ab6: Multi-network deployment config.

  • devstack: renamed the persisted id-config/ids layer to deployment
    (NetworkDeployment/DevstackDeployment, loadDeployment, dump-deployment). Added
    multi-network support — per-network service buckets via forNetwork(network), typed committed
    deployments/<net>.ts files (dump-deployment --network <net>), and a deployment envelope
    merged at the Vite layer (committed networks for a prod build, the live local stack overlaid on
    vite dev). Removed the legacy resolve*() config-runtime shims and the
    @devstack-dev/generated-extras subsystem.
  • dev-wallet: the injected dev wallet now operates across the full network set — it advertises
    every configured network as the wallet-standard chain sui:<name> (including fork/custom
    names), routes a per-network faucet, and stays registered across a dApp Kit switchNetwork.
    createDevstackAdapterFromManifest accepts an optional networks set so manifest-built
    adapters advertise the same chains.
  • create-devstack-app: templates reshaped around the deployment API and multi-network
    deployments (typed deployments/<net>.ts authoring surface, dApp Kit wired to the generated
    network set).