RATATOSK
← All releases

Mesheryv1.0.81

Breaking changes 2Important fixes 15Enhancements 1Dependency updates 1Other changes 3

Get Meshery alerts

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

Breaking changes2

SMP load tests now cover every configured endpoint

AffectsProfile load tests using SMP configurations with multiple clients or endpoint URLs(Inferred)
Action requiredEvery URL must be valid, and each client must have endpoint URLs; otherwise, the request returns 400 before tests start.

Previously, the handler tested only the first client and endpoint, silently dropping the others. It now tests every configured endpoint sequentially from the Meshery Server, identifies each result by endpoint, and continues with remaining endpoints if one fails.

Show release-note lines
- [Server] Run load tests against every configured endpoint URL @RameshwariS (#23822)
github.com/meshery/meshery/releases/tag/v1.0.81

Kubernetes context requests now return HTTP 404 for missing contexts

AffectsKubernetes context lookup and deletion endpoints

When a request targets a context ID that does not exist, GetContext previously returned HTTP 500, and DeleteContext returned HTTP 500 while logging an error event. Genuine database failures still return HTTP 500.

Evidence“In `DeleteContext` (`DELETE /api/system/kubernetes/contexts/{id}`), checks for not-found errors when retrieving the target context and returns `models.ErrResultNotFound(err)` with HTTP 404 Not Found instead of logging an error event and returning HTTP 500.” meshery/meshery/pull/23824 ↗
Show release-note lines
- [Server] Return 404 Not Found for non-existent Kubernetes context in GetContext and DeleteContext @patelshivani2283-lab (#23824)
github.com/meshery/meshery/releases/tag/v1.0.81

Important fixes15

  • Environment deletion detection fixed for undefined deletedAt
    Affectsenvironment cards with deletedAt set to undefined or null

    When deletedAt was undefined, including when omitted, the environment was treated as deleted and its bulk-selection checkbox was disabled. Now undefined or null values are treated as active, keeping the checkbox enabled.

    - [UI] Deduplicate connection transfer lists and fix active environment… @harmanD-MAX (#23820)
    github.com/meshery/meshery/releases/tag/v1.0.81
  • Duplicate connection chips in environment assignments fixed
    Affectsconnection-assignment lists on the Environments page

    When fetched pages or refetched results were accumulated, records with duplicate id values could add duplicate chips to the displayed assignment list. Accumulated lists now keep only one entry per id, including when the modal is reopened or data is refetched.

    - [UI] Deduplicate connection transfer lists and fix active environment… @harmanD-MAX (#23820)
    github.com/meshery/meshery/releases/tag/v1.0.81
  • Connection-assignment modal state reset
    Affectsthe connection-assignment modal on the Environments page

    When the modal was closed or reopened, previous connection lists, pagination, or assigned selections could carry over and leave incorrect connection state without an error. Both actions now clear the lists and selections, reset pagination, and disable the transfer button.

    - [UI] Deduplicate connection transfer lists and fix active environment… @harmanD-MAX (#23820)
    github.com/meshery/meshery/releases/tag/v1.0.81
  • Connection-assignment pagination and transfer-list counts corrected
    Affectsconnection-assignment lists on the Environments page for assignable or already assigned connections

    Pagination could advance before the current page had accumulated, and reopening or refetching could leave duplicate records while counts used the server’s totalCount. Now pages cannot be advanced past before they accumulate, and after all pages load, transfer-list counts use the deduplicated accumulated list length.

    - [UI] Deduplicate connection transfer lists and fix active environment… @harmanD-MAX (#23820)
    github.com/meshery/meshery/releases/tag/v1.0.81
  • Nil logger checks added to GetContext and DeleteContext error logging
    Affectssetups where GetContext or DeleteContext has a nil logger(Inferred)
    - [Server] Return 404 Not Found for non-existent Kubernetes context in GetContext and DeleteContext @patelshivani2283-lab (#23824)
    github.com/meshery/meshery/releases/tag/v1.0.81
  • Kubernetes discovery and ping hangs fixed
    AffectsKubernetes cluster discovery and version lookups without an incoming context deadline

    Probes could hang when they reached unreachable, firewalled, or private cluster endpoints. These discovery and ping version lookups now fail fast after a 5-second bound.

    - [Server] Add timeout bounds and context propagation for Kubernetes cluster discovery @harmanD-MAX (#23812)
    github.com/meshery/meshery/releases/tag/v1.0.81
  • Kubernetes discovery probe cancellation fixed
    AffectsKubernetes context discovery from requests, including kubeconfig discovery handlers

    When a client aborted a request while discovery probes were running, the probes continued because they used background contexts. Now the abort stops in-flight and subsequent cluster network probes.

    - [Server] Add timeout bounds and context propagation for Kubernetes cluster discovery @harmanD-MAX (#23812)
    github.com/meshery/meshery/releases/tag/v1.0.81
  • Nil-pointer panic fixed in RedactCredentialsForContext
    Affectscallers of RedactCredentialsForContext

    Passing nil to RedactCredentialsForContext caused a runtime panic. It now returns without dereferencing a nil K8sContext pointer.

    - [Server] Consolidate K8sContext credential redaction helpers and guard nil input @Supersaiyan101 (#23799)
    github.com/meshery/meshery/releases/tag/v1.0.81
  • mesheryctl SafeClose panic handling fixed
    Affectsresource-closing paths in mesheryctl that use SafeClose

    Passing a nil or typed-nil io.Closer, or getting a close error while Log is nil, could panic. Now nil closers are skipped, close errors do not panic when Log is nil (but are not logged), and valid closers are still closed; errors are logged when Log is initialized.

    - [mesheryctl] Make SafeClose nil-safe and handle uninitialized logger @muskan-creates352 (#23830)
    github.com/meshery/meshery/releases/tag/v1.0.81
  • JSON null version response no longer crashes mesheryctl system check
    Affectsmesheryctl system check

    When /api/system/version returned JSON null, the command panicked with a nil pointer dereference. It now reports an error and does not compare an empty version with the latest release.

    - [mesheryctl] Report a null server version in system check instead of panicking @Shikhyy (#23817)
    github.com/meshery/meshery/releases/tag/v1.0.81
  • Missing component models no longer crash listing
    Affectscomponents with a null or absent model in mesheryctl component list

    A component with "model": null previously caused a nil-pointer panic. It now appears with N/A for both its model name and version.

    - [mesheryctl] Show N/A for a component with no model in component list @Shikhyy (#23818)
    github.com/meshery/meshery/releases/tag/v1.0.81
  • mesheryctl design apply null-response panic fixed
    Affectsmesheryctl design apply <name>

    When the design lookup returned JSON null, the command previously panicked with a nil pointer dereference. It now handles that response like an empty list and reports ErrDesignNotFound.

    - [mesheryctl] Treat a null design lookup as not found in design apply @Shikhyy (#23816)
    github.com/meshery/meshery/releases/tag/v1.0.81
  • JSON null handling fixed in mesheryctl filter list
    Affectsmesheryctl filter list

    When the server returned JSON null, the command panicked with a nil pointer dereference, both with and without --count. It now displays No WASM Filter to display, or No filters found with --count.

    - [mesheryctl] Treat a null response as no filters in filter list @Shikhyy (#23815)
    github.com/meshery/meshery/releases/tag/v1.0.81
  • JSON null handling fixed in performance commands
    Affectsmesheryctl perf profile and mesheryctl perf result

    When either command receives a JSON null reply from the server or another response source, it no longer panics with a nil pointer dereference; it returns an empty page without an error.

    - [mesheryctl] Treat a null response as an empty page in perf profile and perf result @Shikhyy (#23814)
    github.com/meshery/meshery/releases/tag/v1.0.81
  • Model initialization panic on invalid --path fixed
    Affectsmodel initialization with --path set to a regular file or a path below one

    During model-folder checks, these paths made os.Stat return ENOTDIR with no FileInfo, causing a panic. The command now reports an actionable error identifying the unusable path.

    - [mesheryctl] Handle non-directory --path in model init @hemv-857 (#23805)
    github.com/meshery/meshery/releases/tag/v1.0.81

Enhancements1

Dependency updates1

    1 more, none mentioning security
    • - chore: bump meshery/schemas to v1.3.120 @leecalcote (#23826)
    Other changes3

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