RATATOSK
← All releases

Mesheryv1.0.50

Security 1Breaking changes 1Important fixes 5Enhancements 77Dependency updates 3Other changes 32

Get Meshery alerts

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

Security1

ws remote memory-exhaustion crash fixed

AffectsMeshery Docker extension UI dependencies in /install/docker-extension/ui

A peer could send many tiny fragments and data chunks with modest network traffic, causing a ws server or client to crash from OOM. The UI lockfile now uses ws 8.21.0 and 7.5.11; the 8.21.0 fix prevents this described crash.

Show release-note lines
- Bump ws in /install/docker-extension/ui @[dependabot[bot]](https://github.com/apps/dependabot) (#20110)
github.com/meshery/meshery/releases/tag/v1.0.50

Breaking changes1

AWS API Gateway v2 hierarchical relationships refactored

AffectsAWS API Gateway v2 Route/API and Stage/API hierarchical relationships(Inferred)

The relationships used the prior schema and had mutatorRef logic that needed correction; the route relationship targeted the AWS logical name instead of the Kubernetes object name. They now use the v1alpha3 schema with corrected mutatorRef logic, and the route relationship targets the Kubernetes object name.

Evidence“- Updated `hierarchical-inventory-route-api` to use `v1alpha3` schema and correct `mutatorRef` logic (targeting K8s object name instead of AWS logical name).” meshery/meshery/pull/17631 ↗
Show release-note lines
- [Models] Implemented AWS APIGatewayV2 Bindings & Refactored Hierarchical Relationships to v1alpha3 schema @AhmedAzzam-Web (#17631)
github.com/meshery/meshery/releases/tag/v1.0.50

Important fixes5

  • Azure Container Service relationship model names corrected
    Affectssetups using the azure-container-service model and its existing relationships

    Selectors in eight existing relationship files used the misspelled azure-conatiner-service model name, leaving incorrect model-name references. The files now refer to azure-container-service.

    - feat(meshmodel): fix typo and add ManagedClustersAgentPool relationship for azure-container-service @adityaupasani2 (#17760)
    github.com/meshery/meshery/releases/tag/v1.0.50
  • AWS networking relationships added to aws-ec2-controller/v1.9.2
    AffectsAWS models using aws-ec2-controller/v1.9.2

    When modeling AWS routing and egress, RouteTable → Subnet existed, but route targets and the listed NAT Gateway, instance, and VPC endpoint relationships were missing. The model now includes ten relationships: RouteTable to InternetGateway, NATGateway, VPCPeeringConnection, TransitGateway, and VPCEndpoint; NATGateway to Subnet and ElasticIPAddress; Instance to Subnet; and VPCEndpoint to Subnet and SecurityGroup.

    - [Models] Add AWS routing and NAT Gateway relationships for aws-ec2-controller @akshayghalme (#19087)
    github.com/meshery/meshery/releases/tag/v1.0.50
  • Exoscale icons now include their brand background
    AffectsKanvas/shapes using crossplane-provider-exoscale model versions v1.0.0 and v1.0.1

    When svgComplete was empty in meshmodel metadata, Kanvas/shapes showed only a white glyph without the Exoscale brand background. The metadata now provides the full red-circle-and-white-logo icon.

    - fix(meshmodel): populate svgComplete for Exoscale icons @ShubhamSoni09 (#19939)
    github.com/meshery/meshery/releases/tag/v1.0.50
  • mesheryctl minimum() tie handling fixed
    Affectsmesheryctl code paths that use minimum() and encounter tied minimum arguments(Inferred)

    When two arguments tied for the minimum, such as a == b < c, minimum() returned the largest argument instead.

    - [mesheryctl] Fix minimum() returning max on argument ties @Priyanshu6968 (#20285)
    github.com/meshery/meshery/releases/tag/v1.0.50
  • Add Cluster upload handling for errored contexts fixed
    Affectskubeconfig uploads through Add Cluster

    When an uploaded kubeconfig contained an unreachable or unsavable context, the UI read the wrong response buckets and tried to access a missing error field, then displayed a post-upload crash as an upload failure even though the upload succeeded. It now handles those contexts and builds notifications from the context name and server.

    - [UI] Fix Add Cluster crash on kubeconfig upload with errored contexts @marblom007 (#20317)
    github.com/meshery/meshery/releases/tag/v1.0.50

Enhancements77

Dependency updates3

    3 more, none mentioning security
    • - Bump launch-editor from 2.12.0 to 2.14.1 in /install/docker-extension/ui @[dependabot[bot]](https://github.com/apps/dependabot) (#20104)
    • - Bump tmp from 0.2.6 to 0.2.7 in /ui @[dependabot[bot]](https://github.com/apps/dependabot) (#20080)
    • - Rewire model data references to repo-root models/ and bump meshkit v1.0.19 @miacycle (#20312)
    Other changes32

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