# Meshery v1.0.35

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

Breaking changes 1 · Important fixes 3 · Enhancements 3 · Other changes 13

## Breaking changes (1)

### `mesheryctl` design-evaluation error codes changed

- Affects: automation or integrations that inspect `mesheryctl` design-evaluation error codes (Inferred)

Previously, the evaluation error codes collided with `ErrDeleteModelCode` and `ErrPromptCancelledCode`; they now use `mesheryctl-1247` and `mesheryctl-1248`.

Evidence: “The error-codes utility check was failing because #17897 introduced duplicate codes: `ErrEvaluateDesignCode` (1200) and `ErrEvaluateDesignResponseCode` (1202) collided with `ErrDeleteModelCode` and `ErrPromptCancelledCode`. Reassigned to free codes 1247/1248.” https://github.com/meshery/meshery/pull/19804

> - fix(mesheryctl): bridge v1beta3 design parse output to v1beta1 for evaluation @PragalvaXFREZ (#19804)

## Important fixes (3)

### Policy-engine UUIDs stabilized across restarts

- Affects: Go policy-engine setups that persist or consume UUIDs generated at `selectorSetItem` or `eval_rules` `selectorSet` call sites (Inferred)

When these call sites generated UUIDs from typed structs, formatting leaked pointer addresses into the seeds, so UUIDs drifted across process restarts and persisted values churned. They now remain stable across restarts.

> - Compile Golang Policy Engine to WASM @guan404ming (#18939)

### Policy match-label result selection made deterministic

- Affects: policy match-label evaluations in the Go policy engine (Inferred)

When results were truncated to 20 entries, map iteration could make different runs select different subsets.

> - Compile Golang Policy Engine to WASM @guan404ming (#18939)

### Policy-binding output ordering fixed

- Affects: policy-binding evaluations (Inferred)

Previously, iteration over the `bindingKinds` map could leak its order into the output. The keys are now sorted before iteration, so the output order no longer depends on map iteration order.

> - Compile Golang Policy Engine to WASM @guan404ming (#18939)

## Enhancements (3)

- Local CSV input for `mesheryctl relationship generate` (To use: Provide either `--file/-f` with a CSV containing two header rows, at least one data row, and at least 15 columns, or the existing Google Spreadsheet input; one input is required and the options are mutually exclusive.)
- Design evaluation command in mesheryctl
- Browser-loadable WebAssembly build of the Golang Policy Engine

## Other changes (13)

- `wasm-engine` target switches to `awk` for `wasm_exec.js` patching
- WASM policy-engine build fixed
- Repository listings added to `MAINTAINERS.md`
- Substantial revision to `GOVERNANCE.md`
- `wasm-engine` build now cleans and tidies its Go module
- Native Go policy engine package documentation added
- mesheryctl design evaluation build fixed
- Consistent colors for design action icons
- Node 22 updates for UI and Docker extension builds
- Discard button error backgrounds fixed
- Audit-only `step-security/harden-runner` in three GitHub workflows
- Broken links to the Meshery UI contribution guide fixed
- Native Go policy engine documentation

---

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