RATATOSK
← All releases

Mesheryv0.9.0

Breaking changes 9Important fixes 8Enhancements 1Dependency updates 11Other changes 93

Get Meshery alerts

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

Breaking changes9

Cluster resync skipped on hard reset with empty k8scontextID

Affectscluster resynchronization requested during a hard reset

During a database reset, the Kubernetes context entry could be removed while resyncCluster still tried to use it, causing errors with the Layer5 provider. The hard-reset path now skips the resync and returns model.StatusProcessing.

Show release-note lines
- fix(resync): skip cluster resync when hardReset=true and k8scontextID is empty @Omkar-Ugal (#18038)
github.com/meshery/meshery/releases/tag/v0.9.0

Workspace listing in mesheryctl now uses pagination

Affectsuse of mesheryctl exp workspace list

Previously, the command fetched workspaces without pagination query parameters. With no flags, it now requests the first 10 workspaces (page=0&pagesize=10 in the API); --page is one-based and defaults to 1, while --page-size defaults to 10 and is capped at 100.

Evidence“+ listWorkspaceCmd.Flags().IntVarP(&workspaceListFlags.Page, "page", "", 1, "page number for paginated results. (default: 1)")” meshery/meshery/pull/17967 ↗
Show release-note lines
- refactor(mesheryctl): enhance workspace command using flags validator @lekaf974 (#17967)
github.com/meshery/meshery/releases/tag/v0.9.0

Meshery CLI set-context status validation fixed

Affectsset-context API calls made by mesheryctl system config or mesheryctl connection create

When the API returned a non-2xx status, these commands could appear to succeed. They now return an error containing the status code and response body; successful 2xx responses continue normally, and the raw response body remains in debug logs.

Evidence“Previously, mesheryctl system config and mesheryctl connection create did not validate the HTTP status code returned by the set-context API. As a result, the CLI could appear to succeed even when the API returned an error response (for example, 4xx or 5xx).” meshery/meshery/pull/17912 ↗
Show release-note lines
- [mesheryctl] Use MakeRequest for set‑context API calls @dipanshurdev (#17912)
github.com/meshery/meshery/releases/tag/v0.9.0

Workspace organization identifier renamed to organization_id

Affectsworkspace API responses and CLI workspace-view output(Inferred)

The linked fixtures previously used org_id for that identifier.

Evidence“+ "organization_id": "2d2c0b60-076a-4f0a-8a63-de538570a553",” meshery/meshery/pull/18126 ↗
Show release-note lines
- upgrade to meshery/schemas v0.8.135 @leecalcote (#18126)
github.com/meshery/meshery/releases/tag/v0.9.0

Performance-result metrics field and YAML key renamed

AffectsYAML performance-result output and code using PerformanceResult.ServerMatrics(Inferred)

The YAML key changes from servermatrics to servermetrics, while the JSON tag remains server_metrics; the Go field is now ServerMetrics instead of ServerMatrics. On the HTTP StatusOK success path in PublishMetrics() for both providers, the response body was previously left open after an early return, leaking connections and file descriptors over time; it is now closed.

Evidence“- ServerMatrics interface{} `json:"server_metrics"` + ServerMetrics interface{} `json:"server_metrics"`” meshery/meshery/pull/17716 ↗
Show release-note lines
- Fix HTTP response body leak in PublishMetrics and correct typos @Ironankit525 (#17716)
github.com/meshery/meshery/releases/tag/v0.9.0

Full design IDs by default in mesheryctl design list

Affectsthe mesheryctl design list command(Inferred)

Without --verbose, design IDs were truncated. The existing command invocation now shows the full IDs without a flag change.

Evidence“This requires full `id` which was only displayed in `mesheryctl design list --verbose`. I have added full design ID support in this PR on non-verbose mode (`mesheryctl design list`), to avoid confusion and better UX.” meshery/meshery/pull/17971 ↗
Show release-note lines
- [mesheryctl] Show full design IDs in design list by default @PragalvaXFREZ (#17971)
github.com/meshery/meshery/releases/tag/v0.9.0

Workspace creation validates required flags and orgId UUIDs

Affectsworkspace creation through mesheryctl exp workspace create

Previously, omitting description caused an error, and the old check did not validate whether orgId was a UUID. Now, omitting description creates a workspace with an empty description; missing orgId or name, or a non-UUID orgId, fails validation.

Evidence“OrganizationID string `json:"orgId" validate:"required,uuid"`” meshery/meshery/pull/17967 ↗
Show release-note lines
- refactor(mesheryctl): enhance workspace command using flags validator @lekaf974 (#17967)
github.com/meshery/meshery/releases/tag/v0.9.0

mesheryctl system channel commands now return errors

Affectssetups that use mesheryctl system channel view, mesheryctl system channel set, or mesheryctl system channel switch(Inferred)

Previously, failures such as errors getting the current context, invalid context content, configuration-write errors, or missing switch confirmation were logged and returned as nil, so the commands did not pass the errors to the caller. The returned errors use the meshkit style.

Show release-note lines
- refactor(mesheryctl): update system channel to use meshkit and return errors properly and update description @lekaf974 (#18122)
- refactor(mesheryctl): update system channel to use meshkit and return errors properly and update description @lekaf974 (#18122)
github.com/meshery/meshery/releases/tag/v0.9.0

Shared flag validation for mesheryctl model commands

Affectsuse of mesheryctl model commands

Previously, model generate had command-specific checks for a missing file or argument and too many arguments. It now validates file, template, and register values through the shared path, with new relative and absolute path validation tags.

Show release-note lines
- refactor(mesheryctl): model commands flags validation @lekaf974 (#17737)
- refactor(mesheryctl): model commands flags validation @lekaf974 (#17737)
- refactor(mesheryctl): model commands flags validation @lekaf974 (#17737)
github.com/meshery/meshery/releases/tag/v0.9.0

Important fixes8

  • Stale context selection fixed for system channel view and system provider view
    Affectssystem channel view and system provider view commands

    When Cobra command state was reused, stale persistent-flag state could make a later command resolve the wrong or default-empty result, particularly after a --context override. A temporary context is now used only when --context is set for that invocation; otherwise, the configured default context is used.

    - Stabilize mesheryctl system view output across reused Cobra command state @[copilot-swe-agent[bot]](https://github.com/apps/copilot-swe-agent) (#18140)
    github.com/meshery/meshery/releases/tag/v0.9.0
  • Kubernetes endpoint reporting fixed in mesheryctl system status
    AffectsKubernetes deployments with LoadBalancer or NodePort Meshery services that have a discoverable external endpoint

    Previously, status showed the configured local endpoint even when it was stale or did not reflect the service’s actual status. It now shows the discovered external address and port when available, and notes differences from the configured endpoint with guidance to run mesheryctl system dashboard.

    - [mesheryctl] Refactor endpoint discovery with shared helper function @PragalvaXFREZ (#17073)
    github.com/meshery/meshery/releases/tag/v0.9.0
  • Relationship evaluation returns partial results at the depth limit
    Affectsdesigns with nested relationships

    Previously, reaching MAX_RE_EVALUATION_DEPTH during deeply nested relationship evaluation returned HTTP 500 with evaluation depth exceeded. It now returns the relationship changes processed up to the limit as a partial result with HTTP 200 and logs a warning.

    - fix(server): return partial result when evaluation depth is exceeded @dhakshin-raghav (#18120)
    github.com/meshery/meshery/releases/tag/v0.9.0
  • Nil preference panic in session sync fixed
    Affectsserver session synchronization and preference loading

    A missing persisted preference or stored JSON null could leave no usable preference, causing SessionSyncHandler to panic while assigning prefObj.MeshAdapters; loading errors or a nil result could also leave middleware without a preference. Missing rows now return the default, and middleware uses it when loading errors or returns nil; the default enables AnonymousUsageStats and AnonymousPerfResults.

    - [Server] Prevent nil preference panic during session sync @fitzergerald (#18048)
    github.com/meshery/meshery/releases/tag/v0.9.0
  • Channel switch nil pointer panic fixed
    Affectsmesheryctl system channel switch command

    When config.GetMesheryCtl() failed, the CLI logged the error and continued, leading to a nil pointer panic. It now returns the configuration retrieval error instead.

    - fix: Fixes nil pointer panic when config.GetMesheryCtl() fails @ARZU-V (#18106)
    github.com/meshery/meshery/releases/tag/v0.9.0
  • Missing connection deletion handling fixed
    Affectsconnection deletion through the server API or mesheryctl connection delete

    When the requested connection ID did not exist, the CLI treated a “no rows in result set” response as an error. Now the server returns HTTP 404, and mesheryctl connection delete logs a warning and returns successfully.

    - fix: update connection deletion logic and error handling on server and cli @lekaf974 (#17910)
    github.com/meshery/meshery/releases/tag/v0.9.0
  • Metrics response-body closure fixed in both providers
    Affectssetups publishing metrics through DefaultLocalProvider or RemoteProvider

    On HTTP 200 responses, PublishMetrics() returned before closing the response body, leaking HTTP connections and file descriptors over time. The response body now closes on the success path too.

    - Fix HTTP response body leak in PublishMetrics and correct typos @Ironankit525 (#17716)
    github.com/meshery/meshery/releases/tag/v0.9.0
  • Local metrics provider marshal-error wording corrected
    Affectslocal metrics provider(Inferred)

    The marshal-error text said “Matrics,” and comments used “asyncronously”; both spellings are corrected.

    - Fix HTTP response body leak in PublishMetrics and correct typos @Ironankit525 (#17716)
    - Fix HTTP response body leak in PublishMetrics and correct typos @Ironankit525 (#17716)
    github.com/meshery/meshery/releases/tag/v0.9.0

Enhancements1

  • Workspace detail viewing with mesheryctl exp workspace view
    - feat(mesheryctl): add workspace view command @Vydeh07 (#17711)
    - feat(mesheryctl): add workspace view command @Vydeh07 (#17711)
    github.com/meshery/meshery/releases/tag/v0.9.0

Dependency updates11

    11 more, none mentioning security
    • - Bump flatted from 3.4.1 to 3.4.2 in /install/docker-extension/ui @[dependabot[bot]](https://github.com/apps/dependabot) (#18071)
    • - Bump flatted from 3.3.3 to 3.4.1 in /install/docker-extension/ui @[dependabot[bot]](https://github.com/apps/dependabot) (#17956)
    • - Bump yauzl and hugo-extended in /docs-new @[dependabot[bot]](https://github.com/apps/dependabot) (#17961)
    • - [Dependencies] Upgrade Meshery Server, UI, and mesheryctl to meshery/schemas v0.8.136 @leecalcote (#18127)
    • - upgrade to meshery/schemas v0.8.135 @leecalcote (#18126)
    • - Bump flatted from 3.3.4 to 3.4.2 in /ui @[dependabot[bot]](https://github.com/apps/dependabot) (#18070)
    • - Bump flatted from 3.3.4 to 3.4.2 in /provider-ui @[dependabot[bot]](https://github.com/apps/dependabot) (#18072)
    • - Bump next from 15.5.12 to 15.5.14 in /provider-ui @[dependabot[bot]](https://github.com/apps/dependabot) (#18074)
    • - Bump github.com/buger/jsonparser from 1.1.1 to 1.1.2 @[dependabot[bot]](https://github.com/apps/dependabot) (#18073)
    • - Bump google.golang.org/grpc from 1.77.0 to 1.79.3 @[dependabot[bot]](https://github.com/apps/dependabot) (#18050)
    • - Chore: upgrade meshkit and schemas @fitzergerald (#18052)
    Other changes93

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