# Meshery v0.9.0

2026-03-23 · [Original release notes](https://github.com/meshery/meshery/releases/tag/v0.9.0) · [Full summary](https://ratatosk.io/en/releases/meshery/v0.9.0)

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

## Breaking changes (9)

### Cluster resync skipped on hard reset with empty `k8scontextID`

- Affects: cluster 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`.

> - fix(resync): skip cluster resync when hardReset=true and k8scontextID is empty @Omkar-Ugal (#18038)

### Workspace listing in `mesheryctl` now uses pagination

- Affects: use 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)")” https://github.com/meshery/meshery/pull/17967

> - refactor(mesheryctl): enhance workspace command using flags validator @lekaf974 (#17967)

### Meshery CLI set-context status validation fixed

- Affects: set-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).” https://github.com/meshery/meshery/pull/17912

> - [mesheryctl] Use MakeRequest for set‑context API calls @dipanshurdev (#17912)

### Workspace organization identifier renamed to `organization_id`

- Affects: workspace 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",” https://github.com/meshery/meshery/pull/18126

> - upgrade to meshery/schemas v0.8.135 @leecalcote (#18126)

### Performance-result metrics field and YAML key renamed

- Affects: YAML 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"`” https://github.com/meshery/meshery/pull/17716

> - Fix HTTP response body leak in PublishMetrics and correct typos @Ironankit525 (#17716)

### Full design IDs by default in `mesheryctl design list`

- Affects: the `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.” https://github.com/meshery/meshery/pull/17971

> - [mesheryctl] Show full design IDs in design list by default @PragalvaXFREZ (#17971)

### Workspace creation validates required flags and `orgId` UUIDs

- Affects: workspace 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"`” https://github.com/meshery/meshery/pull/17967

> - refactor(mesheryctl): enhance workspace command using flags validator @lekaf974 (#17967)

### `mesheryctl system channel` commands now return errors

- Affects: setups 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.

> - 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)

### Shared flag validation for `mesheryctl` model commands

- Affects: use 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.

> - refactor(mesheryctl): model commands flags validation @lekaf974 (#17737)
> - refactor(mesheryctl): model commands flags validation @lekaf974 (#17737)
> - refactor(mesheryctl): model commands flags validation @lekaf974 (#17737)

## Important fixes (8)

### Stale context selection fixed for `system channel view` and `system provider view`

- Affects: `system 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)

### Kubernetes endpoint reporting fixed in `mesheryctl system status`

- Affects: Kubernetes 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)

### Relationship evaluation returns partial results at the depth limit

- Affects: designs 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)

### Nil preference panic in session sync fixed

- Affects: server 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)

### Channel switch nil pointer panic fixed

- Affects: `mesheryctl 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)

### Missing connection deletion handling fixed

- Affects: connection 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)

### Metrics response-body closure fixed in both providers

- Affects: setups 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)

### Local metrics provider marshal-error wording corrected

- Affects: local 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)

## Enhancements (1)

- Workspace detail viewing with `mesheryctl exp workspace view`

## Dependency updates (11)

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 changes (93)

- `GetWorkspaceByIdHandler` validates `orgID`
- Updated error message for `ResyncResources` machine-context failures
- YAML front matter added to `api-doc` and `gen-test` skills
- Policy relationship tests updated to use `RelationshipDefinitionSelectorsPatch`
- LLM-agnostic agent definitions, skills, development hooks, and `AGENTS.md` guidance added
- Documentation site migrated to Hugo and launched
- Documentation stylesheet Sass variable references fixed
- Catalog files moved from `docs-new/catalog` to the repository root
- Documentation site sidebar layout and navigation adjusted
- Documentation code-block and guide-page markup updates
- Documentation content synchronized with the new `v0.8.214` release page
- Documentation site's `openapi.yml` synchronized with updated OpenAPI content
- Custom sorting for the documentation release listing
- Blank layout for the latest-release documentation page
- Corrected `mesheryctl model` help examples
- Sorted context output for `mesheryctl` channel and provider views
- Workspace server and CLI lint and typecheck issues fixed
- Centralized logger initialization for Meshery CLI
- CLI schema-upgrade fixtures, golden outputs, and tests updated
- CLI schema field accesses corrected to `.ID`
- `mesheryctl` documentation and images moved to the new documentation structure
- Relationship-view test golden output updated
- Meshery Server workspace persistence now uses `workspace.Workspace`
- Docker extension UI `usePingServer` checks run on setup and clean up
- Workspace creation validates `OrganizationID` as a UUID
- Pattern row-deletion confirmation fixed
- More reliable end-to-end tests for the design configurator and extension links
- Sistent icons replace Material UI icons in `ConfirmationModal` and `CustomToolbarSelect`
- mesheryctl e2e performance workflow switches from an action to commands
- e2e workflow uses a temporary auth file for adapter deployment
- Workflow checkout pinned to `actions/checkout@v6` with date-output fixes
- Pull request handler prints branch refs from an environment variable
- Documentation links added to `mesheryctl system channel` help
- Security-insights license and Copilot PR ref handling updated
- Flaky UI end-to-end tests for the design configurator and extension links stabilized
- Jekyll removed from E2E-results commit step name and message
- Documentation preview workflows consolidated into `build-and-preview-docs.yml`
- Documentation preview comment action handles both event payloads
- Security Insights file moved to the LFX Insights path
- Hugo documentation site support
- `mesheryctl` documentation migrated to the reference structure
- Documentation build updates Docsy and Hugo and fixes Dart Sass warnings
- Documentation contributor agent updated and content synchronized
- First-PR welcome text now uses an HTTPS Slack link
- Project structure overview added to the Meshery README
- Related-discussions shortcode shows Meshery-tagged topics
- Nathanael Fetue's GSoC 2026 introduction added to documentation meeting materials
- Copy-button shortcode for documentation code blocks
- Hugo code-block styling configuration changed
- Updated Model Schema link on the contributing models page
- Kavitha Karunakaran's bio added to meeting notes
- Model Schema link updated in the contributing-models documentation
- Taiwo Sholadoye’s meeting attendance added to the documentation
- Himanshu Rathi's attendance for the week of 03-19-2026 added
- Dhakshin Raghav's introduction added to the meetings documentation
- Attendance submission for the week of 03-19-2026
- Chetan Ahuja's introduction added to the documentation
- Bhumika Garg's introduction added to the documentation
- Joy Gundu meeting notes updated
- Introductory message added in `Yash-Mahakal.md`
- Mahesh Nandigam’s meeting introduction added
- Schema-contributing guide covers OpenAPI vendor extensions
- Schema-contributing guide documents `snake_case` for database-mirrored fields
- Schema contribution guide adds a build-pipeline diagram
- Schema-contributing guide adds database helper guidance
- Further reading for contributing schemas
- Attendance instruction added to the March 19 meeting-notes index
- Dockerfile catalog copy moved to `/app/docs/data/catalog/`
- Documentation ignore rules consolidated in the root `.gitignore`
- Documentation editing links now point to `docs/content/...`
- Community sections removed from the English localization file
- Attendance and introduction for Pruthvi Raj D S at the March 13, 2026 Newcomers Meeting
- `Nishant.md` added with personal and project details
- `Raunak.md` file added
- Added `EylulGeyik.md` file
- Added `bishal-attendance.md`
- March 13, 2026 meeting attendance added
- Ahmed Sayed's introduction added to the meetings documentation
- GSoC introduction for Harpalsinh Sindhav
- Taiwo Sholadoye's meeting attendance added
- Harsh Raj's introduction added to the meeting notes
- Meeting details added to `joy_gundu.md`
- Introductory text added to `Samanvai.md`
- Introductory message added in `Yash-Mahakal.md`
- `Hrishikesh.md` meeting notes file added
- Introduction section added for the week of 03-12-2026
- OpenSSF Best Practices Baseline badge added to `README`
- Copilot PR workflow head-ref passthrough and echo
- License expression updated in both `SECURITY-INSIGHTS.yml` files
- Pull request head ref sanitization in the Copilot PR handler workflow
- Security insights file moved
- README project structure overview added
- HTTPS Slack links for first-time issue and PR welcome comments

---

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