NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Packagist
Packagist, #2799 most downloaded on Packagist
Doctrine multi-platform support for spatial types and functions, compliant with Doctrine 2.19, 3.1, and dev ones (3.2 and 4.0).
Latest stable
6.0.0
Last release 2 months ago
12 Sep 2026
Release timing varies
gaps range from 9 days to 1.2 years
Nearly every release is documented
notes for 16 of 17 stable releases
Nothing withdrawn
no release was ever pulled
5 years old
24 releases · first in 2021
Drag across the ruler to compare, or tap a release to open it.
add deprecation handling for SpBuffer DQL function in MariaDB and MySQL
Your coding agent can read these notes before it upgrades. Set up the MCP server →
add deprecation handling for SpBuffer DQL function in MariaDB and MySQL
Replacing coveralls.io by codecov.io by @Alexandre-T in https://github.com/longitude-one/doctrine-spatial/pull/144
Full Changelog: https://github.com/longitude-one/doctrine-spatial/compare/5.0.4...5.0.5
Full Changelog: 5.0.4...5.0.5
Mr 97 : Support for MariaDB by @PowerKiKi in https://github.com/longitude-one/doctrine-spatial/pull/117
Full Changelog: https://github.com/longitude-one/doctrine-spatial/compare/5.0.3...5.0.4
Full Changelog: 5.0.3...5.0.4
Version 5.0.4 improved contributor and CI tooling rather than changing the public spatial API. It added explicit container platforms for PostGIS and MySQL, corrected Docker and installation instructions, added repository attributes, removed the redundant ext-json requirement, and updated PHP CodeSniffer, PHP CS Fixer, PHP Mess Detector, PHPStan, and their dependencies. The release also incorporated MariaDB support work from the main branch.
PHPDOC optimized by @Alexandre-T in https://github.com/longitude-one/doctrine-spatial/pull/90
Full Changelog: https://github.com/longitude-one/doctrine-spatial/compare/5.0.2...5.0.3
Full Changelog: 5.0.2...5.0.3
Version 5.0.3 extended ST_SRID() support to accept two parameters. It added a PostgreSQL-specific SRID function, deprecated use of the standard SRID function on PostgreSQL, and included tests for the new behaviour and the emitted deprecations.
Throw deprecations when developers don't use next gen standard constr… by @Alexandre-T in https://github.com/longitude-one/doctrine-spatial/pull/82
Full Changelog: https://github.com/longitude-one/doctrine-spatial/compare/5.0.1.RC...5.0.2
Full Changelog: 5.0.1.RC...5.0.2
Version 5.0.2 addressed a false positive that reported the SQL Server platform as unavailable. The surrounding maintenance work also covered an edge case in isClosed for empty line strings, documentation adjustments, and quality-tool baseline updates, keeping the patch focused on reliable platform detection and regression coverage.
72 GitHub actions the set-output command is deprecated by @Alexandre-T in https://github.com/longitude-one/doctrine-spatial/pull/74
set-output command is deprecated by @Alexandre-T in https://github.com/longitude-one/doctrine-spatial/pull/74Full Changelog: https://github.com/longitude-one/doctrine-spatial/compare/5.0.0...5.0.1.RC
Version 5.0.1 corrected an unexpected conversion of coordinate values while storing points. It also separated geodetic and Cartesian coordinates through new interfaces, introduced an internal RangeException, resolved the related issues, and refined CI so that duplicate checks are avoided across pushes and pull requests.
Update copyrights and fix #44 by @Alexandre-T in https://github.com/longitude-one/doctrine-spatial/pull/45
Full Changelog: https://github.com/longitude-one/doctrine-spatial/compare/4.0.0...5.0.0
Version 5.0.0 focused on compatibility with modern Doctrine ORM versions: it added support for Doctrine ORM 2.19 and 3.1, with testing also performed against the 3.2 and 4.0 development lines. The release upgraded Composer, PHPUnit, parsers, GitHub Actions, and the quality-tool suite; removed deprecated APIs; strengthened the test harness and coverage workflow; and introduced interfaces and return types that prepared the library for later releases.
Closes #19 by @Alexandre-T in https://github.com/longitude-one/doctrine-spatial/pull/33
Full Changelog: https://github.com/longitude-one/doctrine-spatial/compare/3.0.2...4.0.0
Version 4.0.0 modernized the parsing layer by adopting longitude-one/wkt-parser and subsequently pinning it to the 1.0 release. It removed support for PHP 7.4 and PHP 8.0, migrated test fixtures from annotations to attributes, improved cross-platform floating-point tests, and refreshed the CI and code-quality configuration. These changes established the technical baseline for the 4.x series.
Fixing some comments by @Alexandre-T in https://github.com/longitude-one/doctrine-spatial/pull/38
Full Changelog: https://github.com/longitude-one/doctrine-spatial/compare/4.0.0-rc1...4.0.0-rc2
Migrate tests from annotations to attributes, fixes for doctrine/annotation 2
Full Changelog: https://github.com/longitude-one/doctrine-spatial/compare/3.0.2...4.0.0-rc1
Tests now run in the same action to avoid unnecessary CPU usage and power wastage.
Removing deprecation due to doctrine and class ORMException ;
Nothing published for this version
Test upgraded. Weak code detected by PhpStorm fixed. Documentation up to date. Code coverage improved.
Test upgraded. Weak code detected by PhpStorm fixed. Documentation up to date. Code coverage improved.
If no issues are detected, Version 3.0 will be release August 17th.
No changes inside the core of the library, but test have been improved and simplified.
No changes inside the core of the library, but test have been improved and simplified.
Version 3.0 will be released last week of July.
removing deprecated methods PHPUnit::Mock::setMethods
As the creof team doesn't have anymore time to maintain their awesome spatial extension for doctrine (creof/doctrine2-spatial), this package replaces
As the creof team doesn't have anymore time to maintain their awesome spatial extension for doctrine (creof/doctrine2-spatial), this package replaces it.
This package starts as the third version, because last release of creof/doctrine2-spatial is 2.0.
Look at the Changelog, to know each updates, but the essential is:
This package includes improvements in the PR#209
add deprecation handling for SpBuffer DQL function in MariaDB and MySQL
Full Changelog: https://github.com/longitude-one/doctrine-spatial/compare/5.0.5...6.0.0.RC.0
72 GitHub actions the set-output command is deprecated by @Alexandre-T in https://github.com/longitude-one/doctrine-spatial/pull/74
set-output command is deprecated by @Alexandre-T in https://github.com/longitude-one/doctrine-spatial/pull/74Full Changelog: https://github.com/longitude-one/doctrine-spatial/compare/5.0.0...5.0.1.RC
set-output command is deprecated by @Alexandre-T in #74Full Changelog: 5.0.0...5.0.1.RC
If no issues are reported, the 5.0.0 will be released on May 15th.
If no issues are reported, the 5.0.0 will be released on May 15th.
Full Changelog: https://github.com/longitude-one/doctrine-spatial/compare/5.0.0.RC3...5.0.0.RC4
If no issues are reported, the 5.0.0 will be released on May 15th.
If no issues are reported, the 5.0.0 will be released on May 15th.
Full Changelog: https://github.com/longitude-one/doctrine-spatial/compare/5.0.0.RC2...5.0.0.RC3
If no issues are reported, the 5.0.0 will be released on May 15th.
Full Changelog: 5.0.0.RC2...5.0.0.RC3
Update copyrights and fix #44 by @Alexandre-T in https://github.com/longitude-one/doctrine-spatial/pull/45
Full Changelog: https://github.com/longitude-one/doctrine-spatial/compare/4.0.0...5.0.0.RC2
Full Changelog: 4.0.0...5.0.0.RC2
I've made significant progress! Because the current dev branch is already compatible with all doctrine/orm versions!
dev branch is already compatible with all doctrine/orm versions!
All tests are passing successfully.
The three dependencies, longitude-one/geo-parser:3.0.0, longitude-one/wkt-parser:3.0.0 and longitude-one/wkb-parser:3.0.0 are working flawlessly. Compatibility is achieved, I'm already able to publish longitude-one:doctrine-spatial/5.0.0.RC 🎉🎉🎉.
The final release will depend on your feedbacks., I'm confident I can publish the 5.0.0 final version by May 14th.
One column per quarter.