# wasmCloud wash-v0.42.0

2025-05-30 · [Original release notes](https://github.com/wasmCloud/wasmCloud/releases/tag/wash-v0.42.0) · [Full summary](https://ratatosk.io/en/releases/wasmcloud/wash-v0.42.0)

Breaking changes 3 · Enhancements 2 · Dependency updates 1 · Other changes 2

## Breaking changes (3)

### `wash call` now uses context RPC settings

- Affects: component calls using a named or default context in `wash call`

Previously, established contexts were ignored during component calls, so `wash call` could use its default RPC host and port and silently reach a different valid endpoint. It now uses the loaded context’s RPC and authentication settings for values not explicitly overridden, locates contexts with `--context-dir`, and returns an error if a context cannot be derived or loaded.

Evidence: “This commit allows wash call to use established context (e.g. set up with `wash ctx`) when performing component calls.” https://github.com/wasmCloud/wasmCloud/pull/4502

> ### Bug Fixes 🐞
> * fix(wash): use context during wash call by @vados-cosmonic in https://github.com/wasmCloud/wasmCloud/pull/4502

### `wash dev` no longer flattens `WadmOpts`

- Affects: the `wadm_manifest` option in `WadmOpts` used with `wash dev` (Inferred)

When it starts the host, `wash dev` sets `wadm_manifest` to `None` and explicitly passes `wadm_version`, `disable_wadm`, and `wadm_js_domain`.

> * fix(wash): dev manifest option by @vados-cosmonic in https://github.com/wasmCloud/wasmCloud/pull/4347

### Newer-release checks in `wash`

- Affects: runs of `wash` with `cli.experimental` enabled

When a newer GitHub release is available, `wash` prints an informational message to stderr. If the check fails, it prints an error and exits with status 2.

Evidence: “if cli.experimental { + if let Err(e) = inform_new_wash_version().await { + eprintln!("Error while checking for new wash version: {e}"); + std::process::exit(2); + } + }” https://github.com/wasmCloud/wasmCloud/pull/4425

> * feat(wash): add information when new version is available by @f4z3r in https://github.com/wasmCloud/wasmCloud/pull/4425

## Enhancements (2)

- `wadm_component_name` accepted in `wash dev` manifests
- Configurable generated links in `wash dev` overrides (To use: A `wash dev` override with `link_config` or its `link_configs` alias)

## Dependency updates (1)

1 more, none mentioning security

- `* chore: Bump nats-server version to 2.11.3 by @joonas in https://github.com/wasmCloud/wasmCloud/pull/4452`

## Other changes (2)

- wash artifact filename fallback now uses `next_back()`
- wash now defaults to wasmCloud host `v1.8.0`

---

Summaries are produced by AI, so they can be wrong, and they are provided without warranty.
