A maintenance-focused release with dependency updates, new operator-visible connections and relationships, and fixes across the Meshery CLI and UI. It contains no security advisories or breaking changes.
Source ↗Releases
AI-analyzed release notes for CNCF graduated and incubating projects.
A maintenance release with server notification fixes, Sistent dependency updates, and a new Meshery CLI registry purge command. Existing operator workflows have no broad changes.
Source ↗A focused maintenance release fixes remote-provider environment creation and clarifies environment API compatibility. Requests accept both organizationId and legacy organization_id formats, with organizationId taking precedence and responses using the canonical format. No disruptive operator migration is required.
A maintenance release with dependency updates, model-version cleanup, and server and UI correctness fixes. It also removes old model versions.
Action needed (1)
breakingOld model versions purged
Old model versions are purged in this release.
A small maintenance release with a UI discoverability improvement, documentation polish, and developer-facing logging cleanup. It does not introduce major operational behavior changes.
Source ↗A maintenance release with dependency updates, clearer connection reporting, and UI refinements. It also changes the meshmodel API route naming while retaining deprecated aliases, with no security changes disclosed.
Plan ahead (1)
breakingRenamed meshmodel API routes
The meshmodel API routes are renamed to
/api/registry. Deprecated aliases are included for compatibility.
A maintenance release with UI improvements and dependency updates also includes a security fix for path traversal in file handlers. It does not introduce breaking operator configuration changes.
Action needed (1)
securityPath traversal prevention in file handlers
File handlers now prevent path traversal. The fix ships in this release.
A maintenance release adds an F5 BIG-IP Kubernetes model, updates subscription transport, and corrects UI and permission behavior. GraphQL subscriptions are retired in favor of REST/SSE, alongside updates to models, connections, and interface behavior.
Action needed (1)
breakingGraphQL subscriptions retired
GraphQL subscriptions are retired across the server and UI in favor of
REST/SSE.