fix: add CI and MCP to MetaOrigin enum#73
Merged
Conversation
Pijukatel
approved these changes
Jul 8, 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.
Add the two
MetaOriginvalues the platform already emits but the Python enum was missing, bringing it to parity withapify-shared-js:MCP— runs started through the Apify client triggered from the Apify MCP server.CI— runs started from a CI/CD pipeline (e.g. GitHub Actions).Without
MCP, any Actor invoked via the Apify MCP server crashes at startup: the released SDK line (apify3.4.x) validatesrun.meta.originagainstapify_shared.consts.MetaOrigin, and an unknown value raises apydantic.ValidationErrorbefore user code runs.Related: apify/apify-sdk-python#1032. The API OpenAPI spec is fixed in parallel (apify/apify-docs#2752), which covers the SDK master line that reads the enum from
apify-clientv3.