API Versioning
Configure structured version tracking for REST, GraphQL, gRPC, AsyncAPI, Webhook, and MCP API definitions with format-specific controls and automatic version suggestions.
NeoArc Studio supports structured version tracking for all API and schema definitions. Rather than a free-text version field, you choose a version format that determines how versions are validated, compared, and displayed. This applies consistently across REST, GraphQL, gRPC, AsyncAPI, Webhook, and MCP API types, as well as shared schemas.
Version Formats
Select a version format from the dropdown on any API or schema home form. The version input control adapts to show format-appropriate fields.
Setting a Version Format
Versioning Model
The version format field tells the system how to parse, compare, and suggest version numbers. It does not change the fundamental versioning model in NeoArc, which is based on directory-level forking.
Version Comparison and Suggestions
The version utility system provides automatic version comparison and next-version suggestions based on detected change categories. When a breaking change is detected, the system can suggest a major version bump. Additive changes suggest a minor bump (for semantic and major.minor formats). Patch-level bumps apply only to the semantic format for cosmetic changes.