Info Require Version

info-skill-require-version

info experience: versioning spec: info

Info MUST Have Version

Publishing a version for your OpenAPI technical contract helps you communicate change with consumers using Semantic or date-based versioning published to the info version property.

Rule definition

The full Spotlight rule — drop it into a ruleset (.spotlight.yaml / .spectral.yaml) and run it with any Spotlight tool.

info-skill-require-version:
  title: Info Require Version
  reference: https://spotlight-rules.com/spec/rules/openapi/info-skill-require-version/
  description: Publishing a version for your OpenAPI technical contract helps you
    communicate change with consumers using Semantic or date-based versioning
    published to the info version property.
  message: Info MUST Have Version
  severity: info
  given: $.info
  then:
    field: version
    function: truthy
  tags:
    - format:openapi
    - spec:info
    - experience:versioning
  prompt: "You are editing an OpenAPI document to satisfy the Spotlight API
    governance rule 'info-skill-require-version' (Info Require Version).
    Requirement: Publishing a version for your OpenAPI technical contract helps
    you communicate change with consumers using Semantic or date-based
    versioning published to the info version property. To fix: Ensure `version`
    is present and non-empty at each matching location. This rule is evaluated
    at the JSONPath `$.info` — inspect every location it matches and correct
    only what violates the rule. Make the smallest change that satisfies the
    rule, leave all unrelated content, key order, comments, and formatting
    unchanged, and keep the document valid OpenAPI. Return only the complete
    corrected document, with no commentary."
AI fix prompt — send this to Claude, Gemini, or ChatGPT with your artifact to auto-fix this rule
You are editing an OpenAPI document to satisfy the Spotlight API governance rule 'info-skill-require-version' (Info Require Version). Requirement: Publishing a version for your OpenAPI technical contract helps you communicate change with consumers using Semantic or date-based versioning published to the info version property. To fix: Ensure `version` is present and non-empty at each matching location. This rule is evaluated at the JSONPath `$.info` — inspect every location it matches and correct only what violates the rule. Make the smallest change that satisfies the rule, leave all unrelated content, key order, comments, and formatting unchanged, and keep the document valid OpenAPI. Return only the complete corrected document, with no commentary.
ArtifactOpenAPI
Applies at (given)$.info
Severityinfo — educational by default; raise to warn/error to enforce
Referencehttps://spotlight-rules.com/spec/rules/openapi/info-skill-require-version/