Skip to main content

Publish Test Plan Version

POST 
/test-plans/:ref/versions

Publish the next version of the plan ref names — the deliberate edit.

Everything a create does, plus two checks a create cannot make. ref has to resolve to a plan that exists, so an edit aimed at nothing is a 404 rather than a new plan nobody meant to start. And plan.name has to agree with the plan being edited, so an edit cannot rename its way onto another plan's history — renaming is publishing a new plan, which is the create route.

base_version is optional and checked after the replay lookup: an edit that declares the version it was made from is refused when that is no longer the latest, so two people editing the same version produce one publish and one 409 rather than two silently stacked versions.

Request​

Responses​

Successful Response