# Meshery v0.9.2

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

Security 1 · Breaking changes 3 · Important fixes 4 · Dependency updates 3 · Other changes 15

## Security (1)

### Login redirects now accept only safe in-app `ref` paths

- Affects: Local- and remote-provider login flows that receive a `ref` query parameter

Previously, the local provider redirected only to decoded `ref` values that passed its safety check, while the remote provider used any non-empty raw `ref` as its redirect URL.

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

## Breaking changes (3)

### Remote-provider retries now clone requests

- Affects: remote-provider requests

After a remote-provider request received HTTP 401 and token refresh succeeded, the retry previously reused the original request and body. Now replayable bodies are refreshed from `GetBody`; requests without a body use `http.NoBody`, and a non-replayable body causes an error.

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

### `mesheryctl` system commands now propagate errors

- Affects: use of `mesheryctl system context` and `mesheryctl system check`

When an affected error path occurred, these commands logged the error and returned nil, which could hide a failure and produce a success exit code. They now return the error to the CLI, so the command reports failure instead.

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

### Remote-provider token refresh now rejects non-200 responses

- Affects: remote-provider token refresh (Inferred)

Before, only HTTP 500 returned an explicit error; other statuses proceeded to token-response decoding. Now every non-200 response returns an error with the status code and, when readable, the trimmed response body.

Evidence: “- if r.StatusCode == http.StatusInternalServerError { - return "", ErrTokenRefresh(fmt.Errorf("failed to refresh token. Status code 500")) - }” https://github.com/meshery/meshery/pull/18162

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

## Important fixes (4)

### [Silent failure] Meshery UI Node.js engine range corrected

- Affects: Meshery UI installations or builds using Node.js (Inferred)

Installs and builds silently failed on Node 18 and early Node 20.x because the upgraded ESLint and Next.js toolchain required Node 20.19+. The UI package now advertises `^20.19.0 || ^22.13.0 || >=24` as its Node.js engine range.

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

### Remote-provider 401 handling skips refresh for non-refreshable tokens

- Affects: remote-provider requests

When a request gets a 401 while its token is blank, cannot be decoded, or has no nonblank refresh token, the original response is returned.

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

### Remote-provider token refresh trims tokens and rejects blank values

- Affects: remote-provider token refresh

Previously, cached tokens and returned `TokenCookieName` values with surrounding whitespace were used as-is, while blank or missing refreshed values were stored and returned.

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

### Local-provider UI boot hang fixed

- Affects: Meshery UI sessions during bootstrap, including local-provider boot

The UI could hang during bootstrap. Bootstrap failures are now logged and the outer loader clears when initialization finishes or throws; if session initialization stays loading for over 10 seconds, a slow-initialization message appears and warnings repeat every 15 seconds.

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

## Dependency updates (3)

3 more, none mentioning security

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

## Other changes (15)

- Preference-persister tests add Given/When/Then comments and database cleanup
- UI TypeScript lint configuration and suppressions adjusted
- UI build tooling migrated from `webpack` to `turbopack`
- Deprecated `eslint` key removed from `next.config.js`
- Registry tree views migrated to `SimpleTreeView` and the v8 API
- UI TypeScript deprecation error silenced
- Component definition lookup misses logged at debug level
- ESLint unused-variable rules split by file type
- Meshery UI user and system-event requests use the API endpoints
- Server JSON response headers and identity-profile route aliases
- One `getLoggedInUser` cache entry per browser session
- Default preferences no longer persisted when a session is missing
- TypeScript linting updates across UI files
- Meshery Code Contributor agent adds PostgreSQL tools
- Updated model-page Related Models and suggested-reading sections

---

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