NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Packagist
Packagist, #3945 most downloaded on Packagist
Adjacency List’ed Closure Table database design pattern implementation for Laravel
Latest stable
v6.2.2
Last release 9 months ago
01 Feb 2026
Ships unpredictably
gaps range from 2 weeks to 5.3 years
Most releases are documented
notes for 26 of 30 stable releases
Nothing withdrawn
no release was ever pulled
13 years old
30 releases · first in 2013
Drag across the ruler to compare, or tap a release to open it.
Column disambiguation in closure table queries (#252) by @franzose in https://github.com/franzose/ClosureTable/pull/284 (originally @Djuuu in https://
Full Changelog: https://github.com/franzose/ClosureTable/compare/v6.2.1...v6.2.2
feat: add parent_id column to fillable at construct by @penerbangkode in https://github.com/franzose/ClosureTable/pull/257
Full Changelog: https://github.com/franzose/ClosureTable/compare/v6.2...v6.2.1
Your coding agent can read these notes before it upgrades. Set up the MCP server →
Thanks to @devig who pointed this out in #234. This issue has been moved to #238 and fixed by this release.
Thanks to @devig who pointed this out in #234. This issue has been moved to #238 and fixed by this release.
Laravel 8 support in tests, thanks to @avvertix
Entity::parent() many-to-one relationship to the direct ancestor nodeThis is a small release which brings a fix to the regression pointed out by @ritterg.
This is a small release which brings a fix to the regression pointed out by @ritterg.
Fixes and improvements by @dcanaud and @gulch.
Fixes and improvements by @dcanaud and @gulch.
Nothing published for this version
Nothing published for this version
I introduced params binding for raw queries in ClosureTable model.
I introduced params binding for raw queries in ClosureTable model.
I have removed checks for ancestor and descendant arguments to be integers because there are situations when one needs to use another column type.
I have removed checks for ancestor and descendant arguments to be integers because there are situations when one needs to use another column type.
Another Composer dependency fix.
Another Composer dependency fix.
Nothing published for this version
In this release, I added the third optional argument to addChild() and addSibling() methods that allows you to get the child or sibling that's being a
In this release, I added the third optional argument to addChild() and addSibling() methods that allows you to get the child or sibling that's being added to an ancestor. Please, explore readme for the examples.
Nothing published for this version
Many many fixes. Huge thanks to @tomzx for help. Also thanks to all guys who discovered the issues.
Many many fixes. Huge thanks to @tomzx for help. Also thanks to all guys who discovered the issues.
Fixed generator that stripped out the first letter of the models. Fixed entity migration stub, made parent_id column unsigned to prevent foreign key c
Fixed generator that stripped out the first letter of the models. Fixed entity migration stub, made parent_id column unsigned to prevent foreign key constraints. Thanks to @kmccarthyweb for the issues.
Finally, I hope that it is, I fixed nodes reordering and moving bugs. Real depth of all descendants of a node now is updated properly when the node is
Finally, I hope that it is, I fixed nodes reordering and moving bugs. Real depth of all descendants of a node now is updated properly when the node is moved somewhere. Also I added guessing of closure table name if its default model class (i.e. Franzose\ClosureTable\Models\ClosureTable) is not changed to something else.
P.S. Highly recommended for you to update your ClosureTable to this release.
Fixed suddenly arisen issues with reordering siblings.
Fixed suddenly arisen issues with reordering siblings.
Fixed wrong behaviour after appendChild with $returnChild = true, when retrieving of siblings led to wrong results.
Fixed wrong behaviour after appendChild with $returnChild = true, when retrieving of siblings led to wrong results.
Fixes: 1. #27, database table prefix led to wrong closure table name. 2. #25, wrong behaviour happened while moving a descendant to a new ancestor by
Fixes:
fix: handle root sibling ordering and add tests by @franzose in https://github.com/franzose/ClosureTable/pull/259
Full Changelog: https://github.com/franzose/ClosureTable/compare/v6.1.1...v6.2
Franzose\ClosureTable\Contracts\EntityInteface has been deprecated and will be removed in the next major release
real_depth attribute & database column have been deprecated and are not included in the generated model and migration anymorePHP 5.6 support has been dropped. Starting from this release, ClosureTable supports PHP 7.0 and higher.
Thanks to @dcanaud, the package now supports Laravel 5.5.
Thanks to @dcanaud, the package now supports Laravel 5.5.
Thanks to @krutuzick pull request, the library now supports Laravel 5.4+.
Thanks to @krutuzick pull request, the library now supports Laravel 5.4+.
Added support for Laravel 5.2 + other fixes.
Added support for Laravel 5.2 + other fixes.
Big big thanks to @EspadaV8 work! Now that his pull request has been accepted we can release a new package version. ClosureTable 4 fully supports Lara
Big big thanks to @EspadaV8 work! Now that his pull request has been accepted we can release a new package version. ClosureTable 4 fully supports Laravel 5 and also follows PSR-2 coding standard. Stay enjoing hierarchical relations!
In this release, issues with removeChild and deleteSubtree methods have been resolved. If you have already been using the package, please set on delet
In this release, issues with removeChild and deleteSubtree methods have been resolved. If you have already been using the package, please set on delete set null constraint to the parent_id foreign key on your entity table, if that constraint has not been set yet.
The new version introduces an injection of the Adjacency List pattern to the pure Closure Table. Adjacency list's features allows to simplify most of
The new version introduces an injection of the Adjacency List pattern to the pure Closure Table. Adjacency list's features allows to simplify most of the database queries dramatically. In the new version, all the existed bugs were fixed. I also introduced a method, that the community requested long ago. It is called createFromArray and is used to create a bunch of records by just passing an array of attributes to it.
However, the feature I mentioned is not the only thing I added while developing the 3.0. Explore the source!
Introducing filteredTree method, see #18. You can use it when it's necessary to get a tree, filtered by some condition.
In this release:
filteredTree method, see #18. You can use it when it's necessary to get a tree, filtered by some condition.\Franzose\ClosureTable\Collection when tree is empty).Thanks to @vjandrea for the first two improvements.
Now the package for Laravel 4. It has a lot of improvements over the previous version and still no dependencies on other packages.
Now the package for Laravel 4. It has a lot of improvements over the previous version and still no dependencies on other packages.
One column per quarter.