What meshery/meshery shipped
Written by FoxPlug from the repository's own releases; not affiliated with Meshery. Paste your own repository in the box below and FoxPlug writes the same weekly update for your product. This page is an automatic summary of the releases, pull requests and commits in github.com/meshery/meshery; Meshery did not write it and does not use or endorse FoxPlug. Every line links to the change it describes.
Get a weekly update like this for your product, free
Week of November 2, 2026
What shipped
- Model export now rejects version fields that contain path traversal, writing files only inside the export directory. Pull request #23031
- Workspace environment, view and team assignments no longer leave mappings behind after removal, and repeated assignments are deduplicated. Pull request #23043
- Mesheryctl system token view no longer blocks on an empty prompt and honors the --yes flag. Pull request #23036
- Mesheryctl design delete -f now sends the deploy payload the server expects instead of the raw design content. Pull request #23021
- MeshSync resource filters now require every requested label to match and no longer return or count a resource once per label. Pull request #23041
- The Designs publish form now reports an error when the schema fails to load instead of only logging to the console. Pull request #22990
- Deleting a performance profile now shows an error when the delete fails. Pull request #22986
- Mesheryctl system logs on Docker now exits unless -f is passed. Pull request #22979
- Updating a connection with an unknown ID now returns 404 instead of creating a connection. Pull request #23004
- Updating a connection on the Local provider now preserves its
created_atand owner. Pull request #23027
Why it matters
This week's changes close several data integrity gaps: model export no longer writes outside its directory via a crafted version, workspace mappings no longer duplicate or survive removal, and connections keep their creation time and owner when edited. They also remove silent failures across the CLI and UI, so a hung prompt, a dropped deploy payload, a failed profile delete or an unloaded schema now surfaces instead of passing quietly.
Changelog entry
- Reject path traversal in model version fields during export. Pull request #23031
- Stop repeated workspace assignments from surviving removal. Pull request #23043
- Deduplicate workspace environment, view and team mappings. Pull request #23034
- Prevent mesheryctl system token view from hanging on an empty prompt and respect --yes. Pull request #23036
- Send the deploy payload from mesheryctl design delete -f. Pull request #23021
- Respect --follow for mesheryctl system logs on Docker. Pull request #22979
- Require every label to match in MeshSync resource filters. Pull request #23041
- Notify when the Designs publish schema fails to load. Pull request #22990
- Show an error when deleting a performance profile fails. Pull request #22986
- Return 404 instead of creating a connection for an unknown ID. Pull request #23004
- Keep a connection's
created_atand owner when updating it. Pull request #23027 - Keep a performance profile's
created_atwhen editing it. Pull request #23002
This week: model export rejects path traversal in version fields, workspace mappings stop duplicating, and connections keep created_at and owner. mesheryctl token view no longer hangs and system logs exits unless -f is passed.
Changes this week cover correctness in several places. Model export now rejects version fields that contain path traversal, so exported files stay in the export directory. Workspace environment, view and team assignments are deduplicated and no longer leave mappings behind after removal. Connections keep their created_at and owner when updated, and an unknown connection ID returns 404 instead of creating a record. Performance profiles keep their created_at when edited. In mesheryctl, token view no longer blocks on an empty prompt, design delete -f sends the deploy payload the server expects, and system logs on Docker exits unless -f is passed. In the UI, publish schema load failures, failed profile deletes and failed SMP mesh list loads now show an error.
Week of October 26, 2026
What shipped
- Upgraded Next.js from 16.4.0 to 16.4.3 and applied dependency security fixes for two published advisories. Pull request #22550
- Closed the HTTP response body leak in the mesheryctl system dashboard keepConnectionAlive loop and removed conflicting debug logging. Pull request #22627
- Closed response bodies inside each loop iteration of the mesheryctl system check adapter health check to stop socket descriptor leaks. Pull request #22583
- Managed the Blob object URL lifecycle in the Notification Center DataToFileLink so URLs are no longer created inline during render. Pull request #22570
- Fixed adapter selection in MesheryPlayComponent by replacing an invalid array size check with a find and presence check. Pull request #22349
- Fixed the inverted schema dropdown condition and HTML nesting in the shared LegacyRJSFModal so the version switcher renders. Pull request #22350
- Fixed the double-wrapped error from mesheryctl model export flag validation and added tests. Pull request #19866
- Corrected 23 broken in-page anchor links across 20 documentation files. Pull request #22441
- Updated the Helm Snapshot docs with the renamed helm-kanvas-snapshot plugin and a working install URL. Pull request #22574
- Re-enabled the commented-out mesheryctl environment list unit tests and corrected the mock query URL. Pull request #22589
Why it matters
This week's changes mostly remove small but persistent sources of friction: leaked HTTP response bodies and Blob URLs, an adapter picker that could not switch, a schema dropdown that stayed hidden, and doubled CLI error text. The Next.js upgrade addresses two published security advisories, and documentation fixes repair broken anchors and an install command that returned a 404.
Changelog entry
- Upgrade Next.js to 16.4.3 to address security advisories and apply dependency fixes. Pull request #22550
- Close response bodies in the mesheryctl system dashboard keepConnectionAlive loop. Pull request #22627
- Close response bodies per iteration in mesheryctl system check adapter health checks. Pull request #22583
- Manage Blob URL lifecycle in the Notification Center DataToFileLink. Pull request #22570
- Fix adapter selection in MesheryPlayComponent and remove variable shadowing. Pull request #22349
- Fix schema dropdown rendering condition and HTML nesting in LegacyRJSFModal. Pull request #22350
- Fix double-wrapped export flag validation error in mesheryctl model and add tests. Pull request #19866
- Fix 23 broken in-page anchor links across the docs. Pull request #22441
- Update Helm Snapshot install URL and plugin usage for helm-kanvas-snapshot. Pull request #22574
- Re-enable environment list unit tests and fix the mock query URL in mesheryctl. Pull request #22589
- Include the declared namespace in Forbidden messages from the default fallback dry-run. Pull request #22661
- Replace a fixed wait in the user preference e2e spec with a web-first assertion. Pull request #22619
This week in Meshery: Next.js upgraded for two security advisories, mesheryctl dashboard and system check response body leaks fixed, adapter selection and schema dropdown repaired in the UI, broken docs anchors corrected, and 23 doc links fixed.
This week's Meshery changes focus on reliability and docs. Next.js was upgraded from 16.4.0 to 16.4.3 to address two published security advisories. In mesheryctl, HTTP response body leaks were closed in the system dashboard keep-connection loop and in system check adapter health checks, model export no longer doubles its flag validation error, and environment list unit tests are re-enabled with a corrected mock query URL. In the UI, adapter selection in MesheryPlayComponent works again, the schema version dropdown in LegacyRJSFModal renders correctly, and Notification Center file links no longer leak Blob object URLs. Docs fixes include 23 corrected in-page anchors and an updated Helm Snapshot page for the renamed helm-kanvas-snapshot plugin.
Week of October 19, 2026
What shipped
- Released Meshery v1.0.74, which includes the server fix for remote provider connection responses and the release workflow permission change that restores stable builds. Release
- Fixed the stable release workflow by granting the Helm chart releaser its token permissions, so releases build again after v1.0.72 and v1.0.73 failed at startup. Pull request #22521
- Server now accepts both shapes of remote provider connection responses, so it works as Layer5 Cloud moves registerConnection and connection listing to the schemas v1beta3 contract. Pull request #22520
- Mesheryctl perf profile and perf result now reject page values below 1 instead of sending page=-1 to the server. Pull request #22248
- Kubernetes dry-run validation now resolves resource endpoints through discovery instead of guessing plural names, and handles namespaces defined in the design. Pull request #22464
- Added how-to guides for deploying designs, sharing clusters, and running mesheryctl in CI. Pull request #22512
- Checked the infrastructure management guides against current UI, mesheryctl and server code and rewrote the stale ones as task-focused how-tos. Pull request #22510
- Checked the configuration management guides against current code and the UI form schemas and rewrote them in active voice. Pull request #22509
- Checked the performance management and telemetry guides against mesheryctl perf, the UI and the performance profile schema, fixing stale content. Pull request #22511
- Fixed two broken links in GOVERNANCE.md, pointing the community members link to its current location and updating the moved CNCF governance review template link. Pull request #22453
Why it matters
This week brought a stable release back online after two tags failed to build, and it shipped a server fix that keeps Meshery compatible with the v1beta3 connection contract. The CLI also stops sending invalid page values, and Kubernetes dry-run validation is more reliable for resources and namespaces defined in a design. Alongside that, large parts of the installation, configuration, performance and CLI documentation were checked against current code.
Changelog entry
- Release Meshery v1.0.74 Release
- Ci(release): grant the Helm chart releaser its token permissions Pull request #22521
- Fix(server): accept both remote provider connection response shapes Pull request #22520
- Mesheryctl: reject page values below 1 in perf profile and perf result Pull request #22248
- Fix(server): resolve dry-run resource endpoints and in-design namespaces Pull request #22464
- Docs: add guides for deploying designs, sharing clusters and running mesheryctl in CI Pull request #22512
- Docs: verify infrastructure management guides against code Pull request #22510
- Docs: verify configuration management guides against code Pull request #22509
- Docs: verify mesheryctl and troubleshooting guides against code Pull request #22508
- Docs: verify performance management and telemetry guides against code Pull request #22511
- Docs: correct the Kubernetes, Helm and platform install pages Pull request #22502
- Docs: fix two stale links in GOVERNANCE.md Pull request #22453
Meshery v1.0.74 is out, with the release workflow fixed so stable builds run again. This week also brought a fix for remote provider connection responses, stricter mesheryctl page checks, better Kubernetes dry-run validation, and a docs pass over guides checked against current co
Meshery v1.0.74 is released. The stable release workflow builds again after the token permission fix, and v1.0.74 carries the server change that accepts both remote provider connection response shapes. Also this week: mesheryctl perf profile and perf result reject page values below 1, Kubernetes dry-run validation resolves resource endpoints through discovery and handles in-design namespaces, and three new how-to guides cover deploying designs, sharing clusters and running mesheryctl in CI. The installation, configuration, performance, telemetry, troubleshooting and CLI guides were checked against current code and rewritten where stale, and two broken links in GOVERNANCE.md are fixed.
Week of October 12, 2026
What shipped
- Fixed a nil pointer panic in the GraphQL server resolver when ServiceMeshFilter is nil or has no type. Pull request #22419
- Fixed clicking the Meshery Server connection chip, which previously did nothing. Pull request #22332
- Fixed malformed Performance Profile run URLs when no Kubernetes contexts are selected. Pull request #22261
- Fixed workspace Edit and Delete actions to resolve the workspace by id instead of displayed row index. Pull request #21266
- Fixed the My Recent Designs widget error fallback in Local Provider mode. Pull request #22274
- Fixed docker not launching on macOS in mesheryctl by removing hardcoded paths. Pull request #22266
- Updated the playground cleanup workflow to point at the new OCI infrastructure. Pull request #21548
- Published Allure results after E2E failures so uploaded results stay visible in the dashboard. Pull request #22328
- Removed the AWS App Mesh adapter, which AWS stopped supporting. Pull request #22355
- Removed the NGINX Service Mesh adapter from the UI. Pull request #22013
Why it matters
This week brought fixes to several user-facing problems, including the Meshery Server connection chip, Performance Profile run URLs without Kubernetes contexts, and workspace Edit and Delete actions. It also cleaned up archived adapters such as AWS App Mesh and NGINX Service Mesh, and improved workflows and documentation paths for contributors.
Changelog entry
- Fix nil pointer panic in the GraphQL resolver when ServiceMeshFilter has no type. Pull request #22419
- Fix clicking the Meshery Server connection chip. Pull request #22332
- Fix malformed Performance Profile run URL when no Kubernetes contexts are selected. Pull request #22261
- Resolve workspace Edit and Delete actions by workspace id. Pull request #21266
- Fix My Recent Designs error in Local Provider mode. Pull request #22274
- Fix docker not launching on macOS in mesheryctl. Pull request #22266
- Update playground cleanup workflow to new OCI infrastructure. Pull request #21548
- Publish Allure results after E2E failures. Pull request #22328
- Remove the AWS App Mesh adapter. Pull request #22355
- Remove the NGINX Service Mesh adapter from the UI. Pull request #22013
- Add OSPS Baseline Scanner to SECURITY-INSIGHTS.yml. Pull request #22336
- Remove duplicated content from the Catalog page. Pull request #22340
This week: fixes for the Meshery Server connection chip, Performance Profile run URLs with no Kubernetes contexts, and workspace edit/delete actions. Archived adapters including AWS App Mesh and NGINX Service Mesh were removed.
This week in Meshery: we fixed several user-facing issues, including clicking the Meshery Server connection chip, malformed Performance Profile run URLs when no Kubernetes contexts are selected, and workspace Edit and Delete actions resolving the wrong workspace. The AWS App Mesh and NGINX Service Mesh adapters were removed from the UI and mesheryctl. We also updated the playground cleanup workflow, published Allure results after E2E failures, and corrected contributor documentation paths for the CLI and docs setup.
Week of October 5, 2026
What shipped
- Meshery v1.0.71 was released, removing the NGINX Service Mesh adapter from the server and install paths and referencing Sistent DESIGN.md in AGENTS.md UI guidelines. Release
- The NGINX Service Mesh adapter was removed from the server, including its ListAvailableAdapters entry and the nginx-system control plane namespace. Pull request #22012
- The NGINX Service Mesh adapter was removed from installation with the deletion of the meshery-nginx-sm Helm subchart and its chart dependencies. Pull request #22135
- Documentation for the NGINX Service Mesh adapter was removed, including the adapter page, its images and the nginx error reference export. Pull request #22124
- Leftover meshery-osm references were removed from mesheryctl's default adapter URLs, Docker image list and test fixtures. Pull request #22163
- Mesheryctl workspace create and environment create now call the marshal error function instead of the unmarshal one when serializing the request payload fails. Pull request #22269
- The design action dropdown now renders above the sticky toolbar by fixing the duplicated z-index defect in ActionButton and ActionPopover. Pull request #21735
- The visibility badge no longer overlaps the owner name on small screens because the Owner and Visibility columns in the legacy info modal now stack at a breakpoint. Pull request #21734
- The delete icon on dynamic additionalProperties key fields now renders with sufficient contrast in the UI. Pull request #21977
- Security-insights.yml was updated to the new schema as part of Security Slam Fall 2026 participation. Pull request #22270
Why it matters
This week the project removed the NGINX Service Mesh adapter from the server, installation and documentation, and dropped leftover meshery-osm references from mesheryctl, so users of those adapters should no longer expect them to be available. A mesheryctl error-reporting fix and several UI fixes improve workspace and environment creation and the readability of design and ownership controls on narrow screens.
Changelog entry
- Release Meshery v1.0.71, including the NGINX Service Mesh adapter removal and Sistent DESIGN.md reference in AGENTS.md. Release
- Remove the NGINX Service Mesh adapter from the server and its available-adapters list. Pull request #22012
- Remove the NGINX Service Mesh adapter from installation, including the Helm subchart and chart metadata. Pull request #22135
- Remove the NGINX Service Mesh adapter documentation, images and error reference export. Pull request #22124
- Remove leftover meshery-osm references from mesheryctl defaults and test configuration. Pull request #22163
- Fix mesheryctl workspace create and environment create to report marshal errors with the correct helper. Pull request #22269
- Raise the design action dropdown above the sticky toolbar. Pull request #21735
- Prevent the visibility badge from overlapping the owner name on small screens. Pull request #21734
- Fix low-contrast delete icon on dynamic key fields. Pull request #21977
- Correct the video prop data type in the Getting Started widget data definitions. Pull request #20520
- Update security-insights.yml to the new schema. Pull request #22270
- Update Yash Sharma's affiliation to UiPath in Community Maintainers. Pull request #22239
Meshery v1.0.71 is out. The NGINX Service Mesh adapter is removed from server, install and docs, and leftover meshery-osm references are gone from mesheryctl. mesheryctl workspace and environment create now report marshal failures correctly, and UI fixes raise the design action d
Meshery v1.0.71 is out. This release removes the NGINX Service Mesh adapter from the server, installation and documentation, and drops leftover meshery-osm references from mesheryctl adapter URLs, Docker image list and test fixtures. mesheryctl workspace create and environment create now report marshal failures with the correct error, and several UI fixes land: the design action dropdown renders above the sticky toolbar, the visibility badge no longer overlaps the owner name on small screens, and dynamic key delete icons are readable. AGENTS.md now points UI contributors to Sistent DESIGN.md, and security-insights.yml follows the new schema.
Week of September 28, 2026
What shipped
- Removed duplicate View Connection link from the Kubernetes connection import success toast. Pull request #21691
- Fixed missing error handling in DeleteContext that prevented proper event logging when context lookup failed. Pull request #22169
- Preserved design mode query parameter on post-login redirect to maintain deep-link functionality. Pull request #22157
- Fixed race condition in SeedKeys that dropped the last key and caused incomplete key seeding at boot. Pull request #22127
- Changed key seeding to report missing register column headers instead of silently persisting zero keys. Pull request #22128
- Prevented boot seeding stage panics from terminating the Meshery server. Pull request #22121
- Fixed broken relative links in UI contributing documentation. Pull request #22058
- Added test assertion that SaveEnvironment correctly refuses requests with 403 when lacking capability. Pull request #22120
Why it matters
This week focused on stability and correctness fixes in server boot seeding, error handling, and authentication workflows. Several race conditions and silent failures that affected initialization were resolved, ensuring more reliable startup and deeper test coverage for authorization enforcement.
Changelog entry
- UI: Removed duplicate View connections link from Kubernetes connection import success toast Pull request #21691
- Server: Added error return on GetK8sContext failure in DeleteContext to prevent event clobbering Pull request #22169
- Server: Keep deep-link query parameter on post-login redirect from Cloud Pull request #22157
- Server: Fixed SeedKeys race condition that dropped last key and buffered errors Pull request #22127
- Server: Report missing register column in keys.csv instead of silently seeding zero keys Pull request #22128
- Server: Prevent boot seeding stage panics from terminating the server Pull request #22121
- Docs: Fixed broken relative links in UI contributing documentation Pull request #22058
- Tests: Added assertion that SaveEnvironment returns 403 when capability is denied Pull request #22120
This week: fixed key seeding race conditions, improved DeleteContext error handling, preserved deep-link mode on login, and added authorization test coverage.
Meshery shipped critical stability fixes this week: resolved a race condition in SeedKeys that dropped the final key during boot, improved error handling in DeleteContext to prevent silent failures, preserved query parameters on post-login redirects to maintain deep-linking, and added test coverage for authorization enforcement.
Week of September 21, 2026
What shipped
- Fixed incorrect --component flag documentation in system command guide, correcting it to the actual Cobra flag --components (-a). Pull request #22057
- Removed obsolete Jekyll _includes/mesheryctl reference from CLI documentation guide. Pull request #22088
- Aligned security vulnerability reporting contact across documentation, AGENTS.md, and Security Insights manifests to use security@meshery.io. Pull request #22048
Why it matters
This week focused on documentation corrections and consistency. The flag syntax fix and obsolete reference removal improve accuracy for developers using mesheryctl. The security contact alignment ensures users report vulnerabilities to the correct address across all guidance materials.
Changelog entry
- Docs: Fix --components flag syntax in mesheryctl system command documentation Pull request #22057
- Docs: Remove obsolete Jekyll _includes/mesheryctl reference from CLI guide Pull request #22088
- Docs: Align security reporting contact to security@meshery.io across all documentation Pull request #22048
This week: fixed mesheryctl flag documentation, removed obsolete Jekyll references, and aligned security reporting contacts across Meshery docs.
Meshery shipped documentation improvements this week including corrected mesheryctl command flag syntax, removal of obsolete Jekyll references from CLI guides, and unified security vulnerability reporting contacts across all materials to ensure developers have accurate information.
Week of September 14, 2026
What shipped
- Meshery v1.0.70 released with dependency updates and CLI traceability improvements. Release
- Fixed invalid --adapter flag syntax in mesheryctl system check documentation. Pull request #22026
- Updated CLI command categories documentation to remove deprecated mesh and app commands. Pull request #21992
- Aligned mesheryctl model generate E2E tests with current CLI implementation. Pull request #21995
- Fixed mobile responsiveness CSS selector and parameter naming in extension-guide shortcode. Pull request #22030
- Refactored clipboard logic to fix tooltip race conditions in Remote Provider Info tab. Pull request #21575
- Fixed mesheryctl to check HTTP status codes before unmarshaling GitHub API responses. Pull request #21678
- Fixed CI workflow bug preventing welcome messages for first-time pull request contributors. Pull request #21979
- Migrated related reading sections to upstream module with Hugo configuration updates. Pull request #21759
- Added troubleshooting documentation for REST API authentication failures. Pull request #21928
Why it matters
This week focuses on documentation accuracy and developer experience improvements. Fixes to CLI command documentation, E2E tests alignment, and bug fixes in tooltip handling ensure users have correct guidance and reliable tooling. The v1.0.70 release consolidates these improvements for production deployment.
Changelog entry
- Release: Meshery v1.0.70 Release
- Docs: Fix invalid --adapter flag syntax in mesheryctl system check Pull request #22026
- Docs: Update CLI command categories, remove deprecated mesh and app commands Pull request #21992
- Mesheryctl: Align model generate E2E tests with current implementation Pull request #21995
- Docs: Fix mobile responsiveness CSS selector in extension-guide shortcode Pull request #22030
- Fix: Refactor clipboard logic and improve tooltip behavior in Remote Provider Info Pull request #21575
- Mesheryctl: Check HTTP status code before unmarshaling GitHub API response Pull request #21678
- CI: Fix PR welcome message not firing for first-time contributors Pull request #21979
- Docs: Migrate related reading sections to upstream module Pull request #21759
- Docs: Add troubleshooting note for REST API auth failures Pull request #21928
Meshery v1.0.70 ships CLI documentation fixes, E2E test improvements, and tooltip behavior refinements. Better docs, better tests, better experience.
Meshery v1.0.70 is out. This release includes critical documentation corrections for mesheryctl, alignment of model generation tests with current implementation, fixes to clipboard tooltip behavior in the Remote Provider Info tab, and improved HTTP error handling in GitHub API calls. We also fixed a CI workflow bug that prevented welcome messages for first-time contributors.