RATATOSK
← All releases

Mesheryv1.0.25

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

Get Meshery alerts

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

Breaking changes2

Empty REMOTE_PROVIDER installation default

Affectsinstallations using the default REMOTE_PROVIDER in install/Makefile.core.mk

Previously, the install Makefile defaulted REMOTE_PROVIDER to Layer5. With the new empty default, first use shows provider choices instead of enforcing one; setting REMOTE_PROVIDER to a provider name can still enforce one through PROVIDER.

Show release-note lines
- Refactor providers: rename Local provider (was "None") and remote providers @hortison (#19574)
github.com/meshery/meshery/releases/tag/v1.0.25

Built-in Local provider renamed from None

AffectsMeshery installations or mesheryctl configurations using the built-in Local provider
Removed ina future Meshery release

Existing None values in cookies, headers, query parameters, environment variables, and config files still resolve as Local; mesheryctl also rewrites legacy values to Local in memory. Using None logs a deprecation warning once per server process.

Evidence“+ h.log.Warnf("DEPRECATION: the local provider name %q is the legacy alias for %q and will be removed in a future Meshery release. Update meshery-provider cookies, the PROVIDER environment variable, and ~/.meshery/config.yaml to use %q. This warning is logged once per server process.", models.LocalProviderLegacyAlias, models.LocalProviderName, models.LocalProviderName)” meshery/meshery/pull/19574 ↗
Show release-note lines
- Refactor providers: rename Local provider (was "None") and remote providers @hortison (#19574)
- Refactor providers: rename Local provider (was "None") and remote providers @hortison (#19574)
- Refactor providers: rename Local provider (was "None") and remote providers @hortison (#19574)
- Refactor providers: rename Local provider (was "None") and remote providers @hortison (#19574)
github.com/meshery/meshery/releases/tag/v1.0.25

Important fixes1

  • Deterministic Go relationship evaluation
    AffectsMeshery Server's Go relationship evaluation engine

    For the same input design, it could produce different relationship IDs or select different matchlabel groups across runs.

    - [Server] Fix non-determinism in relationship eval engine @guan404ming (#19127)
    github.com/meshery/meshery/releases/tag/v1.0.25

Enhancements3

Dependency updates1

    1 more, none mentioning security
    • - [Chore]: Bump meshery/schemas to v1.2.22 @l5io (#19551)
    Other changes13

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