Meshery
v1.0.74Provisioning & RuntimeOct 22, 2026
A focused maintenance release fixes remote-connection compatibility and broadens successful response handling. It requires no operator migration.
All 5 other recorded changesconstraints 2 · value changes 2 · fixes 1
constraints (2)
- -
DeleteConnection: any 2xx is success. A 204 or an empty body returns a connection that carries the deleted id, so callers can still dereference it. A JSON body can be a bare Connection or a page. - -
DeleteMesheryConnection: any 2xx is success.
value changes (2)
- -
registerConnection(POST /api/integrations/connections) will return 201 with theConnectionitself. Today it returns a one-item connection page. - -
deleteConnection(DELETE /api/integrations/connections/{connectionId}) will return 204 with no body. Today it returns 200 with a body. This change lets Meshery Server's remote provider accept both shapes, so it works against current Cloud and the new contract:
fixes (1)
- - fix(server): accept both remote provider connection response shapes (#22520). Shipped in v1.0.73, whose stable build did not start.
Add Meshery to your stack
A weekly email arrives when a release needs action. Weeks with nothing to act on, like this one, send no email.