Versions
Documentation Versions
Choose the documentation release that matches your installed Composer packages and review which APIs were added during the v2.0 maintenance line.
Match the docs to what Composer actually installed.
The live documentation targets the current v2.0.6 mono release. Check the installed package before using a historical version note to reason about API availability.
Use the current docs for mnb/mnb-phpexcel 2.0.6.
When your lock file resolves an earlier patch, open that release note to confirm which APIs and behaviors were available at that point in the v2 maintenance line.
Open v2.0.6 notes →composer show mnb/mnb-phpexcel
composer show mnb/mnb-phpexcel-core
composer show mnb/mnb-phpexcel-xlsxComposer tags and the references recorded in composer.lock are authoritative for an installed project. A newer commit on the default branch does not update an existing tag.
Use release notes to locate when an API or behavior entered the documentation.
The version pages are concise maintenance notes, not complete frozen copies of the entire site.
Current mono-library release and the documentation target for this site.
Open v2.0.6 →Structured row-count summaries, including returned, empty, skipped, and logical row positions.
Open v2.0.5 →Developer-friendly global error rendering and nullable sheet helper behavior.
Open v2.0.4 →Active-sheet, sheet-existence, and empty-row utilities introduced during the v2 line.
Open v2.0.3 →Native XLS support, modular packages, and the coordinated v2 architecture baseline.
Open v2.0.0 →Separate installed code, current documentation, and release history.
That distinction prevents a common documentation mistake: assuming the newest source commit or current page automatically describes an older installed tag.
Use composer show and composer.lock to identify the exact package version your application is running.
Use the main site for the current v2.0.6 behavior, examples, and recommended workflows.
Use the version pages to confirm when specific APIs, fixes, or maintenance behavior appeared in the v2 line.