# Meshery v1.0.7

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

Breaking changes 6 · Important fixes 4 · Enhancements 1 · Dependency updates 3 · Other changes 18

## Breaking changes (6)

### Meshery provider commands validate flags and return errors

- Affects: Meshery system provider commands

Previously, invalid boolean values for `--all` and `--force` were accepted silently, and some provider-command errors were logged while the command returned success. In the changed paths, logging now uses the internal handler instead of direct logrus calls.

Evidence: “Before fix: `--all` and `--force` flags accepted any value silently (no validation)” https://github.com/meshery/meshery/pull/18287

> - fix(mesheryctl): system provider return proper error, remove logrus, … @Omkar-Ugal (#18287)

### Docker Compose error reporting changed in `mesheryctl system stop`

- Affects: Docker Compose use of `mesheryctl system stop` (Inferred)

Previously, the command used direct `logrus` calls and standard wrapped errors for Docker Compose client-creation and container-stop failures. Those failures are now reported through Meshkit errors, and the command uses `utils.Log` for logging.

Evidence: “This replaces direct logrus usage with utils.Log and standard errors with Meshkit errors.” https://github.com/meshery/meshery/pull/18374

> - fix(mesheryctl): use meshkit error properly and remove logrus in syst… @Vydeh07 (#18374)

### Provider commands now return errors to Cobra

- Affects: the `mesheryctl system provider` commands (Inferred)

When configuration loading, context operations, or provider information lookup failed, these commands previously logged the error and returned nil; provider listing used `Fatalf` when provider information could not be fetched. Those paths now return errors to Cobra instead, and direct logrus calls are replaced with the internal logger.

> - fix(mesheryctl): system provider return proper error, remove logrus, … @Omkar-Ugal (#18287)

### `mesheryctl system update` now reports failures through Cobra

- Affects: setups using `mesheryctl system update`

Previously, failures in several preflight, configuration, context, and health-check paths were logged and returned as nil, so the command could fail silently. These failures now produce a non-success command status; logging uses `utils.Log` and `.Infof` instead of direct logrus calls and `fmt.Sprintf` wrappers.

Evidence: “Crucial fix: Refactored multiple blocks in PreRunE and RunE that previously logged errors and returned nil (silent failures). These now properly return the err to Cobra to ensure the CLI exits with the correct status code upon failure.” https://github.com/meshery/meshery/pull/18622

> - [mesheryctl] Standardize logging and error propagation for system update @ashwanisingh011 (#18622)

### Updated error handling in `mesheryctl model import`

- Affects: URL and CSV imports through `mesheryctl model import`

Previously, a failed URL import was logged but the command returned nil; it now returns the import error as a command error. CSV import errors continue to be returned, but without the command-level log output.

Evidence: “It updates `mesheryctl model import` to return URL import errors instead of swallowing them.” https://github.com/meshery/meshery/pull/18420

> - [mesheryctl] return proper errors in model import @Umesh-Tiruvalluru (#18420)

### SMP performance-test validator rejects invalid endpoint URLs

- Affects: SMP performance-test configurations with endpoint URLs

Previously, relative or malformed values such as `not-a-url`, `/health`, and `health` passed validation and could reach runtime; they now return `ErrValidURL`. Valid absolute endpoints, including the documented HTTP and TCP examples, pass validation.

Evidence: “This PR fixes the SMP performance test validator so invalid endpoint strings like `not-a-url` are rejected during validation instead of slipping through to runtime.” https://github.com/meshery/meshery/pull/18291

> - [Server] Reject invalid performance test endpoint URLs @Manishnemade12 (#18291)

## Important fixes (4)

### [Silent failure] Next.js artifact passthrough for `/_next`

- Affects: Meshery setups serving the main UI’s Next.js build artifacts under `/_next`

Previously, unauthenticated requests—including those with missing or expired cookies—for these artifacts were redirected to `/provider`; the HTML response could not be parsed as JSON and silently aborted client-side navigation. Now, unauthenticated GET requests receive the JSON artifacts needed for the navigation to complete.

> - fix(server): serve /_next static assets without auth, accept HEAD on UI routes @leecalcote (#18672)

### Catch-all UI route now accepts `HEAD` requests

- Affects: setups using the catch-all UI route to serve UI paths

Before this change, `HEAD` requests fell through to the method-not-allowed handler and returned 405. They now reach `ServeUI` through the route's existing provider and auth middleware.

> - fix(server): serve /_next static assets without auth, accept HEAD on UI routes @leecalcote (#18672)

### Dashboard resource menu hook-order error fixed

- Affects: Meshery UI Dashboard resource pages

During resource menu initialization, `tableConfig()` could be called conditionally multiple times, causing React to raise “fewer hooks than expected” errors. It is now called exactly once per render, eliminating the hook warnings while preserving existing functionality.

> - Fix React hook error on Dashboard resource pages @marblom007 (#18619)

### Catalog grid crash on undefined design data fixed

- Affects: Meshery UI catalog grid view (`/configuration/catalog?view=grid`)

When a design had `catalog_data` undefined, reading its `published_version` caused a `TypeError` crash. The grid now avoids that crash, while published designs still display their version correctly.

> - [UI] Fix crash on catalog grid when catalog_data is undefined @leecalcote (#18614)

## Enhancements (1)

- HEAD support for Meshery model static files

## Dependency updates (3)

3 more, none mentioning security

- `- Bump next from 16.2.1 to 16.2.3 in /provider-ui @[dependabot[bot]](https://github.com/apps/dependabot) (#18662)`
- `- [Chore]: Update to Sistent v0.18.4 @l5io (#18618)`
- `- Bump go.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetrichttp from 1.35.0 to 1.43.0 @[dependabot[bot]](https://github.com/apps/dependabot) (#18589)`

## Other changes (18)

- Workspace view now requires `--orgId` and sends it in ID requests
- Core schema imports standardized to `core`
- E2E `connections.spec.js` test migrated to TypeScript
- `connections.spec.js` E2E test migrated to TypeScript
- mesheryctl GoReleaser archive configuration fixed
- GoReleaser v2 archive configuration fixed
- Meshery documentation light/dark toggle icon update fixed
- `Raj.md` added to the meeting documentation
- Mateen Anjum introduction added to the meeting documentation
- Samuel meeting attendance file added
- Adan Shahid's file and introduction added to meeting documentation
- Ankit Kumar introduction added to meeting documentation
- Kavitha Karunakaran's bio added to meeting documentation
- Meeting attendance note from Joy Gundu
- Eko Widodo's introduction added to the meeting notes
- Harsh Kushwaha introduction added to meeting documentation
- Yash Mahakal's introduction added to the meeting documentation
- Meeting notes add attendance-marking instructions

---

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