Versioning Policy
PAM follows semantic versioning for the specification:
Major Versions (e.g., 1.0 → 2.0)
Section titled “Major Versions (e.g., 1.0 → 2.0)”Breaking changes to required fields or schema structure. Examples:
- Removing or renaming required fields
- Changing the structure of core objects
- Modifying the content hash algorithm
Major versions get a new permanent URL (e.g., /spec/v2.0). Previous versions remain accessible.
Minor Versions (e.g., 1.0 → 1.1)
Section titled “Minor Versions (e.g., 1.0 → 1.1)”Backwards-compatible additions. Examples:
- New optional fields
- New memory types
- New relation types
- Additional provider mappings
Existing valid PAM files remain valid under minor version updates.
Patch Versions (e.g., 1.0.0 → 1.0.1)
Section titled “Patch Versions (e.g., 1.0.0 → 1.0.1)”Clarifications and errata only. No changes to the schema or required behavior.
Process
Section titled “Process”- Changes are proposed via GitHub issues
- Discussion happens publicly on the issue
- Spec changes are submitted as pull requests
- PRs require a public review period before merging
- New versions are tagged in the spec repository