You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
PUT /api/v1/pipelines/:id declares a flat body but reads a nested one #8583
PUT /api/v1/pipelines/:id {"name":"flat rename"}
500 {"code":"unexpected_error","error":"TypeError: Cannot read properties of undefined (reading 'name')"}
while the undocumented shape works:
PUT /api/v1/pipelines/:id {"pipeline":{"name":"nested rename"}}
200 {"id":"...","name":"nested rename","stages":[]}
The route's own tests use the nested shape, so the handler is probably what's intended and the schema is what's wrong. Either way the two disagree, anything generated from the OpenAPI spec will send the flat shape, and the failure is a 500 carrying a raw TypeError rather than a 400.
Activity