# Meshery v1.0.1

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

Breaking changes 28 · Important fixes 27 · Enhancements 5 · Dependency updates 25 · Other changes 175

## Breaking changes (28)

### `DeleteMeshSyncResource` success body and failure response changed

- Affects: clients calling the `DeleteMeshSyncResource` endpoint

Previously, successful deletions returned an empty HTTP 200 response, while failed deletions also returned HTTP 200 and appeared only in server logs. Successful deletions now include `{"deleted": true}`; failed deletions return HTTP 500 with an error message.

Evidence: “- On delete failure: - logs the delete error - returns `500 Internal Server Error` with error message in response body - On delete success: - returns `200 OK` - returns JSON response: `{"deleted": true}`” https://github.com/meshery/meshery/pull/18193

> - [Server] Fix DeleteMeshSyncResource HTTP response handling @Manishnemade12 (#18193)

### Request retries now check body replayability

- Affects: requests with bodies made through `RemoteProvider.DoRequest` (Inferred)

After a successful token refresh, replayable bodies are resent; requests with non-replayable bodies return an error instead of being retried.

Evidence: “default: + return nil, fmt.Errorf("request body is not replayable")” https://github.com/meshery/meshery/pull/18162

> - local provider boot hang @hortison (#18162)

### RemoteProvider token refresh validation and trimming

- Affects: setups using `RemoteProvider` token refresh (Inferred)

Refresh responses other than HTTP `200 OK` or with an empty token now return errors, and whitespace around cached and returned tokens is trimmed.

Evidence: “if r.StatusCode != http.StatusOK { + body, readErr := io.ReadAll(r.Body) + if readErr != nil { + return "", fmt.Errorf("failed to refresh token. status code %d", r.StatusCode) + } + return "", fmt.Errorf("failed to refresh token. status code %d: %s", r.StatusCode, strings.TrimSpace(string(body)))” https://github.com/meshery/meshery/pull/18162

> - local provider boot hang @hortison (#18162)

### Dashboard-opening errors no longer fail `mesheryctl system start`

- Affects: setups using `mesheryctl system start`

Previously, if opening the dashboard failed, `mesheryctl system start` returned that error; it now logs a warning and returns nil. With `skipBrowserFlag` set, it skips the dashboard command and returns successfully.

Evidence: “- return dashboardCmd.RunE(nil, nil) + if skipBrowserFlag { + utils.Log.Info("Meshery deployed. Use `mesheryctl system dashboard` to access the UI.") + return nil + } + if err := dashboardCmd.RunE(nil, nil); err != nil { + utils.Log.Warnf("Meshery deployed successfully, but could not open dashboard: %v\nRun `mesheryctl system dashboard` to access the UI.", err) + } + return nil” https://github.com/meshery/meshery/pull/18477

> - fix: mesheryctl e2e system start @lekaf974 (#18477)

### Configuration-loading errors returned by `mesheryctl system reset`

- Affects: the `mesheryctl system reset` command (Inferred)

When Meshery configuration loading failed, the command logged the error but returned success; it now returns the error to its caller. Extra arguments now produce `utils.ErrInvalidArgument`, and reset logging uses `utils.Log` instead of `logrus`.

> - fix: system reset uses meshkit error properly, remove logrus @Omkar-Ugal (#18358)

### Updated `mesheryctl` login validation and stopped-server status handling

- Affects: `mesheryctl system login` calls with `--provider`, and use of `mesheryctl system status`

Previously, arbitrary supplied provider values were not rejected by the validator; invalid non-empty values are now rejected, and errors in the changed login paths are returned to the command rather than only logged. When Meshery is not running, `system status` prints the context, platform, and status message but returns success instead of an error.

> - refactor(mesheryctl): enhance login command UX and error handling, update error codes + fix bug in system status @lekaf974 (#18345)

### Strict flag validation and returned errors in `mesheryctl system status`

- Affects: the `mesheryctl system status` command

Previously, invalid `--verbose`/`-v` values were accepted silently, and failures in health-check, configuration/context, or server-status paths were logged while the command returned nil. These cases now reject invalid flag values or return command errors.

Evidence: “Error: invalid argument "invalid" for "-v, --verbose" flag: strconv.ParseBool: parsing "invalid": invalid syntax” https://github.com/meshery/meshery/pull/18255

> - fix: system status uses meshkit error properly, remove logrus, add fl… @Omkar-Ugal (#18255)

### System context and system-check errors now reach the CLI

- Affects: the `mesheryctl system context` command and associated system-check paths

Configuration unmarshalling, current-context retrieval, or health-check errors were logged and returned as success, producing an incorrect CLI success exit code. These failures now reach the CLI caller, so the command reports failure.

Evidence: “- Prevented silent failures and incorrect CLI success exit codes” https://github.com/meshery/meshery/pull/18154

> - fix(mesheryctl): return proper error in system context command @Omkar-Ugal (#18154)

### Stable context ordering in Meshery CLI `--all` commands

- Affects: the `mesheryctl system channel view --all` and `mesheryctl system provider view --all` commands

Previously, the channel command's output order varied because it iterated contexts from a Go map.

Evidence: “`mesheryctl system channel view --all` was producing nondeterministic output because it iterated contexts from a Go map directly.” https://github.com/meshery/meshery/pull/18140

> - Stabilize mesheryctl system view output across reused Cobra command state @[copilot-swe-agent[bot]](https://github.com/apps/copilot-swe-agent) (#18140)

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

- Affects: non-verbose `mesheryctl design list` output (Inferred)

Previously, non-verbose listings truncated design IDs; full IDs appeared only with `--verbose`.

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

### Set-context API error reporting in `mesheryctl`

- Affects: use of `mesheryctl system config` or `mesheryctl connection create`

Previously, these commands could appear to succeed when the set-context API returned a 4xx or 5xx response. They now return an error with the status code and response body for non-2xx responses; the raw response body remains in debug logs.

Evidence: “If the API responds with a non-2xx status code, the command now returns an error that includes the status code and response body.” https://github.com/meshery/meshery/pull/17912

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

### Shared flag validation added to `mesheryctl model` commands

- Affects: the affected `mesheryctl model` commands, especially those with path-valued flags (Inferred)

Path-valued flags are checked before affected commands run. `mesheryctl model delete` now produces no output and no error for a nonexistent model, instead of returning an error.

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

### Metrics publishing leak fixed and field spelling corrected

- Affects: Meshery server deployments publishing metrics through `DefaultLocalProvider` or `RemoteProvider`

When `PublishMetrics()` received `http.StatusOK`, it returned without closing the response body, leaking HTTP connections and file descriptors over time; it now closes the body on that path. The YAML output key changes from `servermatrics` to `servermetrics`.

Evidence: “The `defer resp.Body.Close()` was placed **after** an early `return nil` on `http.StatusOK`, meaning the response body was never closed on the success path. Over time, this leaks HTTP connections and file descriptors.” https://github.com/meshery/meshery/pull/17716

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

### Environment and workspace handlers now read `orgId`

- Affects: organization IDs supplied through environment or workspace handler query parameters (Inferred)

Before this change, frontend requests using `orgId` supplied an empty organization ID, causing provider calls to fail with 404.

Evidence: “The frontend (@meshery/schemas) sends `orgId` (camelCase) but the Go handlers were reading `orgID` (capital ID). Since Go's url.Values.Get() is case-sensitive, the org ID was always empty, causing provider calls to fail with a 404.” https://github.com/meshery/meshery/pull/18513

> - Fix orgId query parameter case mismatch in environment and workspace … @fitzergerald (#18513)

### `SessionInjectorMiddleware` preserves sessions during remote-provider outages with HTTP 503

- Affects: sessions using a remote provider
- Action required: No companion Meshery Cloud change is required first; the companion PR can be deployed independently.

When a remote provider such as Cloud was temporarily unreachable, the middleware logged users out and redirected them to login, causing a redirect loop while the outage continued.

Evidence: “- **Distinguish transient errors from auth failures**: `SessionInjectorMiddleware` no longer destroys user sessions when Cloud is temporarily unreachable — returns 503 instead of logging out + redirecting (which looped when Cloud stayed down).” https://github.com/meshery/meshery/pull/18434

> - fix: resolve auth redirect loops between Meshery Server and Cloud @leecalcote (#18434)

### Empty organization IDs rejected by `GetWorkspaceByIdHandler`

- Affects: integrations calling `GetWorkspaceByIdHandler` (Inferred)

When the organization ID query value was empty, the handler previously passed it to `GetWorkspaceByID` without checking. It now returns HTTP 400 with a workspace-input error instead.

> - fix(server): enforce missing OrgID handling in GetWorkspaceByIdHandler @lekaf974 (#18141)

### `mesheryctl filter view` rejects extra positional arguments

- Affects: the `mesheryctl filter view` command

The command previously silently accepted multiple positional arguments; it now returns an at-most-one-argument error. The `--all` conflict and missing name/ID checks also run earlier, in `PreRunE`.

Evidence: “# Properly rejected mesheryctl filter view arg1 arg2 Error: accepts at most 1 arg(s), received 2” https://github.com/meshery/meshery/pull/18362

> - [mesheryctl] Replace cobra.ArbitraryArgs with proper argument validat… @Manishnemade12 (#18362)

### `mesheryctl system logout` now returns errors

- Affects: use of `mesheryctl system logout`

Previously, failures to load Mesheryctl configuration, get the current context’s token, or write the token file were logged but returned as nil. These failures now return errors to the caller; a token-file write failure returns `ErrLogout` (`mesheryctl-1229`).

Evidence: “- utils.Log.Error(ErrGetCurrentContext(errors.Wrap(err, "failed to find token path for the current context"))) - return nil + return ErrGetCurrentContext(err)” https://github.com/meshery/meshery/pull/18327

> - fix: system logout uses meshkit error properly, remove logrus @Omkar-Ugal (#18327)

### Dashboard command now validates flags and returns errors

- Affects: the `mesheryctl system dashboard` command

Previously, invalid flag values were not checked, and configuration/context lookup or port-forward initialization errors could be logged while the command returned success. The validator now rejects invalid values, and affected errors are returned instead of being treated as successful completion.

> - refactor(mesheryctl): update dashboard command flags and improve error handling @lekaf974 (#18341)

### Structured errors from `mesheryctl system delete`

- Affects: `mesheryctl system delete` on Docker or unsupported platforms

Previously, Docker Compose client-creation or container-removal failures and unsupported platforms returned generic system errors. These failures now return corresponding Meshery/meshkit errors, including Docker Compose error codes, changing the errors received by automation.

> - refactor(mesheryctl): update system delete removing logrus reference and return proper meshkit error  @lekaf974 (#18342)

### `mesheryctl system logs` validates `--follow` and returns errors

- Affects: use of `mesheryctl system logs`

Previously, invalid `--follow` values were silently accepted, while failures could be logged and the command could still return nil. Health-check, config/context, and server-not-running failures now return command errors.

Evidence: “Error: invalid argument "invalid" for "-f, --follow" flag: strconv.ParseBool: parsing "invalid": invalid syntax” https://github.com/meshery/meshery/pull/18227

> - fix: system logs uses meshkit error properly, remove logrus, add flag… @Omkar-Ugal (#18227)

### Context subcommands now validate flags and return structured errors

- Affects: `mesheryctl system context create`, `delete`, and `view` commands

Previously, these commands had no added pre-run flag validation, and some configuration read/write, duplicate-context, prompt, and argument errors lacked structured handling. Those failure paths now return errors instead of following the less specifically handled paths.

> - refactor(mesheryctl): update system context subcommands to use proper error handling and flags validator @lekaf974 (#18244)

### Missing-connection deletion returns HTTP 404; mesheryctl succeeds

- Affects: connection deletion

When a deletion targets an ID that does not exist, the server previously returned an internal-server error and the CLI returned a connection-not-found error. Now the CLI logs “No connection with ID "…" found” as a warning.

> - fix: update connection deletion logic and error handling on server and cli @lekaf974 (#17910)

### Channel command failures now return errors

- Affects: `mesheryctl system channel` commands, including `view`, `set`, and `switch`

When getting the current context fails or its content is unavailable, the commands previously logged the error and returned nil; they now return the error. `set` and `switch` return an invalid-argument error when the number of release-channel arguments is not exactly one.

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

### Performance API metric names corrected

- Affects: server metric publishing messages and code using `PerformanceResult` (Inferred)

The comment and error message previously used `asyncronously` and `Matrics`/`ServerMatrics`; they now use `asynchronously` and `Metrics`. The Go field is now `ServerMetrics`, while its JSON field remains `server_metrics`.

Evidence: “- `asyncronously` -> `asynchronously` in comments - - `Matrics` -> `Metrics` in error message - - `ServerMatrics` -> `ServerMetrics` struct field name (JSON tag unchanged, non-breaking)” https://github.com/meshery/meshery/pull/17716

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

### Workspace commands moved to `mesheryctl workspace`

- Affects: the `mesheryctl` workspace commands (Inferred)

Workspace commands were previously under `mesheryctl exp workspace`; their workspace operations are unchanged.

> - [mesheryctl] graduate workspace command from experimental @PragalvaXFREZ (#18125)

### Workspace-list page-size flag renamed to `--pagesize`

- Affects: workspace-list command invocations using `--page-size` (Inferred)

When explicitly set, the value is sent as the `pagesize` query parameter. The default remains 10 and the maximum remains 100.

> - [mesheryctl] graduate workspace command from experimental @PragalvaXFREZ (#18125)
> - [mesheryctl] graduate workspace command from experimental @PragalvaXFREZ (#18125)

### Docker image catalog data now uses a new source and path

- Affects: Meshery Docker image deployments and integrations reading its catalog files (Inferred)

Previously, the image copied catalog data from `docs-new/data/catalog` to `/app/docs/catalog/`. It now copies data from `docs/data/catalog` to `/app/docs/data/catalog/`.

Evidence: “COPY ./docs/data/catalog /app/docs/data/catalog/” https://github.com/meshery/meshery/pull/17991

> - Clean up for docs @CodexRaunak (#17991)

## Important fixes (27)

### Meshery design deployment now honors `--skip-save`

- Affects: Meshery design deploy/onboard commands run with `--skip-save`

Previously, the parsed design was persisted to the Meshery Server database despite the flag. It is now left unpersisted, and the server returns a successful 200 payload with a simulated design record and a generic success broadcast event.

> - [mesheryctl] design deploy --skip-save not saving is not skipped @Ironankit525 (#17860)

### Active config path honored by `mesheryctl system token`

- Affects: non-default active config files used with `mesheryctl system token`, including files selected with `--config`

Previously, token operations used the default config path instead of the selected file, so they could read or change the wrong config. They now use the active config file.

> - Refactor token commands to use active config path for consistency @Manishnemade12 (#18280)

### System check flag, error, and platform handling corrected

- Affects: use of `mesheryctl system check`

Previously, invalid flag values were not validated, and some health-check or related failure-path errors were logged or swallowed rather than returned. Invalid flags are now rejected, errors are returned, and full checks enable operator checks only on Kubernetes.

> - refactor(mesheryctl): system check error logger @lekaf974 (#18138)

### Corrected `READY` counts in `mesheryctl system status`

- Affects: `mesheryctl system status` container counts

When a pod had fewer ready containers than its total, the `READY` column showed equal counts, such as `1/1`, regardless of actual pod health. It now uses the total container count as the denominator, so one ready container out of two appears as `1/2`.

> - fix(mesheryctl): correct container ready count in system status @Vydeh07 (#18224)

### Stale endpoint display fixed in `mesheryctl system status`

- Affects: Kubernetes deployments with an accessible Meshery service endpoint, such as a LoadBalancer IP or NodePort

When the configured endpoint was stale or differed from the actual service endpoint, `mesheryctl system status` displayed the configured value instead. It now discovers and displays the actual endpoint, reports when it differs from the configured endpoint, and `system dashboard` uses the same discovery helper.

> - [mesheryctl] Refactor endpoint discovery with shared helper function @PragalvaXFREZ (#17073)

### Environments connection pagination page-count calculation fixed

- Affects: Environments pagination for assigned and assignable connections (Inferred)

When `total_count` was nullish, the old calculation did not handle it explicitly. The new calculation treats nullish totals as zero and removes the redundant outer `parseInt`.

> - [UI] Remove redundant parseInt wrapping Math.ceil in Environments @boergeson (#18437)

### Dashboard layout unsaved-change confirmation

- Affects: Dashboard layout editor

When leaving with unsaved changes, users can choose to save or discard their edits before leaving.

> - [UI] Add unsaved changes confirmation modal to Dashboard @Rajesh-Nagarajan-11 (#18382)

### Meshery normalizes empty remote workspace responses

- Affects: setups with a remote provider that returns `204 No Content` for `GetWorkspaces`

Previously, the server forwarded the empty body, which could cause a UI JSON parse error. Now it returns a JSON `workspace.WorkspacePage` with zero workspaces, page size, and total count, plus the requested page value (or zero if omitted); `200 OK` responses still pass through unchanged.

> - [Server] Normalize empty remote workspace list responses @[copilot-swe-agent[bot]](https://github.com/apps/copilot-swe-agent) (#18475)

### Remote-provider session validation recovery fixed

- Affects: sessions validated through a remote provider (Inferred)

When token introspection failed, including while Meshery Cloud was temporarily unavailable, session validation had no recovery path and could send users into a redirect loop. It now attempts token refresh as a fallback and re-verifies a successfully refreshed token.

> - fix: resolve auth redirect loops between Meshery Server and Cloud @leecalcote (#18434)

### Unauthenticated handler caps repeated authentication redirects

- Affects: unauthenticated remote-provider authentication flows

Repeated failed authentication could keep redirecting without a retry limit. After three failed attempts, the server clears the JWT, provider-session, and retry cookies and returns HTTP 401 instead of redirecting again; the retry counter cookie has a two-minute TTL.

> - fix: resolve auth redirect loops between Meshery Server and Cloud @leecalcote (#18434)

### Structured `[AUTH_FLOW]` authentication logs

- Affects: authentication flows through the remote-provider and middleware decision points (Inferred)

When token introspection failed during a temporary Meshery Cloud outage, token refresh had no recovery path and users entered a redirect loop. The middleware now preserves sessions and returns 503 during temporary outages, and after three failed attempts the loop ends with an error instead of redirecting forever.

> - fix: resolve auth redirect loops between Meshery Server and Cloud @leecalcote (#18434)

### Nil `UserID` handling fixed in events resolver

- Affects: GraphQL event subscriptions (Inferred)

When `event.UserID` is nil, the resolver leaves the resolved `UserID` unset instead of converting it to a string.

> - fix: handle nil UserID in events resolver @ianrwhitney (#18366)

### Connection registration panic fixed

- Affects: Meshery connection registration requests

When `InitializeMachineWithContext` returned an error, the handler could continue with a nil `inst` and panic, crashing the Meshery server. It now returns an HTTP 500 response instead of continuing to `inst.SendEvent()`.

> - [Server] Fix nil pointer dereference in ProcessConnectionRegistration @Manishnemade12 (#18219)

### Connection-registration nil-event panic fixed

- Affects: connection-registration requests

When `SendEvent` returned an error with a nil event, the handler dereferenced `*event` and could panic. It now returns HTTP 500 without persisting or publishing when the event is nil; with a non-nil event, it persists and publishes it.

> - [Server] Fix nil pointer dereference in ProcessConnectionRegistration @Manishnemade12 (#18219)

### Connection-registration error message corrected

- Affects: connection registration (Inferred)

Previously, the error message misspelled `persist` as `perisit` and showed a literal `%s` instead of the connection kind. It now spells `persist` correctly and includes the connection kind.

> - [Server] Fix nil pointer dereference in ProcessConnectionRegistration @Manishnemade12 (#18219)

### Depth-limit errors in relationship evaluations fixed

- Affects: design relationship evaluations

Heavily nested evaluations that exceeded `MAX_RE_EVALUATION_DEPTH` previously returned HTTP 500 with an evaluation-depth error. They now return the relationship changes processed up to that point with HTTP 200.

> - fix(server): return partial result when evaluation depth is exceeded @dhakshin-raghav (#18120)

### Database-backed preference fallback fixed

- Affects: database-backed preferences

When no preference row existed, loading failed, or stored JSON was `null`, session sync could receive a nil preference and panic. It now receives a non-nil default in those cases; the default enables `AnonymousUsageStats` and `AnonymousPerfResults`.

> - [Server] Prevent nil preference panic during session sync @fitzergerald (#18048)

### Kubernetes context initialization stops on client setup errors

- Affects: Kubernetes context initialization

Previously, kubeconfig-generation or client-creation failures left a nil client that could trigger a nil-pointer panic and crash Meshery Server, including when one invalid or unreachable cluster was used in a multi-cluster setup. Controllers now initialize only with a valid client, and kubeconfig-generation failures emit an error event with `k8sContextID`, `k8sContextName`, and `connectionID`.

> - fix: prevent nil pointer panic on invalid kubeconfig during controller init @pulkitvats2007-crypto (#18478)

### `mesheryctl system logs` nil-pointer panic fixed

- Affects: `mesheryctl system logs`

When pod listing failed and `podList` was nil, the command accessed `podList.Items` before checking the error and could panic. It now returns the listing error before accessing the pod-list items.

> - fix(mesheryctl): resolve nil pointer dereference in system logs @Vydeh07 (#18261)

### System `view` command context selection fixed

- Affects: the `mesheryctl system channel view` and `mesheryctl system provider view` commands

When Cobra command state was reused, a stale persistent `--context` value could make a later command resolve the wrong or default-empty result. Subsequent `view` commands now use the default context unless that invocation explicitly sets `--context`.

> - Stabilize mesheryctl system view output across reused Cobra command state @[copilot-swe-agent[bot]](https://github.com/apps/copilot-swe-agent) (#18140)

### `mesheryctl` nil-pointer panic fixed

- Affects: `mesheryctl` invocations

When `config.GetMesheryCtl()` failed during an invocation, it could cause a nil-pointer panic. The note does not specify how the failure is handled now.

> - fix: Fixes nil pointer panic when config.GetMesheryCtl() fails @ARZU-V (#18106)

### RTK Query token endpoints now return JSON

- Affects: Meshery UI token retrieval through RTK Query `getToken` or `getAccessToken` (Inferred)

Previously, these calls requested `GET /api/user/token`, the OAuth callback that redirects with HTML and caused a JSON parsing error. They now request `GET /api/token` to receive token JSON.

> - Fix RTK Query token endpoints hitting wrong URL @yi-nuo426 (#18508)

### Kanvas rounded keyboard arrow icon resolution fixed

- Affects: Kanvas extension code that externalizes `@mui/icons-material/KeyboardArrowDownRounded`

When Kanvas externalized this icon subpath from `designOutline.tsx` but Meshery did not export it, production had a runtime gap despite matching shared package versions. The remote-component resolve map now includes the icon subpath.

> - fix: export KeyboardArrowDownRounded for Kanvas @leecalcote (#18472)

### Kanvas extension runtime dependency mappings added

- Affects: Kanvas extension bundles requiring the added runtime dependencies

When the bundle needed modules absent from the remote-component mappings, the Kanvas extension could fail to load with a missing-module error such as `@reduxjs/toolkit/query/react` not existing in dependencies. The added mappings let it load without that error.

> - [UI] Add missing remote component dependencies for Kanvas extension @guan404ming (#18262)

### UI Node.js engine range updated for toolchain compatibility

- Affects: UI installs and builds using Node.js

Installs and builds were broken on Node 18 and early Node 20.x, even though the UI package advertised `^18 || ^20`. The declared range is now `^20.19.0 || ^22.13.0 || >=24`, matching the upgraded toolchain's Node 20.19+ requirement.

> - fix(ui): update engines.node to match ESLint 10 and Next 16 requirements @[copilot-swe-agent[bot]](https://github.com/apps/copilot-swe-agent) (#18164)

### Local-provider application-shell startup hang fixed

- Affects: application-shell bootstrap during local-provider UI startup (Inferred)

The local-provider UI could hang during startup; bootstrap failures are now logged and the outer loader is cleared.

> - Fix:local provider boot hang @hortison (#18157)

### Local provider boot hang fixed

- Affects: UI setups using current-user or profile queries, and clients of `/api/user`, `/api/user/prefs`, `/api/provider/capabilities`, or `/api/identity/users/profile` (Inferred)

The current-user and profile queries previously missed Meshery's actual endpoints, and `/api/user`, `/api/user/prefs`, and `/api/provider/capabilities` did not return the proper JSON responses. The queries now use the actual endpoints, those routes return JSON, and `/api/identity/users/profile` has aliases.

> - Fix:local provider boot hang @hortison (#18157)

## Enhancements (5)

- Debug logging for Meshery startup and dashboard endpoint discovery
- RTK query error middleware and mutation notifications
- Turbopack alias for the remote component config (To use: Turbopack in development mode)
- Delayed debug logging for persistent session loading
- Workspace view command added to `mesheryctl`

## Dependency updates (25)

### `flatted` updated from 3.3.4 to 3.4.2 in `/ui`

- [CVE-2026-32141](https://www.cve.org/CVERecord?id=CVE-2026-32141), [CVE-2026-33228](https://www.cve.org/CVERecord?id=CVE-2026-33228), [GHSA-25h7-pfq9-p65f](https://github.com/advisories/GHSA-25h7-pfq9-p65f), [GHSA-rf6f-7fwh-wjgh](https://github.com/advisories/GHSA-rf6f-7fwh-wjgh)

> - 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 /ui @[dependabot[bot]](https://github.com/apps/dependabot) (#18070)

### `flatted` updated to 3.4.2

- [GHSA-25h7-pfq9-p65f](https://github.com/advisories/GHSA-25h7-pfq9-p65f), [GHSA-rf6f-7fwh-wjgh](https://github.com/advisories/GHSA-rf6f-7fwh-wjgh)

In 3.3.4, `parse()` could cause denial of service through unbounded recursion during its revive phase and was vulnerable to prototype pollution. These issues are fixed in 3.4.2.

> - Bump flatted from 3.3.4 to 3.4.2 in /provider-ui @[dependabot[bot]](https://github.com/apps/dependabot) (#18072)
> - Bump flatted from 3.3.4 to 3.4.2 in /provider-ui @[dependabot[bot]](https://github.com/apps/dependabot) (#18072)

### `/docs` `picomatch` dependency updated to 2.3.2

- [CVE-2026-33671](https://www.cve.org/CVERecord?id=CVE-2026-33671), [CVE-2026-33672](https://www.cve.org/CVERecord?id=CVE-2026-33672), [GHSA-3v7f-55p6-f55p](https://github.com/advisories/GHSA-3v7f-55p6-f55p), [GHSA-c2c7-rcm5-vvqj](https://github.com/advisories/GHSA-c2c7-rcm5-vvqj)

Version 2.3.2 includes fixes for several security issues in `picomatch`.

> - Bump picomatch in /docs @[dependabot[bot]](https://github.com/apps/dependabot) (#18214)

22 more, none mentioning security

- `- Bump lodash from 4.17.23 to 4.18.1 in /install/docker-extension/ui @[dependabot[bot]](https://github.com/apps/dependabot) (#18397)`
- `- Bump yaml from 1.10.2 to 1.10.3 in /install/docker-extension/ui @[dependabot[bot]](https://github.com/apps/dependabot) (#18213)`
- `- Bump brace-expansion from 1.1.12 to 1.1.13 in /install/docker-extension/ui @[dependabot[bot]](https://github.com/apps/dependabot) (#18285)`
- `- Bump path-to-regexp from 0.1.12 to 0.1.13 in /install/docker-extension/ui @[dependabot[bot]](https://github.com/apps/dependabot) (#18284)`
- `- Bump picomatch from 2.3.1 to 2.3.2 in /install/docker-extension/ui @[dependabot[bot]](https://github.com/apps/dependabot) (#18216)`
- `- Bump node-forge from 1.3.3 to 1.4.0 in /install/docker-extension/ui @[dependabot[bot]](https://github.com/apps/dependabot) (#18240)`
- `- 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)`
- `- chore: Upgrade meshery/meshkit to v1.0.2 @[copilot-swe-agent[bot]](https://github.com/apps/copilot-swe-agent) (#18438)`
- `- upgrade to meshery/schemas v0.8.135 @leecalcote (#18126)`
- `- Bump lodash-es from 4.17.23 to 4.18.1 in /ui @[dependabot[bot]](https://github.com/apps/dependabot) (#18395)`
- `- Upgrade meshery/schemas to v1.0.1 and replace local struct definitions @leecalcote (#18373)`
- `- Bump yaml in /ui @[dependabot[bot]](https://github.com/apps/dependabot) (#18212)`
- `- [UI] Chore Sistent v0.18.0 @hortison (#18172)`
- `- upgrade/react 19, next 16, eslint 10 @hortison (#18163)`
- `- Chore: Upgrade to meshery/schemas v0.9.0 @hortison (#18152)`
- `- [Dependencies] Upgrade Meshery Server, UI, and mesheryctl to meshery/schemas v0.8.136 @leecalcote (#18127)`
- `- 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 (175)

- Event-subscription start log now formats `userID`
- Failing `MapPreferencePersister` unit test skipped until implementation is complete
- Server preference-persister test cleanup and Given/When/Then comments
- Default preferences seeded on map-backed read misses
- Unrefreshable-token `401` handling in `RemoteProvider.DoRequest`
- Docker Extension UI React 19 compatibility fixes
- Cluster resync skipped during hard resets without Kubernetes context
- YAML front matter added to `api-doc` and `gen-test` skills
- Policy relationship tests switch to `RelationshipDefinitionSelectorsPatch`
- Repository agent and skill definitions added and updated
- Documentation site in `docs-new` migrated to Hugo Go
- Fixed Sass variable references in `docs-new` stylesheets
- Catalog files moved to the root
- Updated `docs-new` documentation layout
- Documentation sync adds the `v0.8.214` release page
- Blank Hugo layout for the latest-release page using `plainify`
- Documentation release lists now use `sort-releases.html` for sorting
- Legacy YAML CLI documentation generator removed
- Clarified `mesheryctl system context create` usage text
- `mesheryctl` end-to-end workflow adjustments
- YAML documentation generator output path fixed
- Build-and-preview-docs workflow path filters updated
- `Credential`, `Key`, and `Schedule` now use schema models
- BATS end-to-end tests for `mesheryctl registry update`
- Stale experimental workspace command constants fixed in `mesheryctl` error-helper references
- Workspace CLI documentation links moved to non-experimental paths
- End-to-end assertions aligned with current workspace and connection behavior
- Model command returns configuration errors
- Corrected `mesheryctl model` help examples and spelling
- Workspace `golangci-lint` failures cleaned up
- Centralized logger package for Meshery CLI
- Updated `mesheryctl` component-view and search tests
- Stale `mesheryctl` schema field accesses corrected
- mesheryctl documentation migrated
- Workspace flag validation and pagination URL checks improved
- Relationship-view unit test updated for API response change
- Core UI and User Settings Playwright tests migrated to TypeScript
- Underlines removed from dashboard-card links
- Local RTK Query API path normalization
- Meshery settings autocomplete exceptions logged
- Kanvas can externalize shared libraries
- MeshSync Stepper handler lookup and registration callback signature updated
- Meshery UI GraphQL subscriptions gain resilient WebSocket handling
- RTK Query 401 handling and logout cleanup updated
- Vitest testing setup added
- 13 data-fetch consumer files migrated to RTK Query
- Meshery UI WebSocket connection lifecycle machine added
- `mesheryEventBus` documented as the extension communication mechanism
- Meshery UI component organization refactored
- Kubernetes chart link displayed without an underline
- Playwright end-to-end tests adjusted to avoid recurring CI timeouts
- Custom Playwright reporter now displays test error messages
- CI workflow removes invalid checkout input and rebases the QA repository
- ESLint issue in CI fixed
- UI end-to-end tests switch to `console.warn` and `console.error` in CI
- Catalog Info modal two-column layout fixed
- Provider UI lint scripts switch to cached ESLint
- Provider UI ESLint configuration updated for ESLint 10
- Workspace Activity query skipped without an organization ID
- Workspace mutations moved to local RTK Query endpoints
- TypeScript lint configuration and fixes across UI source and test files
- Meshery UI build now uses Turbopack
- Deprecated `eslint` config removed; UI scripts skip linting
- UI build and export-playground scripts gain `--no-lint`
- Registry tree views migrated to `SimpleTreeView` v8 API
- Missing component definitions logged at debug level
- `ignoreDeprecations: "6.0"` added to UI TypeScript config and lint-staged config adjusted
- ESLint's base `no-unused-vars` rule limited to JavaScript
- Unified `getLoggedInUser` query cache key
- UI RTK Query wrapper normalizes request URLs
- Pattern deletion accepts trimmed, case-insensitive `DELETE` confirmations
- Stabilized Playwright end-to-end coverage for the design configurator and extension links
- Meshery UI component icons now come from `@sistent/sistent`
- `mesheryctl` end-to-end workflow updated
- Core UI and User Settings end-to-end tests migrated to TypeScript
- Documentation tests use temporary directories for file paths
- UI build workflow split into smaller steps
- Four consistently failing Playwright test timeouts fixed
- First-time contributor workflow switches to `pull_request_target`
- ESLint issue in CI fixed
- BATS end-to-end test added for the registry update command
- CI warnings switched from core warnings to console warnings
- CI job renamed to `update-tests`
- `errcheck` linter enabled in CI
- First-time contributor workflow triggers on opened pull requests
- Documentation-site footer gradient colors updated
- Documentation site switches to a Docsy sidebar
- TypeScript linting maintenance
- PostgreSQL tools added to the Meshery Code Contributor agent
- `mesheryctl` performance workflow updated to replace a brittle SMP action path
- Copilot PR-handler workflow passes the pull request head ref through an environment variable before echoing it
- security-insights license expression set to `Apache-2.0` and Copilot PR-handler head-ref sanitization
- Stabilized end-to-end tests for the design configurator and extension links
- Jekyll wording removed from workflow step and test-report commit message
- Documentation preview workflows consolidated; preview-comment action handles `workflow_run` and `pull_request` payloads
- Security Insights metadata moved to `.github/SECURITY-INSIGHTS.yml`
- GitHub Actions workflows for Hugo documentation updated
- mesheryctl documentation moved under `/reference/mesheryctl`
- Documentation build dependencies updated and Sass warnings addressed
- Documentation contributor agent updated and content synchronized
- Contributor welcome Slack links use HTTPS, and README adds project structure
- docs-new related-discussions rendering and data update fixed
- Relationships shortcode image markup standardized
- Relationships shortcode renders sections collapsed by default
- `Zainab_Ashraf.md` added
- Sulagna Ghosh introduction added to meetings documentation
- Added `Saurabh-Raghuvanshi.md`
- Shubham Sharma's introduction document added
- Ananya's introduction added to the meetings documentation
- Prem Singh's self-introduction added
- `Sohamsig.md` added
- Meeting notes for Joy Gundu added
- Introductory content added to `Raunak.md`
- Kavitha Karunakaran bio added
- Model pages omit empty subtitle paragraphs
- Virat Kumar added to meeting index attendees
- Meeting attendance instructions using named Markdown files
- Documentation links converted to Hugo-friendly absolute paths
- Documentation breadcrumb URLs corrected
- First-time-contributor workflow limited to opened pull requests
- Documentation site footer SCSS updated
- Documentation site adopts a wrapped, custom-styled Docsy sidebar
- Release-note workflow adds a `title` field
- Team management documentation page removed
- Compatibility matrix documentation and styling updated
- Documentation build targets updated
- Documentation compatibility matrix revamped
- Repeated-slash routing fixed on the documentation site
- Meeting notes add instructions for marking attendance
- Meshery v1.0.0 release documentation summary revised
- Meshery v1.0.0 release notes added to the documentation
- v0.9 documentation added as a site version snapshot
- Documentation template renders a Related Models heading without an integrations category
- Nathanael Fetue's GSoC 2026 introduction added to project documentation
- Code block copy button added to the contributing UI tests page
- Project documentation code-block styling fixed
- Model Schema link on contributing models page fixed
- Kavitha Karunakaran’s bio added to meeting notes
- Model Schema link fixed in contributing-models documentation
- Taiwo Sholadoye’s meeting attendance added to project documentation
- Himanshu Rathi's attendance for the week of 03-19-2026 added to documentation
- Dhakshin Raghav introduction added to the meetings documentation
- Attendance submission for the week of 03-19-2026 added to project documentation
- Chetan Ahuja introduction added to project documentation
- Bhumika Garg's introduction added to project documentation
- Joy Gundu meeting notes updated
- `Yash-Mahakal.md` added to project documentation
- Meeting introduction added to project documentation
- Schema-contributing guide expanded with vendor extensions and Schema-Driven Development
- Attendance instructions added to meeting notes documentation
- Documentation ignore rules consolidated in the root `.gitignore`
- Documentation links now target the `docs` directory
- Community sections removed from `docs/i18n/en.toml`
- Newcomers' Meeting documentation adds attendance and introduction for the week of 03-12-2026
- `Nishant.md` added with personal and project details
- `Raunak.md` meeting document added
- Eylül Geyik introduction and interests added
- Bishal Haldar attendance introduction added
- Ragul Balajii's meeting attendance and introduction added
- Ahmed Sayed's introduction added to the meetings documentation
- Harpalsinh Sindhav's GSoC introduction added
- Taiwo Sholadoye's meeting attendance information added
- Harsh Raj's introduction added to meeting notes
- Joy Gundu attendee information added to meeting notes
- Samanvai meeting document added
- Yash Mahakal meeting introduction added
- Initial notes added for the second Layer 5 meeting
- Introduction prompt added to the March 12, 2026 meeting page
- OpenSSF Best Practices Baseline badge added to the README
- Workflow passes the pull request head ref as `head_ref`
- Security-insights license expressions changed to `Apache-2.0`
- Copilot PR handler sanitizes pull request head refs before echoing
- Security Insights metadata moved to `.github/SECURITY-INSIGHTS.yml`
- Welcome-message Slack links switched to HTTPS
- README documents Meshery sub-projects and repositories

---

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