OSSA Versioning Strategy
OSSA follows Semantic Versioning 2.0.0 with specific guidelines for specification evolution.
Version Format
MAJOR.MINOR.PATCH
Example: 0.2.4
Version Increments
MAJOR (Breaking Changes)
Increment when making incompatible changes: - Removing required fields - Changing field types - Removing supported runtime types - Breaking schema validation
Example: 1.0.0 → 2.0.0
MINOR (New Features)
Increment when adding backwards-compatible functionality: - Adding new optional fields - Adding new runtime types - Adding new agent roles - Extending capabilities
Example: 0.2.0 → 0.3.0
PATCH (Bug Fixes)
Increment for backwards-compatible bug fixes: - Documentation clarifications - Schema validation fixes - Example corrections
Example: 0.2.3 → 0.2.4
Current Version
Latest: v0.2.4 (January 2025)
Changelog
v0.2.4 (2025-01-15)
- Enhanced security schema
- Added monitoring configuration
- Improved model parameters
- Documentation updates
v0.2.3 (2024-12-20)
- Added edge runtime support
- Enhanced dependency management
- Improved examples
v0.2.0 (2024-11-15)
- Major specification redesign
- New agent roles (governor, worker, critic, observer)
- Enhanced capability schema
- Runtime configuration
v0.1.9 (2024-10-01)
- Legacy version
- See Migration Guide
Migration Support
We maintain migration paths between versions:
# Migrate from v0.1.9 to v0.2.x
ossa migrate agent-v0.1.yml --output agent-v0.2.yml
See Migration Guides for detailed instructions.
Deprecation Policy
- Deprecation Notice: 2 minor versions before removal
- Breaking Changes: Only in major versions
- Support Period: 12 months for each major version