The package declares three Mautic major versions
The 0.9.4 package declares mautic/core-lib ^5.0 || ^6.0 || ^7.0, PHP ^8.1, Guzzle ^7.0, and ext-zip; its README names MySQL 5.7+ or MariaDB 10.3+, but no tested matrix or date is recorded. Its changelog records 0.9.4 filtering/display fixes, a 0.9.3 modal post-save rendering fix, 0.9.2 replacing the defective, withdrawn 0.9.1 archive with a complete, verified build, and 0.9.0 download/apply/rollback commands with isolated staging. These are the artifact-evidence boundaries for Deal Flow.
Last-tested date: not recorded in the shipped artifacts; package requirements re-verified 2026-08-23.
Verification basis (2026-08-23): the served DealFlowBundle-latest.zip archive, the installation documentation, and the full changelog.
Declared compatibility matrix
| Component | Declared requirement | Evidence status |
|---|---|---|
| Mautic 5.x | mautic/core-lib ^5.0 |
Declared by the 0.9.4 package; an actual tested combination is not recorded. |
| Mautic 6.x | mautic/core-lib ^6.0 |
Declared by the 0.9.4 package; an actual tested combination is not recorded. |
| Mautic 7.x | mautic/core-lib ^7.0 |
Declared by the 0.9.4 package; an actual tested combination is not recorded. |
| PHP | ^8.1 |
Declared package constraint; tested PHP versions are not recorded. |
| HTTP client | Guzzle ^7.0 |
Declared package constraint. |
| PHP extension | ext-zip |
Declared package requirement. |
| Database | MySQL 5.7+ or MariaDB 10.3+ | Documented in the shipped README; a tested matrix is not recorded. |
Declared compatibility is not recorded test coverage
A dependency constraint tells the package manager which dependency ranges the release declares. It does not, by itself, show which exact Mautic, PHP, database, and operating-system combinations were exercised before release.
How to read this matrix: treat each row as a declared requirement. Do not relabel it as tested or certified unless a dated test record is published.
Use the install and uninstall page for the verified archive and update commands, including the file-only rollback boundary.
Current archive verification
The served DealFlowBundle-0.9.4.zip and DealFlowBundle-latest.zip files were SHA-identical when re-verified on 2026-08-23. That observation is dated: the latest alias can change when a later release is published.
The served 0.8.7 archive and 0.8.8 archive were also available when checked on 2026-08-23. Their availability is not used here to invent release notes that the current verified evidence does not establish.
Release notes verified from the current archive
0.9.4 — 2026-06-10
- Fixed task queue filtering.
- Fixed release-date display.
0.9.3
- Fixed modal post-save rendering: saving worked, but the raw AJAX response was displayed instead of the board.
0.9.2
- Replaced the defective, withdrawn 0.9.1 archive with a complete, verified build.
0.9.0
- Introduced the
dealflow:updateCLI download, apply, and rollback operations. - Introduced isolated staging for the update flow.
These summaries come from DealFlowBundle/CHANGELOG.md inside the current 0.9.4/latest package. See the existing full changelog page for the broader site record.
Compare these declared requirements with the exact environment you plan to operate.
Explore Deal Flow Try free for 7 daysFrequently asked questions
Does a declared package constraint prove that Deal Flow was tested on that version?
No. The 0.9.4 package declares Mautic core constraints for major versions 5, 6, and 7, but the shipped artifacts do not record an actually tested version matrix or test date.
When was the Deal Flow compatibility evidence last verified?
Last-tested date: not recorded in the shipped artifacts; package requirements re-verified 2026-08-23.
Which release notes are verified from the latest archive?
The latest archive records 0.9.4 fixes for task queue filtering and release-date display, a 0.9.3 fix for modal post-save rendering, 0.9.2 replacing the defective, withdrawn 0.9.1 archive with a complete, verified build, and 0.9.0 download, apply, and rollback commands with isolated staging.
Are DealFlowBundle-0.9.4.zip and DealFlowBundle-latest.zip the same package?
Yes at the 2026-08-23 verification point. The two served archives were SHA-identical. That is a dated artifact check, not a promise that the latest alias will always point to 0.9.4.