RATATOSK
← All releases

Mesheryv1.0.34

Breaking changes 1Important fixes 4Other changes 11

Get Meshery alerts

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

Breaking changes1

CNCF playground deployment now reconciles its canonical manifest

Affectsthe CNCF playground Deployment managed by cncf-playground-deploy-meshery.yaml
Action requiredThe workflow applies the canonical manifest for the deployed github.sha before setting the release image and checking rollout status.

Previously, the workflow updated only the image, leaving the live pod without PROVIDER=Meshery, so users landed on the provider chooser. At the next release deployment, PROVIDER=Meshery is applied and Meshery is pre-selected; out-of-band cluster edits are overwritten, and the workflow fails if the pod cannot come up.

Evidence“`cncf-playground-deploy-meshery.yaml`: fetch the canonical manifest at the exact `github.sha` being deployed, `kubectl apply` it to reconcile env, then `kubectl set image` to roll the release tag forward, then `rollout status` to fail loudly if the pod can't come up.” meshery/meshery/pull/19748 ↗
Show release-note lines
- [CI] Reconcile playground Deployment env from manifest on every release @leecalcote (#19748)
github.com/meshery/meshery/releases/tag/v1.0.34

Important fixes4

  • Connection-status notifications no longer use a cancelled request context
    AffectsMeshery server connection-status notification flow(Inferred)

    After the HTTP handler returned, its request context was cancelled, causing SendEvent to broadcast a false error and show error toasts despite a successful connection state transition. The goroutine now sends with a context detached from the request lifecycle while retaining values such as TokenCtxKey.

    - fix(server): detach goroutine context in NotifySmOfConnectionStatusChange @ishwar170695 (#19757)
    github.com/meshery/meshery/releases/tag/v1.0.34
  • Docker extension multi-arch UI build failure fixed
    Affectsmulti-architecture Docker extension image builds

    The UI build previously ran under linux/arm64 emulation and crashed with a QEMU Illegal instruction, causing the release build to fail. It now compiles on $BUILDPLATFORM, while the backend and final image still build for the requested target platforms.

    - [Docker] Build docker extension UI on the build platform @[copilot-swe-agent[bot]](https://github.com/apps/copilot-swe-agent) (#19743)
    github.com/meshery/meshery/releases/tag/v1.0.34
  • CRDs tab hook moved to a top-level component
    Affectsthe Meshery dashboard CRDs tab

    The config hook was called inside the parent’s .map() loop under an if (isCRDS) guard, violating the Rules of Hooks. It is now called unconditionally at the top level of CRDsResourcesSubMenu.

    - [UI] Name dashboard resource table-config functions as hooks (fix Rules-of-Hooks in CRDs tab) @marblom007 (#19767)
    github.com/meshery/meshery/releases/tag/v1.0.34
  • Notify Remote Providers dispatches extension builds from master
    AffectsNotify Remote Providers workflow(Inferred)

    Since v1.0.30, tag pushes triggered a 404 when the workflow forwarded the Meshery tag as the dispatch ref and that tag did not exist in the target repository.

    - fix(workflow): set explicit ref on cross-repo workflow dispatch @hamza-mohd (#19742)
    github.com/meshery/meshery/releases/tag/v1.0.34
Other changes11

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