# Meshery v1.0.54

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

Breaking changes 2 · Important fixes 1 · Dependency updates 2 · Other changes 2

## Breaking changes (2)

### Controller helper symbols renamed to the corrected spelling

- Affects: server code using the controller helper, including custom code importing `AddMeshsynDataHandlers`

The helper and its call sites used the misspelled `Meshsyn`/`meshsyn` names; they now use the corrected `Meshsync`/`meshsync` spelling. No alias for `AddMeshsynDataHandlers` remains, so custom code importing that symbol is affected.

Evidence: “Searched GitHub across the `meshery` org and broader public code for `AddMeshsynDataHandlers` usage outside this repo. All hits were forks of `meshery/meshery` itself (same file/line) - no genuine external consumer imports this symbol as a package API, so no deprecated alias is kept.” https://github.com/meshery/meshery/pull/20501

> - [server] Fix Meshsyn->Meshsync typo in controller helper symbols @leecalcote (#20501)

### `resyncCluster` now surfaces MeshSync delete errors

- Affects: setups that invoke the `resyncCluster` GraphQL resolver

When MeshSync cleanup failed, the resolver returned `ErrEmptyHandler` for every failure, obscuring the actual delete error. It now returns and logs the delete error wrapped as `ErrFlushMeshSyncData`, along with the context name and server information.

Evidence: “`FlushMeshSyncData` and the `resyncCluster` resolver now share this single helper, removing the duplicated block. The resolver also surfaces the real delete error instead of the misleading `ErrEmptyHandler` it previously returned for any failure.” https://github.com/meshery/meshery/pull/20502

> - [Server] Fix FlushMeshSyncData stale table-name subqueries leaking MeshSync data @leecalcote (#20502)

## Important fixes (1)

### Deleted-cluster MeshSync inventory cleanup fixed

- Affects: MeshSync inventory cleanup after a Kubernetes server's last connection is deleted

When the last connection referencing a Kubernetes server ID was deleted, the flush errored because its child-row subqueries used a nonexistent `objects` table, leaving the cluster's resource and child rows behind. It now removes those rows, deleting child rows before parent resource rows, while leaving rows for other clusters untouched.

> - [Server] Fix FlushMeshSyncData stale table-name subqueries leaking MeshSync data @leecalcote (#20502)
> - [Server] Fix FlushMeshSyncData stale table-name subqueries leaking MeshSync data @leecalcote (#20502)
> - [Server] Fix FlushMeshSyncData stale table-name subqueries leaking MeshSync data @leecalcote (#20502)

## Dependency updates (2)

2 more, none mentioning security

- `- upgrade to meshkit v1.0.21 @arjunmehta-git (#20506)`
- `- Chore: upgrade meshsync and operator @arjunmehta-git (#20505)`

## Other changes (2)

- Docs Docker environment updated to Hugo 0.157.0
- Redundant Common UI tests removed from `performance.spec.ts` and `telemetry.spec.ts`

---

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