Repository navigation
fix(openapi): add missing fields to the Actor definition schema - #3115
Merged
Merged
Conversation
vdusek
added
adhoc
vdusek
marked this pull request as ready for review
October 26, 2026 10:39
Contributor
|
🗑️ Preview for this PR was deleted. |
Contributor
|
API behavior and specification alignment: Aligned. Reviewed commit: 27ff249 |
Pijukatel
approved these changes
Oct 26, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The build stores the whole
actor.jsonasactorDefinition, andGET /actor-builds/{buildId}returns it in full, but the schema only described part of it. This adds the missing fields:title,description,meta,output,storages.datasets,storages.keyValueStore,webServerSchema, andwebServerMcpPath.metalives in its ownActorDefinitionMetaschema so generated clients get a named model for it.The Python client needs
webServerSchemato read a Server Actor's OpenAPI spec (apify/apify-client-python#1153). I checked the generated Python models against this spec, and the client's type check and unit tests pass.✍️ Drafted by Claude Code