# Meshery v1.0.19

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

Breaking changes 4 · Important fixes 4 · Dependency updates 7 · Other changes 20

## Breaking changes (4)

### Typed `v1alpha3` relationship conversion in the Go policy engine

- Affects: Go policy engine conversion of registered `v1alpha3` relationships and other relationship values

Previously, relationship values without a matching type case went through a generic JSON marshal/unmarshal fallback. Now `v1alpha3` values and pointers use `RelationshipV1alpha3ToV1beta2`, while values reaching the default case are skipped without an error.

Evidence: “- add a typed v1alpha3-to-v1beta2 relationship bridge for the Go policy engine” https://github.com/meshery/meshery/pull/19100

> - [Server] Replace JSON schema-version bridges with typed copies @ritzorama (#19100)

### `event_trackers.metadata` keys changed to camelCase

- Affects: consumers of affected metadata keys in `event_trackers.metadata`
- Action required: No backfill migration is needed.

Affected handlers previously emitted keys such as `connection_id`, `view_link`, `design_name`, and `design_id`; new event rows use camelCase keys instead. Existing rows retain their legacy keys, and the `?design_id=` URL query parameter is unchanged.

Evidence: “`event_trackers` is an append-only audit log, so no backfill migration is needed. Old rows remain under their legacy keys as historical records; new rows comply going forward.” https://github.com/meshery/meshery/pull/19099

> - fix(events): flip event metadata keys to canonical camelCase @leecalcote (#19099)

### `mesheryctl workspace` switches to the `v1beta3` model

- Affects: `mesheryctl workspace create`, `mesheryctl workspace list`, and `mesheryctl workspace view` (Inferred)

Before this release, these commands used the `v1beta1` workspace model, with fields such as `organization_id` and `created_at`. After upgrading, their workspace data uses the `v1beta3` model and camelCase names such as `organizationId` and `createdAt`.

> - [mesheryctl] Align mesheryctl workspace with v1beta3 @PragalvaXFREZ (#19020)

### Meshery UI build moves to Node 22

- Affects: setups that build the Meshery UI or use its Node package or Docker build base (Inferred)

The UI package previously accepted Node 20, the Docker build used `node:20-alpine`, and contributor documentation specified Node 20 LTS. Now the package requires Node `^22.13.0 || >=24`, the Docker build uses `node:22-alpine`, and the documentation specifies Node 22 LTS.

> - Chore: Upgrade to Node 22 and React 19 @leecalcote (#19083)
> - Chore: Upgrade to Node 22 and React 19 @leecalcote (#19083)
> - Chore: Upgrade to Node 22 and React 19 @leecalcote (#19083)

## Important fixes (4)

### Meshery login redirects preserve requested in-app paths

- Affects: Meshery login flows with in-app destinations, including `InitiateLogin` and legacy `?ref=` callers

Previously, if an intermediate provider hop dropped or rewrote `ref`, users could land on Meshery’s nonexistent `/login` route and get a 404. `InitiateLogin` now saves the requested path in `RefCookieName` for `TokenHandler` to use before falling back to `?ref=` and `/`, then clears the cookie after use.

> - fix(auth): own post-login redirect locally in Meshery via cookie @leecalcote (#19119)

### Empty-slice handling fixed in `mesheryctl perf` profile paths

- Affects: profiles with empty `loadGenerators` or endpoint slices used by `mesheryctl perf`

When `mesheryctl perf result` formatted a profile with no `loadGenerators`, it could panic; adjacent paths also indexed the first endpoint or load generator directly. The affected lookups now return an empty string for empty slices.

> - [mesheryctl] Fix perf result panic on empty load generators @leecalcote (#19122)

### `ConnectionStateChip` menu-context runtime error fixed

- Affects: Meshery UI connections flows that render `ConnectionStateChip` outside a menu context

Outside menu contexts, wrapping the status chips in `MenuItem` caused invalid nesting and a `MenuListContext` runtime error. The error no longer occurs, and chip labels, icons, and colors remain unchanged.

> - fix: /management/connections MUI  MenuList issue @saurabhraghuvanshii (#19132)

### Meshery event-bus payload keys fixed to camelCase

- Affects: Setups using Meshery's event-bus publishers for opening designs or views with the paired meshery-extensions integration

When the publishers sent `view_id` while the consumer read `viewId`, the view ID was undefined at runtime. With the paired meshery-extensions change, both sides use `viewId`; during a cross-repository version mismatch, events may not be picked up.

> - fix(wire-format): canonicalize OPEN_*_EXTENSIONS event-bus payloads + ViewInfoModal props @leecalcote (#19136)

## Dependency updates (7)

7 more, none mentioning security

- `- [Chore]: Bump meshery/schemas to v1.2.13 @l5io (#19145)`
- `- [Chore]: Bump meshery/schemas to v1.2.12 @l5io (#18013)`
- `- chore(deps): bump @meshery/schemas ^1.2.12 + @sistent/sistent ^0.21.5 @leecalcote (#19140)`
- `- chore(deps): bump @sistent/sistent to ^0.21.4 @leecalcote (#19128)`
- `- chore(deps): Bump picomatch from 2.3.1 to 4.0.4 in /ui @[dependabot[bot]](https://github.com/apps/dependabot) (#19101)`
- `- [UI] Upgrade to mui-datatables v7.1.0 @ritzorama (#19098)`
- `- Chore: Upgrade to Node 22 and React 19 @leecalcote (#19083)`

## Other changes (20)

- Typed shallow copies for MeshSync dehydration and design hydration
- `mesheryctl model init` tests reset flag state
- Workspace commands now send `orgId`
- Standardized error handling in `mesheryctl system config`
- Docker Compose remediation message typo fixed
- `ViewInfoModal` adopts camelCase props
- Empty `/test` page removed from Meshery UI
- Documentation updates and historical meeting record removal
- First-time contributor workflow converted to an agentic workflow
- E2E extensions test migrated to TypeScript
- Docs Noob Tester workflow updates downloads and finding reports
- Docker edge push and Docker Hub description steps removed from `build-ui-and-server.yml`
- Meshery model definitions use the `schemas.meshery.io` namespace
- Documentation text cleanup and removal of old meeting records
- First-time contributor workflow converted to an agentic workflow
- UI end-to-end test `extensions.spec.js` migrated to TypeScript
- Minikube installation, UI contribution, and provider documentation updates
- `DeployAdapter` switches adapter images to `meshery/`
- Documentation cleanup
- Meshery UI React dependency updated to `^19.2.5`

---

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