Breaking changes28
DeleteMeshSyncResource success body and failure response changed
Affectsclients calling the DeleteMeshSyncResource endpoint
Previously, successful deletions returned an empty HTTP 200 response, while failed deletions also returned HTTP 200 and appeared only in server logs. Successful deletions now include {"deleted": true}; failed deletions return HTTP 500 with an error message.
Evidence“- On delete failure: - logs the delete error - returns `500 Internal Server Error` with error message in response body - On delete success: - returns `200 OK` - returns JSON response: `{"deleted": true}`” meshery/meshery/pull/18193 ↗ Show release-note lines
- [Server] Fix DeleteMeshSyncResource HTTP response handling @Manishnemade12 (#18193)
github.com/meshery/meshery/releases/tag/v1.0.1Request retries now check body replayability
Affectsrequests with bodies made through RemoteProvider.DoRequest(Inferred)
After a successful token refresh, replayable bodies are resent; requests with non-replayable bodies return an error instead of being retried.
Evidence“default: + return nil, fmt.Errorf("request body is not replayable")” meshery/meshery/pull/18162 ↗ Show release-note lines
RemoteProvider token refresh validation and trimming
Affectssetups using RemoteProvider token refresh(Inferred)
Refresh responses other than HTTP 200 OK or with an empty token now return errors, and whitespace around cached and returned tokens is trimmed.
Evidence“if r.StatusCode != http.StatusOK { + body, readErr := io.ReadAll(r.Body) + if readErr != nil { + return "", fmt.Errorf("failed to refresh token. status code %d", r.StatusCode) + } + return "", fmt.Errorf("failed to refresh token. status code %d: %s", r.StatusCode, strings.TrimSpace(string(body)))” meshery/meshery/pull/18162 ↗ Show release-note lines
Dashboard-opening errors no longer fail mesheryctl system start
Affectssetups using mesheryctl system start
Previously, if opening the dashboard failed, mesheryctl system start returned that error; it now logs a warning and returns nil. With skipBrowserFlag set, it skips the dashboard command and returns successfully.
Evidence“- return dashboardCmd.RunE(nil, nil) + if skipBrowserFlag { + utils.Log.Info("Meshery deployed. Use `mesheryctl system dashboard` to access the UI.") + return nil + } + if err := dashboardCmd.RunE(nil, nil); err != nil { + utils.Log.Warnf("Meshery deployed successfully, but could not open dashboard: %v\nRun `mesheryctl system dashboard` to access the UI.", err) + } + return nil” meshery/meshery/pull/18477 ↗ Show release-note lines
- fix: mesheryctl e2e system start @lekaf974 (#18477)
github.com/meshery/meshery/releases/tag/v1.0.1Configuration-loading errors returned by mesheryctl system reset
Affectsthe mesheryctl system reset command(Inferred)
When Meshery configuration loading failed, the command logged the error but returned success; it now returns the error to its caller. Extra arguments now produce utils.ErrInvalidArgument, and reset logging uses utils.Log instead of logrus.
Show release-note lines
- fix: system reset uses meshkit error properly, remove logrus @Omkar-Ugal (#18358)
github.com/meshery/meshery/releases/tag/v1.0.1Updated mesheryctl login validation and stopped-server status handling
Affectsmesheryctl system login calls with --provider, and use of mesheryctl system status
Previously, arbitrary supplied provider values were not rejected by the validator; invalid non-empty values are now rejected, and errors in the changed login paths are returned to the command rather than only logged. When Meshery is not running, system status prints the context, platform, and status message but returns success instead of an error.
Show release-note lines
- refactor(mesheryctl): enhance login command UX and error handling, update error codes + fix bug in system status @lekaf974 (#18345)
github.com/meshery/meshery/releases/tag/v1.0.1Strict flag validation and returned errors in mesheryctl system status
Affectsthe mesheryctl system status command
Previously, invalid --verbose/-v values were accepted silently, and failures in health-check, configuration/context, or server-status paths were logged while the command returned nil. These cases now reject invalid flag values or return command errors.
Evidence“Error: invalid argument "invalid" for "-v, --verbose" flag: strconv.ParseBool: parsing "invalid": invalid syntax” meshery/meshery/pull/18255 ↗ Show release-note lines
- fix: system status uses meshkit error properly, remove logrus, add fl… @Omkar-Ugal (#18255)
github.com/meshery/meshery/releases/tag/v1.0.1System context and system-check errors now reach the CLI
Affectsthe mesheryctl system context command and associated system-check paths
Configuration unmarshalling, current-context retrieval, or health-check errors were logged and returned as success, producing an incorrect CLI success exit code. These failures now reach the CLI caller, so the command reports failure.
Evidence“- Prevented silent failures and incorrect CLI success exit codes” meshery/meshery/pull/18154 ↗ Show release-note lines
- fix(mesheryctl): return proper error in system context command @Omkar-Ugal (#18154)
github.com/meshery/meshery/releases/tag/v1.0.1Stable context ordering in Meshery CLI --all commands
Affectsthe mesheryctl system channel view --all and mesheryctl system provider view --all commands
Previously, the channel command's output order varied because it iterated contexts from a Go map.
Evidence“`mesheryctl system channel view --all` was producing nondeterministic output because it iterated contexts from a Go map directly.” meshery/meshery/pull/18140 ↗ Show release-note lines
- Stabilize mesheryctl system view output across reused Cobra command state @[copilot-swe-agent[bot]](https://github.com/apps/copilot-swe-agent) (#18140)
github.com/meshery/meshery/releases/tag/v1.0.1Full design IDs shown by default in mesheryctl design list
Affectsnon-verbose mesheryctl design list output(Inferred)
Previously, non-verbose listings truncated design IDs; full IDs appeared only with --verbose.
Show release-note lines
- [mesheryctl] Show full design IDs in design list by default @PragalvaXFREZ (#17971)
github.com/meshery/meshery/releases/tag/v1.0.1Set-context API error reporting in mesheryctl
Affectsuse of mesheryctl system config or mesheryctl connection create
Previously, these commands could appear to succeed when the set-context API returned a 4xx or 5xx response. They now return an error with the status code and response body for non-2xx responses; the raw response body remains in debug logs.
Evidence“If the API responds with a non-2xx status code, the command now returns an error that includes the status code and response body.” meshery/meshery/pull/17912 ↗ Show release-note lines
- [mesheryctl] Use MakeRequest for set‑context API calls @dipanshurdev (#17912)
github.com/meshery/meshery/releases/tag/v1.0.1Shared flag validation added to mesheryctl model commands
Affectsthe affected mesheryctl model commands, especially those with path-valued flags(Inferred)
Path-valued flags are checked before affected commands run. mesheryctl model delete now produces no output and no error for a nonexistent model, instead of returning an error.
Show release-note lines
- refactor(mesheryctl): model commands flags validation @lekaf974 (#17737)
- refactor(mesheryctl): model commands flags validation @lekaf974 (#17737)
- refactor(mesheryctl): model commands flags validation @lekaf974 (#17737)
github.com/meshery/meshery/releases/tag/v1.0.1Metrics publishing leak fixed and field spelling corrected
AffectsMeshery server deployments publishing metrics through DefaultLocalProvider or RemoteProvider
When PublishMetrics() received http.StatusOK, it returned without closing the response body, leaking HTTP connections and file descriptors over time; it now closes the body on that path. The YAML output key changes from servermatrics to servermetrics.
Evidence“The `defer resp.Body.Close()` was placed **after** an early `return nil` on `http.StatusOK`, meaning the response body was never closed on the success path. Over time, this leaks HTTP connections and file descriptors.” meshery/meshery/pull/17716 ↗ Show release-note lines
- Fix HTTP response body leak in PublishMetrics and correct typos @Ironankit525 (#17716)
- Fix HTTP response body leak in PublishMetrics and correct typos @Ironankit525 (#17716)
github.com/meshery/meshery/releases/tag/v1.0.1Environment and workspace handlers now read orgId
Affectsorganization IDs supplied through environment or workspace handler query parameters(Inferred)
Before this change, frontend requests using orgId supplied an empty organization ID, causing provider calls to fail with 404.
Evidence“The frontend (@meshery/schemas) sends `orgId` (camelCase) but the Go handlers were reading `orgID` (capital ID). Since Go's url.Values.Get() is case-sensitive, the org ID was always empty, causing provider calls to fail with a 404.” meshery/meshery/pull/18513 ↗ Show release-note lines
- Fix orgId query parameter case mismatch in environment and workspace … @fitzergerald (#18513)
github.com/meshery/meshery/releases/tag/v1.0.1SessionInjectorMiddleware preserves sessions during remote-provider outages with HTTP 503
Affectssessions using a remote provider
Action requiredNo companion Meshery Cloud change is required first; the companion PR can be deployed independently.
When a remote provider such as Cloud was temporarily unreachable, the middleware logged users out and redirected them to login, causing a redirect loop while the outage continued.
Evidence“- **Distinguish transient errors from auth failures**: `SessionInjectorMiddleware` no longer destroys user sessions when Cloud is temporarily unreachable — returns 503 instead of logging out + redirecting (which looped when Cloud stayed down).” meshery/meshery/pull/18434 ↗ Show release-note lines
- fix: resolve auth redirect loops between Meshery Server and Cloud @leecalcote (#18434)
github.com/meshery/meshery/releases/tag/v1.0.1Empty organization IDs rejected by GetWorkspaceByIdHandler
Affectsintegrations calling GetWorkspaceByIdHandler(Inferred)
When the organization ID query value was empty, the handler previously passed it to GetWorkspaceByID without checking. It now returns HTTP 400 with a workspace-input error instead.
Show release-note lines
- fix(server): enforce missing OrgID handling in GetWorkspaceByIdHandler @lekaf974 (#18141)
github.com/meshery/meshery/releases/tag/v1.0.1mesheryctl filter view rejects extra positional arguments
Affectsthe mesheryctl filter view command
The command previously silently accepted multiple positional arguments; it now returns an at-most-one-argument error. The --all conflict and missing name/ID checks also run earlier, in PreRunE.
Evidence“# Properly rejected mesheryctl filter view arg1 arg2 Error: accepts at most 1 arg(s), received 2” meshery/meshery/pull/18362 ↗ Show release-note lines
- [mesheryctl] Replace cobra.ArbitraryArgs with proper argument validat… @Manishnemade12 (#18362)
github.com/meshery/meshery/releases/tag/v1.0.1mesheryctl system logout now returns errors
Affectsuse of mesheryctl system logout
Previously, failures to load Mesheryctl configuration, get the current context’s token, or write the token file were logged but returned as nil. These failures now return errors to the caller; a token-file write failure returns ErrLogout (mesheryctl-1229).
Evidence“- utils.Log.Error(ErrGetCurrentContext(errors.Wrap(err, "failed to find token path for the current context"))) - return nil + return ErrGetCurrentContext(err)” meshery/meshery/pull/18327 ↗ Show release-note lines
- fix: system logout uses meshkit error properly, remove logrus @Omkar-Ugal (#18327)
github.com/meshery/meshery/releases/tag/v1.0.1Dashboard command now validates flags and returns errors
Affectsthe mesheryctl system dashboard command
Previously, invalid flag values were not checked, and configuration/context lookup or port-forward initialization errors could be logged while the command returned success. The validator now rejects invalid values, and affected errors are returned instead of being treated as successful completion.
Show release-note lines
- refactor(mesheryctl): update dashboard command flags and improve error handling @lekaf974 (#18341)
github.com/meshery/meshery/releases/tag/v1.0.1Structured errors from mesheryctl system delete
Affectsmesheryctl system delete on Docker or unsupported platforms
Previously, Docker Compose client-creation or container-removal failures and unsupported platforms returned generic system errors. These failures now return corresponding Meshery/meshkit errors, including Docker Compose error codes, changing the errors received by automation.
Show release-note lines
- refactor(mesheryctl): update system delete removing logrus reference and return proper meshkit error @lekaf974 (#18342)
github.com/meshery/meshery/releases/tag/v1.0.1mesheryctl system logs validates --follow and returns errors
Affectsuse of mesheryctl system logs
Previously, invalid --follow values were silently accepted, while failures could be logged and the command could still return nil. Health-check, config/context, and server-not-running failures now return command errors.
Evidence“Error: invalid argument "invalid" for "-f, --follow" flag: strconv.ParseBool: parsing "invalid": invalid syntax” meshery/meshery/pull/18227 ↗ Show release-note lines
- fix: system logs uses meshkit error properly, remove logrus, add flag… @Omkar-Ugal (#18227)
github.com/meshery/meshery/releases/tag/v1.0.1Context subcommands now validate flags and return structured errors
Affectsmesheryctl system context create, delete, and view commands
Previously, these commands had no added pre-run flag validation, and some configuration read/write, duplicate-context, prompt, and argument errors lacked structured handling. Those failure paths now return errors instead of following the less specifically handled paths.
Show release-note lines
- refactor(mesheryctl): update system context subcommands to use proper error handling and flags validator @lekaf974 (#18244)
github.com/meshery/meshery/releases/tag/v1.0.1Missing-connection deletion returns HTTP 404; mesheryctl succeeds
Affectsconnection deletion
When a deletion targets an ID that does not exist, the server previously returned an internal-server error and the CLI returned a connection-not-found error. Now the CLI logs “No connection with ID "…" found” as a warning.
Show release-note lines
- fix: update connection deletion logic and error handling on server and cli @lekaf974 (#17910)
github.com/meshery/meshery/releases/tag/v1.0.1Channel command failures now return errors
Affectsmesheryctl system channel commands, including view, set, and switch
When getting the current context fails or its content is unavailable, the commands previously logged the error and returned nil; they now return the error. set and switch return an invalid-argument error when the number of release-channel arguments is not exactly one.
Show release-note lines
- refactor(mesheryctl): update system channel to use meshkit and return errors properly and update description @lekaf974 (#18122)
- refactor(mesheryctl): update system channel to use meshkit and return errors properly and update description @lekaf974 (#18122)
github.com/meshery/meshery/releases/tag/v1.0.1Performance API metric names corrected
Affectsserver metric publishing messages and code using PerformanceResult(Inferred)
The comment and error message previously used asyncronously and Matrics/ServerMatrics; they now use asynchronously and Metrics. The Go field is now ServerMetrics, while its JSON field remains server_metrics.
Evidence“- `asyncronously` -> `asynchronously` in comments - - `Matrics` -> `Metrics` in error message - - `ServerMatrics` -> `ServerMetrics` struct field name (JSON tag unchanged, non-breaking)” meshery/meshery/pull/17716 ↗ Show release-note lines
- Fix HTTP response body leak in PublishMetrics and correct typos @Ironankit525 (#17716)
github.com/meshery/meshery/releases/tag/v1.0.1Workspace commands moved to mesheryctl workspace
Affectsthe mesheryctl workspace commands(Inferred)
Workspace commands were previously under mesheryctl exp workspace; their workspace operations are unchanged.
Show release-note lines
- [mesheryctl] graduate workspace command from experimental @PragalvaXFREZ (#18125)
github.com/meshery/meshery/releases/tag/v1.0.1Workspace-list page-size flag renamed to --pagesize
Affectsworkspace-list command invocations using --page-size(Inferred)
When explicitly set, the value is sent as the pagesize query parameter. The default remains 10 and the maximum remains 100.
Show release-note lines
- [mesheryctl] graduate workspace command from experimental @PragalvaXFREZ (#18125)
- [mesheryctl] graduate workspace command from experimental @PragalvaXFREZ (#18125)
github.com/meshery/meshery/releases/tag/v1.0.1Docker image catalog data now uses a new source and path
AffectsMeshery Docker image deployments and integrations reading its catalog files(Inferred)
Previously, the image copied catalog data from docs-new/data/catalog to /app/docs/catalog/. It now copies data from docs/data/catalog to /app/docs/data/catalog/.
Evidence“COPY ./docs/data/catalog /app/docs/data/catalog/” meshery/meshery/pull/17991 ↗ Show release-note lines