# Meshery v1.0.27

2026-05-22 · [Original release notes](https://github.com/meshery/meshery/releases/tag/v1.0.27) · [Full summary](https://ratatosk.io/en/releases/meshery/v1.0.27)

Breaking changes 2 · Important fixes 1 · Enhancements 1 · Dependency updates 3 · Other changes 12

## Breaking changes (2)

### `mesheryctl` fallback uses the canonical provider URL set

- Affects: `mesheryctl` installations using the compiled-in fallback

When the install docker-compose file cannot be downloaded, the fallback previously included `https://meshery.digitalocean.com` and `https://idp.cleverluck.com`; it now uses `https://cloud.meshery.io,https://perf.smp-spec.io,https://cloud.layer5.io,https://meshery.tcs-labs.in`.

Evidence: “const DefaultProviderBaseURLs = "https://cloud.meshery.io,https://perf.smp-spec.io,https://cloud.layer5.io,https://meshery.tcs-labs.in"” https://github.com/meshery/meshery/pull/19621

> - Single-source the remote-provider list across install artifacts @hortison (#19621)

### Standardized `mesheryctl` performance-profile save errors

- Affects: performance-profile saves through `mesheryctl` (Inferred)

Previously, a server 500 while saving a performance profile displayed the raw JSON error response. Now the error includes “Server error while saving performance profile,” the underlying error, and provider-connectivity troubleshooting text.

Evidence: “Previously, when the server returned a 500 error while saving a performance profile, the raw JSON error response from the server was displayed directly to the user, making it difficult to understand what went wrong.” https://github.com/meshery/meshery/pull/19571

> - fix: improve error handling for performance profile server failures @Omkar-Ugal (#19571)

## Important fixes (1)

### Generated install artifacts use `install/providers.env` as their canonical provider source

- Affects: installations using the updated static artifacts, including Docker Compose and the standard-install profile

When provider URLs drift between hand-maintained artifacts, the production playground could serve a stale `PROVIDER_BASE_URLS` value as active configuration without an accompanying error. The generated Docker Compose artifact now sets it to `https://cloud.meshery.io,https://perf.smp-spec.io,https://cloud.layer5.io,https://meshery.tcs-labs.in`, and `make check-install` checks committed artifacts against `install/providers.env`.

> - Single-source the remote-provider list across install artifacts @hortison (#19621)
> - Single-source the remote-provider list across install artifacts @hortison (#19621)
> - Single-source the remote-provider list across install artifacts @hortison (#19621)
> - Single-source the remote-provider list across install artifacts @hortison (#19621)

## Enhancements (1)

- Docker Desktop extension now includes the full provider set

## Dependency updates (3)

3 more, none mentioning security

- `- [Chore]: Bump meshery/schemas to v1.2.23 @l5io (#19623)`
- `- Bump github.com/containerd/containerd from 1.7.30 to 1.7.32 @[dependabot[bot]](https://github.com/apps/dependabot) (#19593)`
- `- Bump github.com/containerd/containerd/v2 from 2.2.0 to 2.2.4 @[dependabot[bot]](https://github.com/apps/dependabot) (#19594)`

## Other changes (12)

- Faster match-label and binding relationship identification
- System endpoints now use generated `meshery/schemas` types
- `GetConnections` batches environment loading
- Example raw GitHub URL removed from `ParseURLGithub` comment
- UI page shell consolidated and browser-tab titles standardized
- Bash installation documentation headings render correctly
- Maanvi Chetwani’s introduction added to meeting documentation
- Ayush Hardeniya's introduction added to the week-of-05-21-2026 meeting documentation
- Akshit Tomar’s introduction added to the week-of-05-21-2026 meeting documentation
- Akash Sah’s introduction added to the May 21, 2026 meeting documentation
- Riteshbabu Allam’s introduction added to the May 21, 2026 meeting documentation
- Yash Mahakal’s introduction added to week-of-05-21-2026 meeting documentation

---

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