From fbed2a142ab4eba8f16fa43dbd335634e6ac8b5b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Mat=C4=9Bj=20Volf?= Date: Sat, 22 Nov 2025 14:07:32 +0100 Subject: [PATCH] Clarify default build version for resurrected run --- .../openapi/paths/actor-runs/actor-runs@{runId}@resurrect.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/apify-api/openapi/paths/actor-runs/actor-runs@{runId}@resurrect.yaml b/apify-api/openapi/paths/actor-runs/actor-runs@{runId}@resurrect.yaml index 1df4b2feb..f1ee1317f 100644 --- a/apify-api/openapi/paths/actor-runs/actor-runs@{runId}@resurrect.yaml +++ b/apify-api/openapi/paths/actor-runs/actor-runs@{runId}@resurrect.yaml @@ -24,7 +24,7 @@ post: schema: type: string example: 0.1.234 - description: Specifies the Actor build to run. It can be either a build tag or build number. By default, the run uses the build specified in the run that is being resurrected (typically `latest`). + description: Specifies the Actor build to run. It can be either a build tag or build number. By default, the run is resurrected with the same build that it originally used. Specifically, if a run is first started with the `latest` tag, which resolves to version `0.0.3` at the time, a run resurrected without the `build` parameter will continue running with the version `0.0.3`, even if the `latest` tag already points to a newer build. - name: timeout in: query required: false