# Meshery v1.0.14

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

Breaking changes 7 · Deprecations 1 · Important fixes 2 · Dependency updates 5 · Other changes 23

## Breaking changes (7)

### Event consumers switch to canonical camelCase JSON keys

- Affects: Meshery UI Event and Notification Center consumers, and clients using the `Event` or `EventsFilter` JSON fields or the `actedUpon` query parameter

Previously, consumers still read fields such as `event.created_at`, `event.user_id`, `event.system_id`, and snake_case event-summary keys while meshkit was at v1.0.6. They now read the canonical camelCase fields and summary keys; `getEventFilter` also accepts the legacy `acted_upon` query parameter as a fallback.

Evidence: “`ui/rtk-query/notificationCenter.ts` - `getEventsSummary` `transformResponse` reads canonical summary keys (`countBySeverityLevel`, `totalCount`, `readCount`); leaves the `sort` URL param as `created_at` because it is the GORM column name, not a JSON field, and is whitelisted by `SanitizeOrderInput` (annotated with a comment to that effect)” https://github.com/meshery/meshery/pull/18987

> - chore(deps): bump meshkit v1.0.6 -> v1.0.7 + flip Event consumer reads @leecalcote (#18987)

### Meshery Server error responses now use structured JSON

- Affects: clients consuming Meshery Server handler and provider error responses
- Action required: No schemas-side change is required

Previously, some error paths returned plain text, causing the UI's RTK Query parser to crash; client-payload unmarshal failures could return 500, and errors after streaming could corrupt downloads without changing the status. Affected status codes are corrected, and post-stream errors are logged instead of appended to download bodies.

Evidence: “Migrates Meshery Server from plain-text HTTP error responses to structured JSON envelopes carrying full MeshKit error metadata (`code`, `severity`, `probable_cause`, `suggested_remediation`, `long_description`). Resolves the `SyntaxError: Unexpected token 'S', "Status Cod"... is not valid JSON` crash in the UI's RTK Query baseQuery and gives every Meshery client (UI, `mesheryctl`, Kanvas, Meshery Cloud) a stable, structured error contract.” https://github.com/meshery/meshery/pull/18919

> - fix(server): JSON error responses across handlers + provider layer @jamieplu (#18919)
> - fix(server): JSON error responses across handlers + provider layer @jamieplu (#18919)
> - fix(server): JSON error responses across handlers + provider layer @jamieplu (#18919)
> - fix(server): JSON error responses across handlers + provider layer @jamieplu (#18919)

### Typed MeshKit errors for affected server paths

- Affects: Meshery server paths for design import, pattern conversion, artifact compression, registry log flush and entity-status updates, extension proxying, and connection state-machine operations

Previously, these failures returned only `{error: <stdlib msg>}`; design-import `oneOf` invariant errors also differed in shape from other 4xx responses. When these failures occur, responses now include `code`, `severity`, `probable_cause`, and `suggested_remediation`; design-import invariant errors use `ErrInvalidImportRequest` and match the shape of other 4xx responses.

Evidence: “Wrap bare-string `errors.New` returns in `resolveImportVariant` (design import oneOf invariant violations) with `ErrInvalidImportRequest`, so that arm of the design-import endpoint's 400 responses no longer differs in shape from its other 4xx responses.” https://github.com/meshery/meshery/pull/18955

> - fix(server): promote raw-err passthroughs to MeshKit codes (follow-up to #18919) @leecalcote (#18955)

### Meshmodel registration reports log-write failures as HTTP 500

- Affects: server setups using `RegisterMeshmodelComponents`

When `WriteLogsToFiles` failed during registration, the internal flush failure previously returned HTTP 400 and was classified as a client error.

Evidence: “`component_handler.go::RegisterMeshmodelComponents` — `WriteLogsToFiles` failure was returning 400; now 500. The flush is internal-only and not driven by caller input, so 4xx mis-classifies the failure as a client error.” https://github.com/meshery/meshery/pull/18955

> - fix(server): promote raw-err passthroughs to MeshKit codes (follow-up to #18919) @leecalcote (#18955)

### Extension proxy failures now return HTTP 502

- Affects: server setups using `ExtensionsHandler` and `provider.ExtensionProxy`

For remote-provider network, DNS, TLS, or non-2xx failures, `ExtensionsHandler` previously returned HTTP 500.

Evidence: “`extensions.go::ExtensionsHandler` — failure of `provider.ExtensionProxy` was returning 500; now 502. The failure is in the upstream remote provider (network, DNS, TLS, non-2xx response), not in this Meshery server, so 502 Bad Gateway is the correct passthrough status.” https://github.com/meshery/meshery/pull/18955

> - fix(server): promote raw-err passthroughs to MeshKit codes (follow-up to #18919) @leecalcote (#18955)

### Kubernetes connection interfaces switch to canonical camelCase

- Affects: Kubernetes connection metadata, `GetK8sContexts` query parameters, or `K8sContext` GraphQL and UI fields

Previously, metadata keys and query parameters, along with generated GraphQL and UI fields, used snake_case. Meshery Cloud accepts both canonical and snake_case metadata keys, with canonical keys taking precedence.

Evidence: “After this change, the canonical wire form is camelCase across struct, metadata blob, URL query, and graphql codegen, fully aligned with the canonical identifier-naming contract in `meshery/schemas`.” https://github.com/meshery/meshery/pull/18986

> - fix(wire-format): flip Kubernetes connection metadata literal keys to canonical camelCase (Phase 5b) @leecalcote (#18986)
> - fix(wire-format): flip Kubernetes connection metadata literal keys to canonical camelCase (Phase 5b) @leecalcote (#18986)

### MeshSync handler errors now use standardized wrappers

- Affects: the server's MeshSync event and store-update handlers (Inferred)

These handlers previously logged raw errors. They now use `ErrMeshsyncEvent` and `ErrMeshsyncStoreUpdates`, with codes `meshery-server-1379` and `meshery-server-1380` and probable-cause and suggested-remediation information.

Evidence: “Currently, the `MeshsyncDataHandler` in `server/models/meshsync_events.go` logs raw errors instead of using Meshery's standardized error code system defined in `server/models/error.go`.” https://github.com/meshery/meshery/pull/18236

> - [Server] Implement Proper Error Codes for MeshSync Data Handler @workwithsarang (#18236)

## Deprecations (1)

### Legacy local-mirror JSON fields and shims deprecated

- Affects: Meshery server local-mirror types and UI consumers for `User`, `Role`, `Connection`, `Workspace`, `Event`, `MesheryPattern`, `MesheryResults`, `Mappings`, `Capabilities`, `Collaboration`, `Academy`, and `MeshModels`
- Removed in: Phase 6

When Meshery Cloud emitted canonical camelCase fields, older local-mirror types silently dropped them because Go's JSON matching does not cross an underscore boundary. The updated types decode those fields, while legacy fields and `MarshalJSON`/`UnmarshalJSON` shims remain for unmigrated downstream consumers during the deprecation window.

> - fix(wire-format): flip meshery server + UI to canonical camelCase (Phase 5) @leecalcote (#18974)
> - fix(wire-format): flip meshery server + UI to canonical camelCase (Phase 5) @leecalcote (#18974)
> - fix(wire-format): flip meshery server + UI to canonical camelCase (Phase 5) @leecalcote (#18974)

## Important fixes (2)

### [Silent failure] Load-test SSE marshaling errors stay in-stream

- Affects: load tests using the server's SSE handler

When JSON marshaling a load-test result failed during an active SSE response, `http.Error` could corrupt SSE framing after headers were flushed and leave the worker blocked if the response-channel buffer filled. The handler now emits a `LoadTestResponse` error event and drains the channel until it closes.

> - ci(server): flip forbidigo http.Error guard to blocking @leecalcote (#18927)

### MeshSync handlers now check unexpected object types

- Affects: server MeshSync event and store-update handlers

Previously, a non-error error-event object or a store-update object that was not a `[]interface{}` could trigger an unchecked type assertion and panic. Such objects are now logged through the corresponding error wrapper and skipped, allowing the handler to continue processing.

> - [Server] Implement Proper Error Codes for MeshSync Data Handler @workwithsarang (#18236)

## Dependency updates (5)

5 more, none mentioning security

- `- chore(deps): bump meshkit v1.0.6 -> v1.0.7 + flip Event consumer reads @leecalcote (#18987)`
- `- chore(deps): Bump github.com/olekukonko/tablewriter from 1.1.0 to 1.1.4 @[dependabot[bot]](https://github.com/apps/dependabot) (#16824)`
- `- Bump github.com/open-policy-agent/opa from 1.11.0 to 1.12.1 @[dependabot[bot]](https://github.com/apps/dependabot) (#16825)`
- `- Bump github.com/envoyproxy/go-control-plane/envoy from 1.35.0 to 1.36.0 @[dependabot[bot]](https://github.com/apps/dependabot) (#16826)`
- `- Bump postcss from 8.5.6 to 8.5.12 in /docs @[dependabot[bot]](https://github.com/apps/dependabot) (#18947)`

## Other changes (23)

- Regression tests for HTTP utility buffer-encode-then-write
- Removed the legacy application handler file
- Commented-out `getLatestKubeVersionFromRegistry` function removed
- Transient-provider handling documented in `SessionInjectorMiddleware`
- Loading screen font name aligned and redundant preload removed
- MeshKit-aware API error formatting in toasts
- Coding-agent profiles standardized on a full tool profile
- Unsupported `copilot-requests` permission removed from Meshery Docs Noob Tester workflow
- Meshery Code Contributor agent GitHub tool allowance expanded to `github/*`
- PR E2E workflow fails on Playwright test failures
- Server CI lint guard checks the full file set
- Default remote-provider URLs now use `https://cloud.meshery.io`
- Stable-release workflow switches to `release-notes-notification-email.yml`
- Reusable GitHub Actions workflow for preparing and emailing release notes
- REST API reference page font family updated
- Duplicate count sentence removed from REST API reference overview
- Error-contract documentation clarifies `forbidigo` lint behavior
- Error-contract documentation for Phase 9 blocking and streaming JSON responses
- Spelling corrected in CLI end-to-end test contribution docs
- Light/dark mode toggle icon fixed in v0.9 static documentation
- Dashboard Widgets contributing documentation updated
- Integrations page heading and navigation text revised
- Alex Rudenkiy contributor introduction added

---

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