Piper Morgan Versioning Strategy

Current Version: 0.8.5

Versioning Scheme

Piper Morgan follows Semantic Versioning (SemVer) with the following format:

MAJOR.MINOR.PATCH[-PRERELEASE]

Version Components

Current Versioning Strategy

Pre-1.0 (Alpha Phase)

Post-1.0 (Production)

Version Sources of Truth

Primary Version Definition

Version References

Roadmap vs. Version Separation

Important: Roadmap positions (e.g., “2.7.5”, “Sprint A8”) are separate from software versions.

This separation allows:

Version Management

Manual Process (Current)

  1. Update VERSION file
  2. Update pyproject.toml version field
  3. Update relevant documentation
  4. Create git tag for releases

Future Automation (Planned)

Alpha Testing Versions

During alpha testing, versions follow this pattern:

Version History

Version Date Milestone Notes
0.8.5 Jan 2026 MUX MUX-IMPLEMENT complete, WCAG 2.1 AA accessibility
0.8.4.3 Jan 2026 Sprint A20 Fresh install fixes (#605-#609), UI polish
0.8.4.2 Jan 2026 Sprint A20 Calendar bug fixes (#596, #588)
0.8.4.1 Jan 2026 Sprint A20 Calendar/TEMPORAL timezone fixes
0.8.4 Jan 2026 Sprint B1 Integration Settings, Portfolio Onboarding
0.8.3.2 Jan 2026 Sprint B1 Interactive Standup Assistant (Epic #242)
0.8.3.1 Jan 2026 Sprint B1 FTUX improvements
0.8.3 Jan 2026 Sprint A17 Epic #314 CONV-UX-PERSIST complete
0.8.2 Dec 2025 Sprint A13 UX polish, accessibility improvements
0.8.1 Nov 2025 Sprint A9 Bug fixes and improvements from alpha testing
0.8.0 Oct 2025 Sprint A8 Alpha tester onboarding preparation
1.0.0 TBD MVP Target MVP release

Guidelines for Contributors

  1. Never tie versions to roadmap positions
  2. Update VERSION file first, then pyproject.toml
  3. Use semantic versioning principles
  4. Document breaking changes clearly
  5. Test version references in documentation

Last updated: January 27, 2026 Current version: 0.8.5