Supported Versions¶
Defines which MineProductivity releases and which Python versions receive support and fixes. Governed alongside the API Stability Policy.
1. Release support¶
| Version line | Status | Support |
|---|---|---|
3.x |
Current | Actively supported: bug fixes, security fixes, and backward-compatible improvements land here. |
2.x |
Previous major | Superseded by 3.0.0. Critical security fixes only, at maintainer discretion, until the next major. |
1.x and earlier |
End of life | Unsupported. Upgrade to 3.x. |
Only the latest MINOR of the current MAJOR is guaranteed to receive routine
fixes. Users on older MINORs of 3.x should upgrade to the latest 3.x before
requesting a fix.
2. Python support¶
| Python | Status |
|---|---|
| 3.13 | Supported (CI matrix) |
| 3.12 | Supported (CI matrix; minimum required) |
| ≤ 3.11 | Not supported (requires-python = ">=3.12") |
The CI test matrix runs the full suite on 3.12 and 3.13 across Linux, macOS,
and Windows. Adding or dropping a Python version is a MINOR change, announced in
CHANGELOG.md.
3. Operating systems¶
Install and smoke-test validation runs on Linux, macOS, and Windows
(ubuntu-latest, macos-latest, windows-latest) for every release build.
4. Dependencies¶
- The base install has zero third-party runtime dependencies.
- Optional features are pulled in via extras (
events,connectors,analytics,notebooks,enterprise,all); the toolchain viadev; docs viadocs. Version bounds are declared inpyproject.tomland pinned by major where a floor/ceiling matters for reproducibility. - The reporting/plotting stack (
matplotlib,PyYAML,reportlab) is confined to theenterpriseextra and the application layer (ADR-0012); the framework core ships no charting dependency.
5. Reporting an issue¶
When reporting a bug, include the output of:
Issues against end-of-life versions will be asked to reproduce on a supported release first.