# Meshery v1.0.37

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

Breaking changes 1 · Important fixes 1 · Enhancements 2 · Dependency updates 2 · Other changes 3

## Breaking changes (1)

### mesheryctl performance profile commands use the new API and schemas

- Affects: `mesheryctl` performance profile listing or creation commands (Inferred)

Previously, these commands used `/api/user/performance/profiles` and legacy service-mesh-performance construct and project models. They now use `/api/performance/profiles` and Meshery Schemas performance profile types.

Evidence: “This switches performance test/profile handling from the legacy service-mesh-performance construct to Meshery Schemas performance profile types, keeps compatibility route handling, and moves the performance UI toward schema-generated API hooks.” https://github.com/meshery/meshery/pull/19909

> - [Performance] Recreate schema-native performance refactor @PragalvaXFREZ (#19909)
> - [Performance] Recreate schema-native performance refactor @PragalvaXFREZ (#19909)

## Important fixes (1)

### Relationship-evaluation rendering supports camelCase metadata

- Affects: relationship-evaluation events in the Meshery UI (Inferred)

When event metadata used `evaluationResponse`, the formatter previously showed empty actions and design without indicating an error. It now uses the contained actions and design for either `evaluationResponse` or `evaluation_response`.

> - [UI] Add Evaluate button for design relationship evaluation @rishiraj38 (#19798)

## Enhancements (2)

- `mesheryctl` accepts explicit mesh and technology names
- Evaluate action added to the Designs page (To use: The user must have the `keys.EVALUATE_RELATIONSHIPS` permission.)

## Dependency updates (2)

2 more, none mentioning security

- `- chore/upgrade/meshery schemas @CodeAhmedJamil (#19912)`
- `- [chore] schemas: upgrade to v1.3.7 @CodeAhmedJamil (#19911)`

## Other changes (3)

- Duration parsing updated in `mesheryctl perf apply`
- Debug logging removed from the permission-denied page
- Single-filter delete confirmation now names the filter

---

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