RATATOSK
← All releases

Mesheryv1.0.27

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

Get Meshery alerts

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

Breaking changes2

mesheryctl fallback uses the canonical provider URL set

Affectsmesheryctl 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"” meshery/meshery/pull/19621 ↗
Show release-note lines
- Single-source the remote-provider list across install artifacts @hortison (#19621)
github.com/meshery/meshery/releases/tag/v1.0.27

Standardized mesheryctl performance-profile save errors

Affectsperformance-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.” meshery/meshery/pull/19571 ↗
Show release-note lines
- fix: improve error handling for performance profile server failures @Omkar-Ugal (#19571)
github.com/meshery/meshery/releases/tag/v1.0.27

Important fixes1

  • Generated install artifacts use install/providers.env as their canonical provider source
    Affectsinstallations 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)
    github.com/meshery/meshery/releases/tag/v1.0.27

Enhancements1

Dependency updates3

    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 changes12

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