RATATOSK
← All releases

Mesheryv1.0.54

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

Get Meshery alerts

Email is sent weekly only when there are changes to check; critical security advisories are sent immediately.

Breaking changes2

Controller helper symbols renamed to the corrected spelling

Affectsserver 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.” meshery/meshery/pull/20501 ↗
Show release-note lines
- [server] Fix Meshsyn->Meshsync typo in controller helper symbols @leecalcote (#20501)
github.com/meshery/meshery/releases/tag/v1.0.54

resyncCluster now surfaces MeshSync delete errors

Affectssetups 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.” meshery/meshery/pull/20502 ↗
Show release-note lines
- [Server] Fix FlushMeshSyncData stale table-name subqueries leaking MeshSync data @leecalcote (#20502)
github.com/meshery/meshery/releases/tag/v1.0.54

Important fixes1

  • Deleted-cluster MeshSync inventory cleanup fixed
    AffectsMeshSync 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)
    github.com/meshery/meshery/releases/tag/v1.0.54

Dependency updates2

    2 more, none mentioning security
    • - upgrade to meshkit v1.0.21 @arjunmehta-git (#20506)
    • - Chore: upgrade meshsync and operator @arjunmehta-git (#20505)
    Other changes2

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