RATATOSK
← All releases

Mesheryv1.0.23

Breaking changes 3Important fixes 12Enhancements 3Dependency updates 2Other changes 134

Get Meshery alerts

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

Breaking changes3

Meshery makes fortio its only load generator

Affectsperformance profiles, saved preferences, API requests, or mesheryctl perf apply configured to use wrk2

wrk2 was previously supported alongside fortio. Existing references to wrk2 are accepted without user-visible errors; saved UI preferences are coerced to fortio when read.

Evidence“fortio is now the sole load generator, so the load-generator value is vestigial on the run path. Existing performance profiles, saved user preferences, and in-flight API requests that still reference "wrk2" are transparently tolerated and run on fortio — **no user-visible errors**.” meshery/meshery/pull/19539 ↗
Show release-note lines
- Remove wrk2 load-generator support completely @ritzorama (#19539)
- Remove wrk2 load-generator support completely @ritzorama (#19539)
- Remove wrk2 load-generator support completely @ritzorama (#19539)
- Remove wrk2 load-generator support completely @ritzorama (#19539)
github.com/meshery/meshery/releases/tag/v1.0.23

Docker edge image publishing removed from the build workflow

Affectssetups consuming edge image tags from the build-ui-and-server.yml workflow(Inferred)

Before this release, qualifying tag builds pushed edge-latest, tag-specific, and commit-specific image tags and updated the Docker Hub description. Those publishing and description-update steps no longer run.

Evidence“Recent unresolved merge conflicts were merged accidently during the fix previously deprecated workflow job was added back to workflow. This PR removes it again.” meshery/meshery/pull/19326 ↗
Show release-note lines
- chore: remove unused Docker push and description steps from CI workflow @ianrwhitney (#19326)
github.com/meshery/meshery/releases/tag/v1.0.23

Nighthawk load-generator and adapter integration removed

Affectssetups using the Nighthawk load generator or adapter, including its Compose service or Helm subchart

Meshery previously included a meshery-nighthawk Compose service and Helm subchart; those and the integration’s server entries are no longer included.

Evidence“Drops the Nighthawk load generator and adapter integration from across the Meshery codebase.” meshery/meshery/pull/19463 ↗
Show release-note lines
- Remove Nighthawk load generator integration @hortison (#19463)
- Remove Nighthawk load generator integration @hortison (#19463)
- Remove Nighthawk load generator integration @hortison (#19463)
github.com/meshery/meshery/releases/tag/v1.0.23

Important fixes12Silent failure1

  • Kubernetes context badge and menu positioning fixed
    Affectsheader Kubernetes context switcher displaying contexts

    Before the context subscription fired, the badge showed an undefined count and the menu position stayed based on the initial zero count. The badge now gets totalCount from the subscription and initial state, and menu positioning reflects the current contexts from mount onward.

    - [UI] Realign k8s context switcher on totalCount across the data path @leecalcote (#19391)
    github.com/meshery/meshery/releases/tag/v1.0.23
  • Kubernetes switcher badge connection count corrected
    AffectsKubernetes context switcher

    When subscribed Kubernetes context data was stored in UI state, it was not normalized, so the badge could show a count that differed from the actual connection count. It now reads the actual count from normalized subscription data.

    - [UI] Fix k8s context switcher count @miacycle (#19381)
    github.com/meshery/meshery/releases/tag/v1.0.23
  • getDuplicateComponents request query handling fixed
    AffectsUI/API flows that use getDuplicateComponents

    Previously, requests used ?apiVersion=v1&?model=k8s, so the backend treated model as a different query key. Requests now use the correct model key and URL-encode special characters.

    - test(ui): comprehensive Vitest + React Testing Library coverage @leecalcote (#19359)
    - test(ui): comprehensive Vitest + React Testing Library coverage @leecalcote (#19359)
    github.com/meshery/meshery/releases/tag/v1.0.23
  • System event persistence fixed in EventsPersisterSilent failure
    Affectssetups that persist system events through EventsPersister.PersistEvent

    System events emitted through MesheryControllersHelper.emitEvent were silently dropped because PersistEvent passed a struct value to GORM's Save, which requires a pointer. Those events can now be persisted.

    - [UI][Server] Stop /management/connections React #185, silent event drops, log noise @miacycle (#19282)
    github.com/meshery/meshery/releases/tag/v1.0.23
  • Updated schema versions in mesheryctl model init scaffolds
    Affectsscaffold generation with mesheryctl model init

    When creating scaffolds for new integrations, generated files previously contained deprecated snake_case keys and could fail the meshery/schemas consumer-audit CI gate. They now use model constructs from v1beta2 and component and relationship templates from v1beta3, with top-level wire keys such as registrantId and componentsCount in camelCase.

    - [mesheryctl] model init: use v1beta2 schema constructs for scaffold generation @YASHMAHAKAL (#19409)
    - [mesheryctl] model init: use v1beta2 schema constructs for scaffold generation @YASHMAHAKAL (#19409)
    github.com/meshery/meshery/releases/tag/v1.0.23
  • Connection table imports corrected and MUI icons replaced
    Affectsbuilds or UI deployments that include the connections table and action menu

    After the Phase 4 kebab-case rename, stale PascalCase sibling paths broke builds on case-sensitive CI/Linux systems. Direct MUI icon imports had also raised the audit:mui count from zero to two, and the action menu used SyncIcon; the menu now uses Sistent SyncAltIcon, and the MUI audit returns to zero matches.

    - fix(ui): ConnectionTable sibling icon + folder-casing cleanup; audit:mui back to 0 @hamza-mohd (#19366)
    github.com/meshery/meshery/releases/tag/v1.0.23
  • Null and undefined crash fixes in Meshery UI views
    Affectsfilters, ConfigMap columns, Kubernetes DaemonSet/Deployment/Pod columns, and adapter SMI conformance results

    These views could crash when the unpublish-handler factory returned undefined, a ConfigMap value was "null", Kubernetes resource fields or containers were null or undefined, or an SMI result lacked its nested details. Those accesses are now guarded, and the SMI details list defaults to [] when details are absent.

    - fix(ui): address critical/high Gemini feedback across Phase 2/3/5.a PRs @hamza-mohd (#19364)
    github.com/meshery/meshery/releases/tag/v1.0.23
  • Design action naming and filter operation fixes
    Affectsdesign actions and filter catalog unpublishing or deletion(Inferred)

    Design actions now use the name parameter instead of reading data.name from a YAML string, which always yielded undefined; UNPUBLISH_CATALOG now has the correct name and error text instead of reusing the publish text. Filter deletion checks for id before calling deleteFilterFile, which requires it.

    - fix(ui): address critical/high Gemini feedback across Phase 2/3/5.a PRs @hamza-mohd (#19364)
    github.com/meshery/meshery/releases/tag/v1.0.23
  • Provider capability payloads normalized for navigator checks
    AffectsMeshery UI instances receiving provider /capabilities payloads and using navigator capability checks

    Previously, when navigator code read a non-array capabilities value from a CapabilitiesRegistry instance rather than directly from the provider payload, the UI could crash with e?.capabilities?.some is not a function. Non-array values now normalize to [], avoiding that .some type crash.

    - ui: guard provider capabilities in navigator @hortison (#19337)
    github.com/meshery/meshery/releases/tag/v1.0.23
  • MenuListContext error fixed in shared select wrappers
    Affectsshared ReactSelectWrapper and MultiSelectWrapper components

    Both wrappers used MenuItem outside the menu context, causing a MenuListContext error. They now use ListItemButton for options while preserving styling and selection behavior.

    - [UI] Fix MenuListContext error in select wrappers @miacycle (#19279)
    github.com/meshery/meshery/releases/tag/v1.0.23
  • Component and relationship detail endpoints resolve from the API root
    AffectsUI/API flows using getComponentsDetail or getRelationshipsDetail

    Before this change, these paths resolved relative to the current page instead of the API root when either function was used.

    - test(ui): comprehensive Vitest + React Testing Library coverage @leecalcote (#19359)
    github.com/meshery/meshery/releases/tag/v1.0.23
  • Connections page render-loop crash fixed
    Affectsthe /management/connections page

    When the pages-router reassigned query and push during rerenders, updateUrlWithConnectionId was recreated, causing setState loops and React error #185 (Maximum update depth exceeded). Its identity is now preserved across renders, preventing the loop and page crash.

    - [UI][Server] Stop /management/connections React #185, silent event drops, log noise @miacycle (#19282)
    - [UI][Server] Stop /management/connections React #185, silent event drops, log noise @miacycle (#19282)
    github.com/meshery/meshery/releases/tag/v1.0.23

Enhancements3

Dependency updates2

    2 more, none mentioning security
    • - [Chore]: Bump meshery/schemas to v1.2.20 @l5io (#19540)
    • - chore(deps): bump @babel/plugin-transform-modules-systemjs from 7.28.5 to 7.29.4 in /install/docker-extension/ui @[dependabot[bot]](https://github.com/apps/dependabot) (#19205)
    Other changes134

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