Security22(Security status unclear2)
Kubernetes context credentials redacted from GetContext responses
Affectssetups using the GetContext endpoint (GET /api/system/kubernetes/contexts/{id})
Before this change, the endpoint exposed authentication and cluster values—including private keys, certificates, and bearer tokens—in plain text over HTTP. Responses now omit those credentials while retaining context identifiers and public endpoint metadata.
Show release-note lines
- [Server] Redact sensitive auth credentials in GetContext HTTP response @Supersaiyan101 (#23797)
github.com/meshery/meshery/releases/tag/v1.0.80Credential deletion now enforces ownership
Affectscredential deletion through DefaultLocalProvider
Additional actiona valid authenticated user
Previously, deletion matched only the credential ID, so a request targeting another user’s credential could remove it without checking ownership. Now, attempts to delete another user’s credential or delete without a valid identity return not-found and leave the credential intact.
Show release-note lines
- [Server] Enforce user ownership validation in credential get and delete @Supersaiyan101 (#23661)
github.com/meshery/meshery/releases/tag/v1.0.80Meshery SSE stream timeouts fixed
AffectsMeshery load-test SSE stream, /api/providers/stream, and /api/system/adapter/events
Load-test runs of two minutes or more could lose their final result frame, while the providers and adapter-events streams were cut off every two minutes. These streams can now continue beyond two minutes, with a fresh 30-second write deadline for each frame.
Show release-note lines
- [Server] Stop the HTTP server timeouts from cutting off SSE streams and slow uploads @SandstromPL (#23634)
github.com/meshery/meshery/releases/tag/v1.0.80Token-file permissions tightened
AffectsWindows mesheryctl token files and token files created on non-Windows platforms
On Windows, existing token files with broader access are restricted to the current user, and updates use a private temporary file. If access restrictions cannot be verified or an update fails, an error is reported and the existing token remains unchanged; newly created non-Windows token files use mode 0600.
Show release-note lines
- fix: restrict Windows token file permissions @0xmaster7 (#23380)
github.com/meshery/meshery/releases/tag/v1.0.80Unsafe export paths fixed in mesheryctl design export
Affectsdesigns exported with mesheryctl design export
Names containing /, \, or ../ could create subdirectories or write the export outside --output. Unsafe characters now become _, keeping the file directly inside --output; already-safe names such as my-design keep the same filename.
Show release-note lines
- [mesheryctl] sanitize the design name in design export file paths @rakesh0x (#23557)
github.com/meshery/meshery/releases/tag/v1.0.80Undefined token assignments rejected by mesheryctl
Affectsmesheryctl system token set assignments using names absent from tokens:
Previously, system token set <name> saved names without a matching tokens: entry, so a subsequent request could send the default token to that context's server. Now the command returns an error and leaves the context unchanged.
Show release-note lines
- [mesheryctl] Reject unknown tokens in token set and in-use tokens in token delete @Asheesh7298 (#23457)
- [mesheryctl] Reject unknown tokens in token set and in-use tokens in token delete @Asheesh7298 (#23457)
github.com/meshery/meshery/releases/tag/v1.0.80Windows token files restricted to the current user
AffectsWindows mesheryctl token files
Previously, Chmod(0600) did not remove existing or inherited ACLs, so token files in shared directories could remain readable by other users. Writes and rewrites through WriteTokenFile now apply a protected ACL for the current user's SID, leaving the previous token intact if the restriction fails; Unix behavior is unchanged.
Show release-note lines
- [mesheryctl] Enforce owner-only token file on Windows via explicit DACL @Pastoray (#23507)
- [mesheryctl] Enforce owner-only token file on Windows via explicit DACL @Pastoray (#23507)
github.com/meshery/meshery/releases/tag/v1.0.80Nil-provider and logger panics fixed in performance profile endpoints
Affectsperformance profile endpoints
A missing or typed-nil provider, or an unavailable handler logger, could cause a server panic when an endpoint handled a request. Missing providers now receive an ErrNilProviderCode 500 response, and guarded logger calls no longer panic.
Show release-note lines
- [Server] Guard nil provider and nil logger in performance profile handlers @antcybersec (#23772)
github.com/meshery/meshery/releases/tag/v1.0.80Docker Extension proxy authentication-token log exposure fixed
AffectsDocker Extension proxy request and backend-error logging(Inferred)
Authentication tokens were exposed in request and backend-error logs. They are now redacted from those logs, including when query parameters are malformed; the delete path also no longer logs the empty token or channel.
Show release-note lines
- [Docker Extension] Don't hang token store and logout when no websocket client is connected @CyberRik (#23765)
github.com/meshery/meshery/releases/tag/v1.0.80Nil-pointer panics fixed in MeshSync endpoints
Affectsthe four MeshSync endpoints
Nil or uninitialized providers or persisters, and unavailable logger paths, could cause nil-pointer panics in these handlers. Missing providers or persisters now produce a 500 ErrNilProviderCode response, nil logger paths no longer panic, and malformed inputs or missing query parameters still receive validation errors.
Show release-note lines
- [Server] Guard nil provider, persister, and logger across MeshSync handlers @antcybersec (#23770)
github.com/meshery/meshery/releases/tag/v1.0.80Nil-provider and logger panics fixed in schedule and organization handlers
Affectsschedule endpoints and GetOrganizations
When these handlers encountered a nil provider, including a typed nil provider, or made logger calls with an uninitialized logger, they could panic. Those paths no longer panic, while malformed schedule requests and missing schedule IDs retain appropriate error responses.
Show release-note lines
- [Server] Guard nil provider and nil logger in schedule and organization handlers @antcybersec (#23768)
github.com/meshery/meshery/releases/tag/v1.0.80Nil-dereference panics in EvaluateRelationshipPolicy fixed
Affectsrelationship policy evaluation
When a user or provider was missing, h.SystemID was nil, or h.evalTracker was uninitialized, the handler could panic on nil dereferences. It now returns HTTP 401 for a missing user and HTTP 500 for a missing provider, falls back to uuid.Nil for a nil system ID, and initializes a nil evaluation tracker.
Show release-note lines
- [Server] Guard unchecked nil dereferences, unbounded body reads, and detached goroutine panics in EvaluateRelationshipPolicy @Amansingh0807 (#23664)
github.com/meshery/meshery/releases/tag/v1.0.80EvaluateRelationshipPolicy request body limits enforced
Affectsrequests to EvaluateRelationshipPolicy
Previously, bodies over 4 MB were read without a size cap, risking memory exhaustion, and empty bodies were not specially rejected before JSON decoding. Now, oversized bodies receive HTTP 413 and empty bodies receive HTTP 400.
Show release-note lines
- [Server] Guard unchecked nil dereferences, unbounded body reads, and detached goroutine panics in EvaluateRelationshipPolicy @Amansingh0807 (#23664)
github.com/meshery/meshery/releases/tag/v1.0.80Credential GET ownership verification added
Affectscredential GET requests through DefaultLocalProvider
Previously, GetUserCredentialByID returned credentials without checking whether credential.UserId matched the authenticated caller's user.ID, allowing another user's credential to be disclosed. Now, requests for another user's or an unowned credential, or requests without a resolved caller identity, return 404.
Show release-note lines
- [Server] Enforce user ownership validation in credential get and delete @Supersaiyan101 (#23661)
github.com/meshery/meshery/releases/tag/v1.0.80Nil-provider panic in GetUsersKeys fixed
Security status unclearAffectsrequests handled by GetUsersKeys
When provider initialization faults or a request reaches the handler during boot, a nil provider previously caused a nil-pointer panic that could take down the server. Such requests now receive HTTP 500 with ErrNilProvider() instead of crashing the process.
Show release-note lines
- fix(server): guard nil provider and validate org ID in GetUsersKeys @hemv-857 (#23645)
github.com/meshery/meshery/releases/tag/v1.0.80ValidationHandler oversized-request crash fixed
Affectsthe /api/registry/validate and /api/meshmodels/validate endpoints
Previously, oversized requests could be read without a limit and cause OOMKilled crashes. Requests over 4 MB now receive HTTP 413 instead of being read without a bound.
Show release-note lines
- [Server] Bound request body size and guard against DoS in ValidationHandler @Supersaiyan101 (#23589)
github.com/meshery/meshery/releases/tag/v1.0.80ValidationHandler returns HTTP 400 for invalid requests
Affectsthe /api/registry/validate and /api/meshmodels/validate endpoints
Client read failures previously returned HTTP 500. Standard JSON whitespace is trimmed before validation.
Show release-note lines
- [Server] Bound request body size and guard against DoS in ValidationHandler @Supersaiyan101 (#23589)
github.com/meshery/meshery/releases/tag/v1.0.80DeleteConnection UUID validation and nil-reference handling
Affectsthe DeleteConnection endpoint
Before this change, malformed or nil connection UUIDs lacked boundary validation, and missing user, provider, or system information could cause dereference panics. Now malformed or nil UUIDs return HTTP 400; nil-provider requests return HTTP 500, while missing user or system information no longer causes those panics.
Show release-note lines
- [Server] Validate connection ID and guard nil dereference in DeleteConnection @Supersaiyan101 (#23404)
github.com/meshery/meshery/releases/tag/v1.0.80Nil-provider handling fixed for extension operations
Affectsextension install/remove handlers and capability persistence
When an unauthenticated request reached an install or remove handler during partial server bootstrap with no provider, the unchecked dereference could panic and terminate the server. The handlers now return HTTP 500 in that case, and capability persistence safely skips calls with a nil provider.
Show release-note lines
- [Server] Guard nil provider dereference and unbounded body reads in extension install and remove handlers @Amansingh0807 (#23395)
github.com/meshery/meshery/releases/tag/v1.0.80Extension handlers reject oversized bodies and avoid nil-provider panics
Affectsextension installation and removal
Previously, reaching either handler without an initialized provider—including through unauthenticated access or during partial server bootstrap—caused an unhandled panic that terminated the server, and request bodies were read without a size bound. Now, bodies over 4 MB receive HTTP 413, and request bodies are closed.
Show release-note lines
- [Server] Guard nil provider dereference and unbounded body reads in extension install and remove handlers @Amansingh0807 (#23395)
github.com/meshery/meshery/releases/tag/v1.0.80mesheryctl token-file writes support long paths on Windows
AffectsWindows setups writing token files to long paths
Show release-note lines
- fix: restrict Windows token file permissions @0xmaster7 (#23380)
github.com/meshery/meshery/releases/tag/v1.0.80MeshSync watched-resource access restored
Security status unclearAffectsMeshery Operator Helm chart installations with MeshSync running in operator mode
Additional actionmeshsync.serviceAccount.dedicated enabled
Previously, MeshSync received forbidden errors on watched resources, breaking discovery. It now gets read access, including open-ended list/watch access for CRDs; with the default shared ServiceAccount, it still has the operator’s write permissions.
Show release-note lines
- [Helm] Give MeshSync read-only RBAC, expose Broker service values, clean up CRs on uninstall @yi-nuo426 (#23259)
github.com/meshery/meshery/releases/tag/v1.0.80Breaking changes34
Cloned filters get fresh metadata
Affectsfilter cloning with the Local provider(Inferred)
When the Local provider clones a filter, the clone previously inherited the source’s created_at and catalog_data. It now gets its own creation time and no catalog data, while retaining the source’s file, resource, and location.
Evidence“The copy +// keeps the source's file, resource and location, but gets its own creation +// time and no catalog data.” meshery/meshery/pull/23451 ↗ Show release-note lines
- [Server] Clone designs and filters as fresh records @Asheesh7298 (#23451)
github.com/meshery/meshery/releases/tag/v1.0.80Pattern-resource lookups exclude deleted records and report missing records as not found
Affectspattern-resource lookups by ID or attributes
Previously, missing records from ID and attribute lookups were not mapped to not-found, and ID lookups could include soft-deleted records. Other database errors are now reported as read errors.
Evidence“Pattern resource lookups now exclude deleted records and distinguish missing records from database errors.” meshery/meshery/pull/23667 ↗ Show release-note lines
- [Server] Harden pattern resource persistence @0xmaster7 (#23667)
github.com/meshery/meshery/releases/tag/v1.0.80Pattern-resource deletion returns not-found for missing or deleted resources
Affectspattern-resource deletion
This occurs when a delete request targets a missing or already soft-deleted ID and the update affects no rows.
Evidence“Deleting a resource that is missing or already deleted now returns a not-found error.” meshery/meshery/pull/23667 ↗ Show release-note lines
- [Server] Harden pattern resource persistence @0xmaster7 (#23667)
github.com/meshery/meshery/releases/tag/v1.0.80Kubernetes context deletion stops on snapshot-loading errors
AffectsKubernetes context deletion
Previously, if the Kubernetes context-list snapshot could not be loaded, the handler returned HTTP 200 and started the delete transition anyway. Now it returns HTTP 500 before deletion starts, allowing the caller to retry.
Evidence“A failed Kubernetes context snapshot previously logged an error but returned 200 and started the delete transition without a usable list. The handler now reports the snapshot error before starting deletion, allowing the caller to retry.” meshery/meshery/pull/23613 ↗ Show release-note lines
- [Server] Report context snapshot failures before deletion @0xmaster7 (#23613)
github.com/meshery/meshery/releases/tag/v1.0.80Context deletion now returns explicit HTTP responses
Affectscontext deletion through DELETE /api/system/kubernetes/contexts/{id}
Previously, successful deletion sent no status or body; if machine initialization failed, the handler logged and persisted an error event but sent no response. It now returns HTTP 200 on success and HTTP 500 with ErrFailToDelete on initialization failure.
Show release-note lines
- [Server] Write HTTP status 200 and error response in DeleteContext @nishant-devv (#23563)
github.com/meshery/meshery/releases/tag/v1.0.80Request-body limits and validation for SavePerformanceProfileHandler
Affectsperformance profile save requests
Bodies over 4 MB could previously be silently truncated; they now receive HTTP 413. Empty, whitespace-only, and null payloads receive HTTP 400.
Evidence“Enforced defensive checks against empty, whitespace-only, and `"null"` payloads with `ErrRequestBody` (`HTTP 400 Bad Request`).” meshery/meshery/pull/23561 ↗ Show release-note lines
- [Server] Guard invalid UUID status codes, missing 404 responses, and unchecked token extraction in performance profile handlers @Amansingh0807 (#23561)
github.com/meshery/meshery/releases/tag/v1.0.80Missing performance-profile deletions now return HTTP 404
Affectsperformance-profile deletion
Action requiredNo error-code regeneration or schema change is required.
Previously, deleting an ID that was never stored locally could return HTTP 200 with a stub profile, falsely indicating success. A provider-reported missing profile also now returns HTTP 404.
Show release-note lines
- [Server] Return 404 when deleting a performance profile that does not exist @Shikhyy (#23544)
github.com/meshery/meshery/releases/tag/v1.0.80Preference persister input validation and missing-delete handling
Affectspreference writes and deletes through SessionPreferencePersister(Inferred)
Before this release, writes could panic with an uninitialized database handler, an empty userID, or nil preference data; deleting a preference that did not exist could return silent nil and appear successful as HTTP 200. Those write inputs are now checked before database queries, and deleting a missing preference returns ErrResultNotFound.
Evidence“`DeleteFromPersister` now verifies `res.RowsAffected == 0` and returns `ErrResultNotFound` when the target preference does not exist instead of returning silent `nil` (200 OK).” meshery/meshery/pull/23536 ↗ Show release-note lines
- [Server] Guard nil database handler, validate userID, and check rows affected in preference persister @piyxsh31 (#23536)
github.com/meshery/meshery/releases/tag/v1.0.80HTTP 404 handling for missing environments
Affectsenvironment records
Previously, updating a nonexistent environment ID could silently create a row, while get, update, and delete requests for missing IDs could return 500 or 502. Now these requests return 404, and an update leaves the environment absent.
Show release-note lines
- [Server] Honour Environment purpose property and align SystemDatabaseModels to v1beta3 @SachinyadavAug20 (#23429)
github.com/meshery/meshery/releases/tag/v1.0.80404 responses for credential updates and deletes with no live match
Affectscredential update and delete requests
Previously, updating an already-deleted credential could return 200 without changing it, while repeating a delete returned 200 and changed deleted_at; an unknown ID could produce 500. Repeated deletes now leave the original deletion record unchanged.
Evidence“On the local provider, `UpdateUserCredential` filtered its update on `deleted_at is NULL` but read the row back without it, so updating a deleted credential matched nothing and still returned the deleted row. The handler answered 200 and nothing changed. `DeleteUserCredential` matched by id only, so a second delete also answered 200 and moved `deleted_at`. An id that never existed came back as a bare `record not found`, which the handlers turned into a 500.” meshery/meshery/pull/23503 ↗ Show release-note lines
- [Server] Return 404 when updating or deleting a missing credential @cortex36a (#23503)
github.com/meshery/meshery/releases/tag/v1.0.80Connection actions now reject invalid IDs and handle missing data safely
AffectsPOST /api/integrations/connections/{connectionId}/actions
Previously, malformed or empty IDs were converted with uuid.FromStringOrNil, and absent provider, user, or system data could cause panics during MeshSync actions. Now malformed or nil IDs return HTTP 400, an unavailable provider returns HTTP 500, and actions with missing user or system data continue without a dereference panic.
Evidence“Guards `provider == nil` before executing `setMeshsyncDeploymentModeAction` or `flushMeshsyncAction`, returning HTTP 500 with `"provider not initialized"` rather than panicking” meshery/meshery/pull/23417 ↗ Show release-note lines
- [Server] Validate connection ID and guard nil dereferences in PerformConnectionAction @piyxsh31 (#23417)
github.com/meshery/meshery/releases/tag/v1.0.80mesheryctl perf result uses the configured command output writer
Affectsmesheryctl perf result setups with a configured command output writer(Inferred)
Previously, expanded results and their formatter wrote to raw stdout, even when the configured command output writer was different. After the change, that output goes to the configured writer instead.
Evidence“Routed expanded result outputs and the output formatter to `cmd.OutOrStdout()` instead of raw `fmt.Printf` / `os.Stdout`.” meshery/meshery/pull/23729 ↗ Show release-note lines
- [mesheryctl] Guard nil TestStartTime, fix dead check, and standardize timestamp in perf result (#23727) @muskan-creates352 (#23729)
github.com/meshery/meshery/releases/tag/v1.0.80Remote design imports use URL-path basenames by default
Affectsremote design imports without an explicit --name
Action requiredA remote URL whose path has no filename requires an explicit --name.
Query strings and fragments are excluded from the derived name, while the full URL is still sent with the request.
Evidence“Derive the default name for remote imports from the URL path, excluding query and fragment while keeping the URL intact for the request.” meshery/meshery/pull/23703 ↗ Show release-note lines
- [mesheryctl] Exclude URL query from imported design name @0xmaster7 (#23703)
github.com/meshery/meshery/releases/tag/v1.0.80Log pod selection now prioritizes exact and cleaned-name matches
Affectsmesheryctl log pod selection by specified pod name
Previously, a name matching multiple pods could silently select the first substring match, even if it was not the intended pod. Exact or cleaned-name matches can now select a different pod without an error; multiple matches at the highest priority and missing pods return errors.
Evidence“Prefer exact pod names and exact cleaned names over substring matches when selecting logs. Report ambiguous matches instead of silently selecting the first pod.” meshery/meshery/pull/23666 ↗ Show release-note lines
- [mesheryctl] Resolve log pod names unambiguously @0xmaster7 (#23666)
github.com/meshery/meshery/releases/tag/v1.0.80Filter name searches now prompt on ambiguous matches and error on no matches
Affectsfilter name searches with mesheryctl filter view
Previously, multiple matches opened the first result automatically, while no matches logged a not-found message and returned success.
Show release-note lines
- fix(mesheryctl): select filters by full name @0xmaster7 (#23580)
github.com/meshery/meshery/releases/tag/v1.0.80Filter-name search now retrieves results across pages
Affectsfilter-name searches with mesheryctl filter view
Previously, the search selected from the API’s default-sized result page, and a search with no matches could silently succeed. Now it prompts when multiple filters match, returns a typed not-found error when none match, and reports errors if results cannot be fetched or are incomplete.
Evidence“Searches can retrieve results across multiple pages, and report errors when results cannot be fetched or are incomplete.” meshery/meshery/pull/23580 ↗ Show release-note lines
- fix(mesheryctl): select filters by full name @0xmaster7 (#23580)
github.com/meshery/meshery/releases/tag/v1.0.80Method-changing redirects refused by utils.MakeRequest
Affectsmesheryctl requests made through utils.MakeRequest
When a DELETE, POST, or PUT received a 301, 302, or 303, the client could resend it as a bodyless GET; a GET route at the destination could run and the command could report success without performing the original operation. These redirects are now refused: most return ErrRedirectChangesMethod, while refused 302 redirects return ErrInvalidToken; redirects that preserve the method remain followed.
Evidence“`utils.MakeRequest` used a default `http.Client{}`. net/http answers a 301, 302 or 303 to a DELETE, POST or PUT by re-sending the request as a GET without its body. When the new path also has a GET route, the GET runs and the command reports success.” meshery/meshery/pull/23405 ↗ Show release-note lines
- [mesheryctl] Report a method-changing redirect instead of following it @Asheesh7298 (#23405)
- [mesheryctl] Report a method-changing redirect instead of following it @Asheesh7298 (#23405)
github.com/meshery/meshery/releases/tag/v1.0.80mesheryctl refuses deletion of tokens used by contexts
Affectsmeshconfig setups with tokens referenced by contexts
When system token delete <name> is run for one of these tokens, the command lists the affected context names in sorted order and refuses deletion. Previously, it removed the token entry while leaving those contexts referring to a missing token; deleting an unused token continues to work as before.
Evidence“`DeleteTokenFromConfig` refuses to delete a token that a context uses and lists those contexts in sorted order: `token "prod" is still used by context(s) prod, staging; set another token on them first with ...`.” meshery/meshery/pull/23457 ↗ Show release-note lines
- [mesheryctl] Reject unknown tokens in token set and in-use tokens in token delete @Asheesh7298 (#23457)
github.com/meshery/meshery/releases/tag/v1.0.80Design export filenames now reflect export type
Affectssetups using mesheryctl design export, particularly oci or original exports(Inferred)
Previously, OCI exports had no extension, original Kubernetes-manifest and Docker Compose exports used .tar.gz despite containing YAML, and an unknown --type such as helm silently exported the current design as YAML. Now oci exports use .tar, original Helm-chart exports use .tar.gz, and other original exports use .yaml; current exports remain .yaml.
Evidence“The Helm and `current` filenames don't change.” meshery/meshery/pull/23447 ↗ Show release-note lines
- [mesheryctl] Name design export files by type and reject unknown --type @mayank609 (#23447)
- [mesheryctl] Name design export files by type and reject unknown --type @mayank609 (#23447)
github.com/meshery/meshery/releases/tag/v1.0.80Invalid --type values rejected by design export
Affectsmesheryctl design export(Inferred)
A mistyped value such as helm used to silently export the current design as YAML. The command now returns ErrInvalidArgument for unsupported values.
Evidence“`RunE` checks `--type` against `current`, `original`, `oci` before any network call and returns `ErrInvalidArgument` naming the valid values.” meshery/meshery/pull/23447 ↗ Show release-note lines
- [mesheryctl] Name design export files by type and reject unknown --type @mayank609 (#23447)
github.com/meshery/meshery/releases/tag/v1.0.80Consistent saved filenames for view --save
Affectsview --save for components, connections, environments, filters, models, relationships, or workspaces
Previously, saved filenames were passed through or only partly sanitized, inconsistently across resource types. Now spaces and filesystem-sensitive characters become underscores, leading and trailing whitespace is trimmed, and unusable names fall back to an available ID or, for several item types, unknown.
Evidence“When a name cannot produce a usable filename, the filename falls back to an item ID where available. For several item types, `unknown` is used if neither the name nor ID produces a usable filename.” meshery/meshery/pull/23436 ↗ Show release-note lines
- fix(mesheryctl): sanitize filesystem-unsafe characters in view --save filenames @ThakurUjjwal1706 (#23436)
github.com/meshery/meshery/releases/tag/v1.0.80Notification Center filters non-serializable UI payload values
AffectsNotification Center integrations using openNotificationCenter(Inferred)
Previously, the events slice stored the payload as received, including an icon component, which caused a Redux warning. Non-serializable fields such as Date, Map, Set, class instances, and circular objects are now dropped; the icon is stored by name and resolved during rendering.
Evidence“This screens the payload in openNotificationCenter before it reaches state. Only serializable values are kept, a Date, Map, Set, class instance or circular object gets dropped. The icon is stored as a name now, and the NotificationCenter resolves it to the component when rendering.” meshery/meshery/pull/23082 ↗ Show release-note lines
- [UI] Keep non-serializable values out of Notification Center state @krishbuilds01 (#23082)
github.com/meshery/meshery/releases/tag/v1.0.80Default-on pre-delete cleanup for Broker and MeshSync resources
AffectsMeshery Operator Helm chart installations with release-owned Broker or MeshSync custom resources
Previously, helm uninstall removed the operator and these resources in one pass, leaving them stuck Terminating on finalizers only the operator removed. The hook now deletes them while the operator is running, waits 90 seconds, then removes finalizers if needed; cleanup can be disabled with customResourceCleanup.enabled.
Evidence“**Symptom.** `helm uninstall` deletes the operator and the Broker/MeshSync resources in one pass. The resources then hang `Terminating` on `broker.meshery.io/finalizer` and `meshsync.meshery.io/finalizer`, which only the operator removes.” meshery/meshery/pull/23259 ↗ Show release-note lines
- [Helm] Give MeshSync read-only RBAC, expose Broker service values, clean up CRs on uninstall @yi-nuo426 (#23259)
github.com/meshery/meshery/releases/tag/v1.0.80Paginated GetID lookups find later design and filter matches
AffectsShort-prefix mesheryctl lookups against servers with more than 10,000 designs or filters
Matches beyond the first page could be missed, causing ValidId to treat an ambiguous prefix as unique and risk unintended deletion, or fail to resolve a unique prefix. GetID now collects IDs across pages, skips duplicates, and reads both totalCount and total_count; if it cannot confirm the full result within 50 pages, it returns an incomplete-lookup or page-limit error.
Evidence“When resolving short ID prefixes, `GetID` previously requested a single batch of `pagesize=10000` without inspecting total item counts. On servers with more than 10,000 designs or filters, matches past the first page were missed, causing `ValidId` to falsely conclude a prefix was unique (risking unintended deletions in `design delete`) or fail to resolve a unique prefix on subsequent pages.” meshery/meshery/pull/23206 ↗ Show release-note lines
- [mesheryctl] Paginate ID prefix lookup across multiple pages in GetID @bodapatisaikrishna (#23206)
- [mesheryctl] Paginate ID prefix lookup across multiple pages in GetID @bodapatisaikrishna (#23206)
github.com/meshery/meshery/releases/tag/v1.0.80Go Extensions field renamed to Account
AffectsGo code using the Extensions model field(Inferred)
The field was previously named Acccount and is now Account; its JSON tag remains json:"account,omitempty", preserving wire and API compatibility.
Evidence“The JSON struct tag remains `json:"account,omitempty"`, ensuring 100% wire and API backward-compatibility.” meshery/meshery/pull/23795 ↗ Show release-note lines
- [Server] Fix misspelled 'Acccount' field in Extensions model @Amansingh0807 (#23795)
github.com/meshery/meshery/releases/tag/v1.0.80Meshery provider validation follows the selected context
Affects--context targeting a context other than the saved current-context
Previously, a provider offered by the selected context could be rejected, while one offered only by the current context could be accepted and used to redeploy the selected context. An invalid context name now returns ErrSettingTemporaryContext before a request is made.
Evidence“`system provider switch --context X` redeploys `X`, but `validateProvider` asked the current context's Meshery server for its providers, because `GetProviderInfo` uses `mctlCfg.GetBaseMesheryURL()`, which follows `CurrentContext`. A provider `X` offers could be rejected, and one only the current context's server offers was accepted and then used to redeploy `X`.” meshery/meshery/pull/23786 ↗ Show release-note lines
- [mesheryctl] Validate the provider on the --context server in provider switch @Eternity0207 (#23786)
github.com/meshery/meshery/releases/tag/v1.0.80Filter cloning rejects empty names
Clone requests for an existing filter with an empty name receive a bad-request response.
Show release-note lines
- [Server] Return 404 for missing filters and validate path UUIDs in filter handlers @antcybersec (#23726)
github.com/meshery/meshery/releases/tag/v1.0.80Malformed workspace and environment path IDs now return HTTP 400
Affectsworkspace and environment routes that take path IDs
Previously, malformed IDs reached the Local provider, which returned HTTP 502 on 18 routes and HTTP 404 on three, where the ID was converted to the nil UUID. Now all 21 routes return HTTP 400 with models.ErrInvalidUUID before calling the provider; well-formed IDs that do not exist are unaffected.
Evidence“A malformed ID in the path of a workspace or environment route used to reach the provider. With the Local provider that came back as `502 Bad Gateway` on 18 routes and as `404` on 3, where the ID was quietly turned into the nil UUID. All 21 routes now answer `400` with the existing `models.ErrInvalidUUID` (`meshery-server-1432`) before the provider is called.” meshery/meshery/pull/23637 ↗ Show release-note lines
- [Server] Return 400 for a malformed ID on workspace and environment routes @himanishpuri (#23637)
github.com/meshery/meshery/releases/tag/v1.0.80Schedule handlers reject empty inputs
Affectsthe schedule handler endpoints
Calls to DeleteScheduleHandler or GetScheduleHandler with an empty scheduleID now receive HTTP 400 before the provider is queried. A nil or empty decoded body sent to SaveScheduleHandler also receives HTTP 400 before the provider operation proceeds.
Evidence“Added validation in `DeleteScheduleHandler` and `GetScheduleHandler` to ensure `scheduleID` is not empty before querying the provider, returning `http.StatusBadRequest` (400) if empty.” meshery/meshery/pull/23540 ↗ Show release-note lines
- [Server] Guard nil provider and validate schedule ID across schedule handlers @piyxsh31 (#23540)
github.com/meshery/meshery/releases/tag/v1.0.80Preference persister errors now use MeshKit constructors
Affectssetups using the preference persister(Inferred)
Read, save, and create failures are returned using ErrDBRead, ErrDBPut, and ErrDBCreate, respectively.
Evidence“Preference read, save, and delete operations now return more specific errors when they fail.” meshery/meshery/pull/23536 ↗ Show release-note lines
- [Server] Guard nil database handler, validate userID, and check rows affected in preference persister @piyxsh31 (#23536)
github.com/meshery/meshery/releases/tag/v1.0.80Configuration file close errors are now reported
Affectsmesheryctl configuration-file creation or backup
Previously, close errors in these paths were ignored. Now, CreateConfigFile returns a close error, while the backup path passes it to Log.Fatal.
Show release-note lines
- [mesheryctl] Fix HTTP response body and file descriptor leaks in utils @muskan-creates352 (#22645)
github.com/meshery/meshery/releases/tag/v1.0.80Adapter deploy and validate waiters now handle response events directly
Affectsadapter deploy or validate flows that wait for response events(Inferred)
If a waiter timed out before its event-reading goroutine finished, that goroutine could remain blocked trying to send its result. The wait loop now returns on matching success or error events and stops its timer on return.
Show release-note lines
- fix: restrict Windows token file permissions @0xmaster7 (#23380)
- fix: restrict Windows token file permissions @0xmaster7 (#23380)
github.com/meshery/meshery/releases/tag/v1.0.80mesheryctl filter delete now requires exactly one argument
Affectsthe mesheryctl filter delete command
Previously, zero arguments could reach the handler, and multiple arguments were not rejected by argument validation. Now, either count produces a validation error before the handler runs.
Evidence“This PR enforces exact argument validation (`cobra.ExactArgs(1)`) on `mesheryctl filter delete`, rejecting invocations with zero arguments or multiple arguments before executing the command handler.” meshery/meshery/pull/23519 ↗ Show release-note lines
- [mesheryctl] Enforce exact argument validation in filter delete @AdityaChaudhary5412 (#23519)
github.com/meshery/meshery/releases/tag/v1.0.80mesheryctl rejects context names containing .
Affectsmesheryctl contexts whose names contain .(Inferred)
Previously, a dotted context could be created even though Viper could not read it back. The failed addition now leaves the existing configuration unchanged.
Evidence“Adding a context name that contains a period now returns an error and leaves the existing configuration unchanged.” meshery/meshery/pull/23441 ↗ Show release-note lines
- [mesheryctl] Reject dotted context names @0xmaster7 (#23441)
github.com/meshery/meshery/releases/tag/v1.0.80