@celigo/api-specs 0.2.139 → 0.2.140

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/dist/tool.yml CHANGED
@@ -1224,8 +1224,9 @@ paths:
1224
1224
  $ref: '#/components/responses/404-not-found'
1225
1225
  '422':
1226
1226
  description: |-
1227
- The Tool ran but a step failed. Includes `invocationId` when logging is active, so
1228
- the failed run can be opened in the run history.
1227
+ A step failed, or the Tool was refused before any step ran because its branches
1228
+ don't all merge back (`tool_dangling_branch`). Either way the response includes
1229
+ `invocationId` when logging is active, so the run can be opened in the run history.
1229
1230
  content:
1230
1231
  application/json:
1231
1232
  schema:
@@ -2398,6 +2399,11 @@ paths:
2398
2399
  `GET /v1/tools/{_id}/test/run/{runId}/{_stepId}` to inspect stage-by-stage
2399
2400
  results. The run id for follow-up calls is the `flowJob._id` value.
2400
2401
 
2402
+ A test run is not free of outside calls: lookups call their sources live. Imports never
2403
+ send; each returns its saved `mockResponse`, or a placeholder response when none is saved
2404
+ (see `mockResponse` on imports). A second test run started while one is still running is
2405
+ refused with `test_run_not_allowed`.
2406
+
2401
2407
  Test runs are a separate, short-lived history from normal runs — capture
2402
2408
  any follow-up step or log details soon after the run completes.
2403
2409
  operationId: testRunTool
@@ -2520,7 +2526,14 @@ paths:
2520
2526
  status: completed
2521
2527
  numError: 1
2522
2528
  '400':
2523
- $ref: '#/components/responses/400-bad-request'
2529
+ description: |-
2530
+ The run was refused before any step ran. A Tool with no steps fails with
2531
+ `tool_empty_router`, and one whose branches don't all merge back with
2532
+ `tool_dangling_branch`; re-running the same document fails the same way.
2533
+ content:
2534
+ application/json:
2535
+ schema:
2536
+ $ref: '#/components/schemas/Error'
2524
2537
  '401':
2525
2538
  $ref: '#/components/responses/401-unauthorized'
2526
2539
  '404':
@@ -19863,7 +19876,7 @@ components:
19863
19876
  without the array); a mapping reshapes the message instead.
19864
19877
  - |-
19865
19878
  Publishing is not limited to flows. Verified surfaces: a flow step; an API step (the API
19866
- invoked at `POST /apis/{version}/{relativeURI}`); a Tool reached through a `ToolImport`
19879
+ invoked at `POST /apis/{version}{relativeURI}`); a Tool reached through a `ToolImport`
19867
19880
  step in a flow; and `POST /v1/imports/{_id}/invoke` with `{"data": [record, ...]}`. A flow
19868
19881
  or API test run (`/test/run`) publishes nothing — import steps are mocked there.
19869
19882
  properties:
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@celigo/api-specs",
3
- "version": "0.2.139",
3
+ "version": "0.2.140",
4
4
  "private": false,
5
5
  "description": "Public OpenAPI bundles (dist/) and the celigo-cli lint schema pack (schemas.json).",
6
6
  "keywords": [