RATATOSK
← All releases

Mesheryv1.0.82

Security 6Breaking changes 6Important fixes 10Enhancements 2Other changes 10

Get Meshery alerts

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

Security6

MeshModelGenerationHandler request-body limits and validation

Affectsrequests to MeshModelGenerationHandler

Previously, the handler read request bodies without a size bound, creating denial-of-service and out-of-memory risk. It now rejects bodies over 4MB with HTTP 413, and returns HTTP 400 for read failures or empty, whitespace-only, null, or empty-data-slice bodies before component generation.

Show release-note lines
- [Server] Bound request body size and guard against DoS in MeshModelGenerationHandler @Supersaiyan101 (#23864)
github.com/meshery/meshery/releases/tag/v1.0.82

Nil provider panics fixed in user test-preference handlers

Affectsserver user test-preference endpoints

When UserTestPreferenceStore, UserTestPreferenceGet, or UserTestPreferenceDelete was invoked with a nil provider, it could dereference nil and panic. These handlers now return a structured ErrNilProvider error with HTTP 500.

Show release-note lines
- [Server] Guard unchecked nil provider dereferences, nil logger panics, and unbounded body reads in UserTestPreference handlers @Amansingh0807 (#23861)
github.com/meshery/meshery/releases/tag/v1.0.82

Oversized UserTestPreferenceStore requests capped

Affectsthe UserTestPreferenceStore endpoint

Previously, the handler could read an oversized request body in full. Bodies over 4 MiB now receive HTTP 413 instead of being fully read and processed.

Show release-note lines
- [Server] Guard unchecked nil provider dereferences, nil logger panics, and unbounded body reads in UserTestPreference handlers @Amansingh0807 (#23861)
github.com/meshery/meshery/releases/tag/v1.0.82

UserTestPreference nil-logger panic fixed

AffectsUserTestPreference handlers that can run with a nil logger(Inferred)

Logging calls on a nil logger could panic in these handlers.

Show release-note lines
- [Server] Guard unchecked nil provider dereferences, nil logger panics, and unbounded body reads in UserTestPreference handlers @Amansingh0807 (#23861)
github.com/meshery/meshery/releases/tag/v1.0.82

UserTestPreferenceHandler now rejects unsupported methods

Affectsthe user test-preference endpoint

When a client sends an unsupported method to the endpoint, it receives a JSON HTTP 405 response.

Show release-note lines
- [Server] Guard unchecked nil provider dereferences, nil logger panics, and unbounded body reads in UserTestPreference handlers @Amansingh0807 (#23861)
github.com/meshery/meshery/releases/tag/v1.0.82

Server-side URL imports restricted to public destinations

AffectsMeshery Server URL imports for designs, filters, or patterns

Private, loopback, link-local, and reserved destinations are blocked, including when reached through redirects. Responses are capped at 10 MiB; filters and patterns allow up to five redirects and 30 seconds, while designs allow up to ten redirects and 60 seconds.

Show release-note lines
- [Server] Restrict filter URL imports to public destinations @itsCodeTide (#23874)
github.com/meshery/meshery/releases/tag/v1.0.82

Breaking changes6

MeshSync flushes preserve cache and resync reports nil handlers

AffectsMeshSync flush actions on Kubernetes connections and ResyncMeshsync() calls

Previously, a flush for a disconnected Kubernetes connection could delete cached resources; it now returns HTTP 409 without deleting them. ResyncMeshsync() returns an explicit error when the MeshSync data handler is nil.

Evidence“Return HTTP `409 Conflict` with a descriptive error when a flush is requested for a disconnected connection.” meshery/meshery/pull/23846 ↗
Show release-note lines
- [Server] Fix MeshSync flush handling for disconnected connections and nil handler @Nixantsingh943 (#23846)
github.com/meshery/meshery/releases/tag/v1.0.82

mesheryctl model search rejects extra positional arguments

Affectsmesheryctl model search(Inferred)

When invoked with extra unquoted positional arguments, such as aws ec2, the command previously searched for aws and exited successfully. It now returns an invalid-argument error; single-argument and quoted multi-word searches continue to work.

Evidence“Keep the existing missing-name error for zero arguments, single-argument searches, and quoted multi-word searches unchanged.” meshery/meshery/pull/22565 ↗
Show release-note lines
- [mesheryctl] Validate model search positional arguments @Karman580 (#22565)
github.com/meshery/meshery/releases/tag/v1.0.82

CLI blocks incomplete performance profile lookups and deletions

AffectsCLI performance profile lookup and deletion(Inferred)

When matching profiles change during traversal or pagination data is inconsistent, the CLI could return partial matches or proceed with deletion. It now returns an error instead and stops deletion.

Evidence“Profiles were added, deleted, or reordered during lookup, or the provider returned inconsistent pagination data” meshery/meshery/pull/22775 ↗
Show release-note lines
- [mesheryctl] Fix profile lookup when paginating performance results @FayezBast (#22775)
- [mesheryctl] Fix profile lookup when paginating performance results @FayezBast (#22775)
github.com/meshery/meshery/releases/tag/v1.0.82

Meshery CLI rejects checks for unconfigured adapters

AffectsMeshery CLI adapter checks in the current context

Previously, when no configured adapter matched the requested name, the command printed “No components configured in current context” and exited 0, so a typo or an adapter that was not deployed looked like a passing check. It now returns an invalid-argument error and exits 1; configured adapters can still be checked by name or location.

Evidence“when a specific adapter was requested and none matched, return `utils.ErrInvalidArgument` with `adapter "<name>" is not configured in the current context`.” meshery/meshery/pull/23849 ↗
Show release-note lines
- [mesheryctl] Fail system check --adapter for an adapter that is not configured @Eternity0207 (#23849)
github.com/meshery/meshery/releases/tag/v1.0.82

mesheryctl Kubernetes log labels now include pod and container names

AffectsKubernetes logs retrieved or followed with mesheryctl(Inferred)

Buffered and streaming log entries use this label, making it clearer which container produced each entry.

Evidence“Prefix Kubernetes logs with both pod and container names in snapshot and follow modes.” meshery/meshery/pull/23847 ↗
Show release-note lines
- [mesheryctl] Include container names in Kubernetes logs @itsCodeTide (#23847)
github.com/meshery/meshery/releases/tag/v1.0.82

Oversized Grafana and Prometheus responses now return errors

AffectsMeshery's Grafana and Prometheus telemetry integrations

When either upstream response exceeded 16 MiB, the clients previously returned the first 16 MiB as a successful response, potentially producing invalid JSON. They now return an explicit error with no partial body, and the telemetry UI displays error details and suggested next steps.

Evidence“This PR fixes Grafana and Prometheus responses over 16 MiB being silently truncated, which could produce invalid JSON.” meshery/meshery/pull/22762 ↗
Show release-note lines
- fix(server):Reject oversized telemetry responses @FayezBast (#22762)
- fix(server):Reject oversized telemetry responses @FayezBast (#22762)
github.com/meshery/meshery/releases/tag/v1.0.82

Important fixes10Silent failure1

  • Wildcard array paths resolved in policy and relationship processingSilent failure
    Affectspolicies or declarative relationships using wildcard paths to target array elements

    Before this fix, forward mutations on array targets could be silently dropped, and deleting a relationship could leave mutated fields stranded in the design document. Wildcard paths are now resolved for matching and mutation, and deletion cleanup can target the same resolved values.

    - [Server] Resolve array wildcard paths during policy mutation and deletion cleanup @nishant-devv (#23670)
    github.com/meshery/meshery/releases/tag/v1.0.82
  • System reset no longer changes the saved current context
    Affectsmesheryctl system reset --context with a context other than the current one(Inferred)

    Previously, resetting X also saved it as current-context, so a context intended for one command remained selected for subsequent commands. Without --context, behavior is unchanged.

    - [mesheryctl] Keep the current context when system reset uses --context @Eternity0207 (#23653)
    github.com/meshery/meshery/releases/tag/v1.0.82
  • Meshery UI query parameter serialization fixed
    AffectsMeshery UI fetchViews requests or urlEncodeArrayParam use for optional or array query parameters

    When optional parameters such as visibility were omitted, array parameters lacked nullish guards and could produce malformed query strings. Affected requests now omit empty query segments, encode array keys and values, avoid malformed ?& prefixes, and leave off the query string when no parameters are present.

    - [UI] Guard urlEncodeArrayParam against undefined input and prevent malformed query strings @madhavzanwar (#23674)
    github.com/meshery/meshery/releases/tag/v1.0.82
  • Nil-provider and nil-user error handling fixed in pattern handlers
    Affectspattern source and clone handlers

    When either handler receives a request while the provider is nil, it returns HTTP 500 instead of reaching a nil-pointer dereference. When the pattern source handler receives a request with a nil user, it returns HTTP 401.

    - [Server] Guard nil provider, validate path UUIDs, and propagate status codes in pattern handlers @patelshivani2283-lab (#23891)
    github.com/meshery/meshery/releases/tag/v1.0.82
  • Pattern handler error statuses now reflect provider errors
    Affectspattern source retrieval, cloning, and download handlers

    When a provider operation returned an error, these handlers previously returned hardcoded HTTP 404 or 500 statuses regardless of the provider error's status. They now return the status from providerStatusOrInternal(err).

    - [Server] Guard nil provider, validate path UUIDs, and propagate status codes in pattern handlers @patelshivani2283-lab (#23891)
    github.com/meshery/meshery/releases/tag/v1.0.82
  • Pattern handler logging guarded against nil loggers
    Affectspattern handlers with a nil h.log logger(Inferred)

    Previously, logger invocations in these handlers were not protected by a nil check.

    - [Server] Guard nil provider, validate path UUIDs, and propagate status codes in pattern handlers @patelshivani2283-lab (#23891)
    github.com/meshery/meshery/releases/tag/v1.0.82
  • Meshery performance profile lookup across pages fixed
    Affectspaginated mesheryctl perf result lookups using --page

    Previously, mesheryctl perf result NAME --page 2 could report an existing profile as missing if it was not on that page. Now profile discovery searches all pages, while results still come from the selected page.

    - [mesheryctl] Fix profile lookup when paginating performance results @FayezBast (#22775)
    github.com/meshery/meshery/releases/tag/v1.0.82
  • Analytics preference switches restore saved values after failed saves
    Affectsanonymous usage statistics or performance results preferences in the Meshery UI

    Previously, when POST /api/user/prefs failed, a switch stayed at a value the server had not stored. While a save is pending, both switches are disabled and further toggles are ignored; successful saves retain the new setting.

    - [UI] Turn analytics preference switches back when saving fails @mayank609 (#23640)
    github.com/meshery/meshery/releases/tag/v1.0.82
  • LazyComponentForm no longer mutates fetched component schemas
    AffectsMeshery UI designs whose LazyComponentForm receives an already-parsed object component schema

    When rawSchema was already an object, downstream property/type normalization could mutate the fetched component object in place. The form now normalizes a shallow copy instead.

    - [UI] Shallow-copy object schema and guard array properties in LazyComponentForm @abhinavkdeval08-design (#23363)
    github.com/meshery/meshery/releases/tag/v1.0.82
  • Shared Meshery Operator lifecycle protected across connections
    AffectsMeshery Server deployments with multiple connections sharing a Kubernetes cluster and using the Meshery Operator

    Before this change, disconnecting or deleting a connection, or switching it to embedded mode, could run helm uninstall and remove the operator used by other connections; simultaneous installs of the same release could race. Those transitions now leave the shared operator installed, and deployments of the same release are serialized per cluster.

    - fix(server): keep Meshery Operator installed across shared-cluster connection lifecycle @yi-nuo426 (#23261)
    github.com/meshery/meshery/releases/tag/v1.0.82

Enhancements2

Other changes10

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