# Meshery v1.0.24

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

Breaking changes 1 · Important fixes 9 · Other changes 2

## Breaking changes (1)

### Navigator reads nested provider capabilities for Designs visibility

- Affects: Navigator configurations using provider access-control data, including `persist-meshery-patterns`, to control Designs visibility

Previously, the capability check read `providerUiAccessControl.providerCapabilities` directly and set `show` on the Configuration category. It now reads `providerUiAccessControl.providerPayload.providerCapabilities` and sets visibility on the Designs child.

> - fix permission issue in configuration panel @aabidsofi19 (#19546)

## Important fixes (9)

### Meshery performance calendar timestamp handling fixed

- Affects: the `/performance` calendar

Rows with a null or missing `test_start_time` previously made the `.format()` call throw and crash the calendar render. Such rows and rows with unparseable timestamps are now omitted, while valid timestamps retain their embedded timezone offset.

> - [UI] Fix performance dashboard crash on null test_start_time @hortison (#19542)

### Connections table null-metadata crash fixed

- Affects: Meshery UI connections page

Before Redux metadata hydration completed, a null `connectionMetadataState` caused a `TypeError` and the production error fallback. The table now renders with `nextStatus` and `kindLogo` falling back to undefined when metadata is absent.

> - fix(ui): stop React #185 update-depth loops on /management/connections @hortison (#19544)

### Connection deep-link URL clearing fixed

- Affects: `/management/connections` pages with a `connectionId` deep link

When the linked connection was off the current page, a refetch or cache invalidation supplied a fresh array and the effect cleared `connectionId`, which could trigger a React update-depth loop. The URL now retains the ID across pagination, filtering, and search.

> - fix(ui): stop React #185 update-depth loops on /management/connections @hortison (#19544)

### Connections page MeshSync flush crash fixed

- Affects: connections table MeshSync flush action (Inferred)

When the connections page rendered with the MeshSync flush action, invoking the wrapper created a new async function on each render and caused a React maximum-update-depth crash. The menu now receives the `useCallback` handler itself.

> - fix(ui): stop React #185 update-depth loops on /management/connections @hortison (#19544)

### Connections page render loop fixed

- Affects: connections UI components that pass `onDeploymentModeAnchor` (Inferred)

The connections page crashed with a React maximum-update-depth error after the ConnectionTable refactor; each render created a fresh `onDeploymentModeAnchor` function. The prop now receives the `useCallback` handler `handleDeploymentModeAnchorOpen`.

> - fix(ui): stop React #185 update-depth loops on /management/connections @hortison (#19544)

### Connection table column updates avoid redundant commits

- Affects: Meshery UI connections table

When the columns memo was invalidated, an effect enqueued a state commit even if no columns had changed. Column state is now updated only when the columns differ from the previous render.

> - fix(ui): stop React #185 update-depth loops on /management/connections @hortison (#19544)
> - fix(ui): stop React #185 update-depth loops on /management/connections @hortison (#19544)

### Responsive column visibility no longer re-commits identical state

- Affects: Responsive column visibility in the Meshery UI connections table (Inferred)

During an unrelated parent re-render, the responsive-column-visibility effect created a new object and queued a state commit even when column visibility had not changed.

> - fix(ui): stop React #185 update-depth loops on /management/connections @hortison (#19544)

### Redundant row-expansion state writes fixed in connection and MeshSync tables

- Affects: Meshery UI connection and MeshSync tables using row expansion

When `mui-datatables` fired `onRowExpansionChange` during an internal re-render with the expanded rows unchanged, repeated commits could reach React’s update-depth limit, particularly on slow renders. Value-equal expanded-row state is now skipped.

> - fix(ui): stop React #185 update-depth loops on /management/connections @hortison (#19544)

### MeshSync stepper update loop fixed

- Affects: Setups using the MeshSync stepper in the Meshery UI (Inferred)

When the stepper wrote `sharedData`, the new object reference retriggered the effect repeatedly because `sharedData` was a dependency. The effect now depends on `onClose` and `setSharedData` instead, stopping the self-feeding update loop.

> - fix(ui): stop React #185 update-depth loops on /management/connections @hortison (#19544)

## Other changes (2)

- Lifecycle Navigator icons corrected
- Stable-release CI workflow fixes

---

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