# Meshery v1.0.39

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

Important fixes 4 · Other changes 4

## Important fixes (4)

### Local provider saves supplied connection credential IDs

- Affects: local provider connections created with a supplied `credentialId`

When local provider connection creation was given a `credentialId`, it ignored the ID and stored `uuid.Nil` instead. It now saves the supplied ID and still uses `uuid.Nil` when no ID is provided.

> - [Server] Preserve credential ID when saving connections @chaitanyamedidar (#19883)

### [Silent failure] Design schema detection fixed

- Affects: designs imported from Kubernetes manifests, Helm charts, or Compose files, and designs with a canonical `designs.meshery.io/` `schemaVersion`

When an imported design was checked for the legacy migration, v1beta3 designs could be misclassified as v1alpha2, lose their components, and render as empty canvases; the POST get-handler could also save the emptied design. Detection now identifies legacy v1alpha2 by the absence of a canonical `designs.meshery.io/` `schemaVersion` prefix, keeping current and future schema versions out of that migration.

> - fix(designs): render imported designs misclassified as legacy v1alpha2 @leecalcote (#19934)

### Organization switching and design validation permission checks fixed

- Affects: organization switching on the Oops page and design validation in the deployment confirmation modal

On the Oops page, when Redux organization state was unavailable, the dropdown could show the wrong active organization, and switching could reload before the backend saved the selection. The dropdown now uses the backend-selected organization when Redux state is missing; a failed update prevents reloading and shows an error, and the deployment confirmation modal checks `keys.VALIDATE_DESIGN.subject` instead of `keys.VALIDATE_DESIGN.resource`.

> - fix organization switcher selection and permission typo @rishiraj38 (#19933)

### Registry Relationships tree crash fixed

- Affects: Setups using the Registry Models → Relationships tree, including the Relationships dropdown under a model version

Expanding the Relationships dropdown under a model version could raise a `RangeError: Maximum call stack size exceeded`. Expansion no longer crashes, and the top-level Relationships view is unchanged.

> - [UI] fix: resolve maximum call stack exceeded crash in Registry Models → Relationships tree @YASHMAHAKAL (#19922)

## Other changes (4)

- Required input validation for `mesheryctl design undeploy`
- OrgSwitcher RTK Query imports corrected
- NotificationCenter and Accordion icon imports consolidated
- `version` input removed from the dispatched `notify-providers` workflow

---

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