# Meshery v1.0.18

2026-05-05 · [Original release notes](https://github.com/meshery/meshery/releases/tag/v1.0.18) · [Full summary](https://ratatosk.io/en/releases/meshery/v1.0.18)

Breaking changes 1 · Deprecations 1 · Important fixes 3 · Enhancements 1 · Dependency updates 3 · Other changes 9

## Breaking changes (1)

### Connection payload metadata keys renamed to camelCase

- Affects: setups or integrations that read Meshery connection JSONB `metadata` fields (Inferred)

Consumers looking up `server_id`, `server_version`, `server_build_sha`, or `server_location` may find those keys absent without the payload reporting an error. New connection payloads contain `serverId`, `serverVersion`, `serverBuildSha`, and `serverLocation` instead.

Evidence: “- Phase 5c of the identifier-naming overhaul. `BuildMesheryConnectionPayload` previously emitted four snake_case literal keys (`server_id`, `server_version`, `server_build_sha`, `server_location`) into the connection's JSONB `metadata` blob, violating the canonical camelCase-wire identifier-naming contract.” https://github.com/meshery/meshery/pull/19096

> - fix(connections): emit camelCase server metadata keys in payload @leecalcote (#19096)

## Deprecations (1)

### Provider fields recognized by `mesheryctl system login`

- Affects: Meshery Server responses with provider details in `camelCase` or `snake_case` (Inferred)
- Removed in: not stated

Previously, canonical provider fields left the provider options blank in the terminal prompt. The prompt now shows those options for canonical fields, and legacy fields are still accepted.

> - [mesheryctl] Fix invisible provider options in system login @YASHMAHAKAL (#19011)

## Important fixes (3)

### [Silent failure] Relationship evaluator component styling fixed

- Affects: relationship evaluation that adds components (Inferred)

When the registry returned components as `v1beta3`, a `v1beta1` type assertion silently failed and the components rendered without styles in Kanvas. Evaluator-added components now receive styles, and their matching `add_component` action payloads are hydrated with component data.

> - fix(eval): hydrate styles on evaluator-added components @guan404ming (#19090)

### `HeaderMenu.tsx` token-error notification moved into an effect

- Affects: Meshery UI `isTokenError` handling

When `HeaderMenu.tsx` rendered with `isTokenError`, it called the notification on every render, risking repeated notifications and infinite update loops.

> - [ui] Remove React anti-patterns and TypeScript escape hatches @miacycle (#19054)

### Import Model file input restored

- Affects: Settings → Registry → Import Model File Import flow

The conditional `file` field rendered as a text widget instead of a file input, so file selection timed out and the modal's file lookup failed in normal use. The existing `CustomFileWidget` now renders a real file input and produces the expected data URL.

> - fix(ui/e2e): unblock "Import a Model via File Import" test @miacycle (#19072)

## Enhancements (1)

- Non-functional click handler removed from MeshModel service avatars

## Dependency updates (3)

3 more, none mentioning security

- `- fix(deps): pin docker/cli to v28.5.1 to match docker/compose/v2 v2.40.3 @leecalcote (#19082)`
- `- Bump Docker extension UI’s transitive Rollup to 2.80.0 @[copilot-swe-agent[bot]](https://github.com/apps/copilot-swe-agent) (#19009)`
- `- chore(deps): Bump github.com/docker/cli from 28.5.1+incompatible to 29.4.2+incompatible @[dependabot[bot]](https://github.com/apps/dependabot) (#19046)`

## Other changes (9)

- README project structure section removed
- Clearer design error notifications
- Local-directory walking error renamed to `ErrWalkingLocalDirectory`
- Meshery UI structural cleanup
- Kubernetes context subscription cleanup now disposes correctly
- KubernetesSubscription subscribe/dispose function moved into effect
- Resources Table `clusterIds` double-encoding fixed
- Kanvas documentation removed from extensions
- Documentation for `x-annotations` schema extensibility in remote providers

---

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