Skip to content

docs(dataset-schema): three non-functional "version": "1.0.0" examples in actor.json snippets #2740

Description

@DaveHanns

Problem

The dataset-schema documentation page at sources/platform/actors/development/actor_definition/dataset_schema/index.md contains three inline actor.json examples that use "version": "1.0.0" (3-part SemVer):

  • Line 50
  • Line 136
  • Line 159

All three are non-functional as-is on the platform — the admission gate at POST /v2/acts/{id}/versions validates against the strict MAJOR_MINOR_VERSION_REGEX in apify-core (src/packages/simple-schema/src/regexs.ts:2):

^([0-9]|[1-9][0-9])\.([0-9]|[1-9][0-9])$

This regex accepts only 2-part MAJOR.MINOR with each segment 0-99. Any user who copies these examples verbatim and runs apify push gets a cryptic admission failure. Direct contradiction with the actor.json reference page on the same site, which correctly documents 2-part versions.

Empirically verified 2026-06-17 on test Actor pYSXdpQa55nSb6SID: "version": "1.0.0" is rejected at the platform edge with MAJOR_MINOR_VERSION_REGEX mismatch.

Suggested change

  1. Change all three "version": "1.0.0" examples to "version": "1.0".

  2. Add a short callout admonition near the first example:

    Note: The Apify platform requires the version field in actor.json to be in MAJOR.MINOR format (each segment 0-99). Three-part SemVer strings like "1.0.0" are rejected at build admission.

Related

  • Cross-ref sibling fixes:
    • @apify/json_schemas actor.schema.json regex is too loose (accepts 3-part) — separate issue against apify-shared-js.
    • apify-cli should validate MAJOR.MINOR before uploading — separate PR against apify-cli.
  • Contradicting page on the same docs site: actor.json reference.

Impact

Medium. Mis-teaches every user (and every agent that crawls Apify docs for examples) that 3-part SemVer is valid. Observed in every low-context agent run so far — the canonical 1.0.0 fallback comes straight from these docs.


Surfaced during an evaluation of Apify surfaces for agent-driven Actor development.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions