RATATOSK
← All releases

Mesheryv1.0.19

Breaking changes 4Important fixes 4Dependency updates 7Other changes 20

Get Meshery alerts

Email is sent weekly only when there are changes to check; critical security advisories are sent immediately.

Breaking changes4

Typed v1alpha3 relationship conversion in the Go policy engine

AffectsGo policy engine conversion of registered v1alpha3 relationships and other relationship values

Previously, relationship values without a matching type case went through a generic JSON marshal/unmarshal fallback. Now v1alpha3 values and pointers use RelationshipV1alpha3ToV1beta2, while values reaching the default case are skipped without an error.

Evidence“- add a typed v1alpha3-to-v1beta2 relationship bridge for the Go policy engine” meshery/meshery/pull/19100 ↗
Show release-note lines
- [Server] Replace JSON schema-version bridges with typed copies @ritzorama (#19100)
github.com/meshery/meshery/releases/tag/v1.0.19

event_trackers.metadata keys changed to camelCase

Affectsconsumers of affected metadata keys in event_trackers.metadata
Action requiredNo backfill migration is needed.

Affected handlers previously emitted keys such as connection_id, view_link, design_name, and design_id; new event rows use camelCase keys instead. Existing rows retain their legacy keys, and the ?design_id= URL query parameter is unchanged.

Evidence“`event_trackers` is an append-only audit log, so no backfill migration is needed. Old rows remain under their legacy keys as historical records; new rows comply going forward.” meshery/meshery/pull/19099 ↗
Show release-note lines
- fix(events): flip event metadata keys to canonical camelCase @leecalcote (#19099)
github.com/meshery/meshery/releases/tag/v1.0.19

mesheryctl workspace switches to the v1beta3 model

Affectsmesheryctl workspace create, mesheryctl workspace list, and mesheryctl workspace view(Inferred)

Before this release, these commands used the v1beta1 workspace model, with fields such as organization_id and created_at. After upgrading, their workspace data uses the v1beta3 model and camelCase names such as organizationId and createdAt.

Show release-note lines
- [mesheryctl] Align mesheryctl workspace with v1beta3 @PragalvaXFREZ (#19020)
github.com/meshery/meshery/releases/tag/v1.0.19

Meshery UI build moves to Node 22

Affectssetups that build the Meshery UI or use its Node package or Docker build base(Inferred)

The UI package previously accepted Node 20, the Docker build used node:20-alpine, and contributor documentation specified Node 20 LTS. Now the package requires Node ^22.13.0 || >=24, the Docker build uses node:22-alpine, and the documentation specifies Node 22 LTS.

Show release-note lines
- Chore: Upgrade to Node 22 and React 19 @leecalcote (#19083)
- Chore: Upgrade to Node 22 and React 19 @leecalcote (#19083)
- Chore: Upgrade to Node 22 and React 19 @leecalcote (#19083)
github.com/meshery/meshery/releases/tag/v1.0.19

Important fixes4

  • Meshery login redirects preserve requested in-app paths
    AffectsMeshery login flows with in-app destinations, including InitiateLogin and legacy ?ref= callers

    Previously, if an intermediate provider hop dropped or rewrote ref, users could land on Meshery’s nonexistent /login route and get a 404. InitiateLogin now saves the requested path in RefCookieName for TokenHandler to use before falling back to ?ref= and /, then clears the cookie after use.

    - fix(auth): own post-login redirect locally in Meshery via cookie @leecalcote (#19119)
    github.com/meshery/meshery/releases/tag/v1.0.19
  • Empty-slice handling fixed in mesheryctl perf profile paths
    Affectsprofiles with empty loadGenerators or endpoint slices used by mesheryctl perf

    When mesheryctl perf result formatted a profile with no loadGenerators, it could panic; adjacent paths also indexed the first endpoint or load generator directly. The affected lookups now return an empty string for empty slices.

    - [mesheryctl] Fix perf result panic on empty load generators @leecalcote (#19122)
    github.com/meshery/meshery/releases/tag/v1.0.19
  • ConnectionStateChip menu-context runtime error fixed
    AffectsMeshery UI connections flows that render ConnectionStateChip outside a menu context

    Outside menu contexts, wrapping the status chips in MenuItem caused invalid nesting and a MenuListContext runtime error. The error no longer occurs, and chip labels, icons, and colors remain unchanged.

    - fix: /management/connections MUI  MenuList issue @saurabhraghuvanshii (#19132)
    github.com/meshery/meshery/releases/tag/v1.0.19
  • Meshery event-bus payload keys fixed to camelCase
    AffectsSetups using Meshery's event-bus publishers for opening designs or views with the paired meshery-extensions integration

    When the publishers sent view_id while the consumer read viewId, the view ID was undefined at runtime. With the paired meshery-extensions change, both sides use viewId; during a cross-repository version mismatch, events may not be picked up.

    - fix(wire-format): canonicalize OPEN_*_EXTENSIONS event-bus payloads + ViewInfoModal props @leecalcote (#19136)
    github.com/meshery/meshery/releases/tag/v1.0.19

Dependency updates7

    7 more, none mentioning security
    • - [Chore]: Bump meshery/schemas to v1.2.13 @l5io (#19145)
    • - [Chore]: Bump meshery/schemas to v1.2.12 @l5io (#18013)
    • - chore(deps): bump @meshery/schemas ^1.2.12 + @sistent/sistent ^0.21.5 @leecalcote (#19140)
    • - chore(deps): bump @sistent/sistent to ^0.21.4 @leecalcote (#19128)
    • - chore(deps): Bump picomatch from 2.3.1 to 4.0.4 in /ui @[dependabot[bot]](https://github.com/apps/dependabot) (#19101)
    • - [UI] Upgrade to mui-datatables v7.1.0 @ritzorama (#19098)
    • - Chore: Upgrade to Node 22 and React 19 @leecalcote (#19083)
    Other changes20

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