Releases: mattiverse/Laravel-Userstamps
3.1.1
What's Changed
- feat: support UUID data type columns by @Suh-Edmond in #66
New Contributors
- @Suh-Edmond made their first contribution in #66
Full Changelog: 3.1.0...3.1.1
3.1.0
What's New
This release introduces macros to simplify creating migrations.
Userstamp columns can now be created with:
$table->userstamps();
$table->userstampSoftDeletes();
And dropped with:
$table->dropUserstamps();
$table->dropUserstampSoftDeletes();
What's Changed
- feat: create .gitattributes by @imanghafoori1 in #55
New Contributors
- @imanghafoori1 made their first contribution in #55
Full Changelog: 3.0.0...3.1.0
3.0.0
Breaking Changes
- This release drops support for PHP versions lower than
8.2and Laravel versions lower than9.x. - This release updates the namespace from
Wildside\UserstampstoMattiverse\Userstampsto reflect the ownership change of this project. - Additionally, the
Userstampstrait has moved fromWildside\Userstamps\UserstampstoMattiverse\Userstamps\Traits\Userstamps- note the additional nesting underTraits.
What's Changed
- feat: support custom user resolution by @mattmcdev
- fix: correct null check order by @mattmcdev in #58
Full Changelog: 2.5.0...3.0.0
2.5.0
What's Changed
- feat: support for Laravel 12
- chore: updated tests
Contributors
- @inmanturbo in #54
- @kosarinin in #43
Full Changelog: 2.4.0...2.5.0
2.4.0
2.3.0
2.2.0
2.1.0
2.0.0
This releases contains no new functionality, but has a breaking change for an undocumented behaviour.
The majority of use cases should not be effected by this change, but tagging a major version in case anyone was relying on the behaviour.
Previously, setting any of CREATED_BY, UPDATED_BY and DELETED_BY class constants to null would revert to the default column name. This release changes that behaviour to match Laravel's pattern for the timestamp class constants. A value of null on any of those class constants will now disable maintaining of that column.