All notable changes to aichadigital/lara-content will be documented in this file.
lara-content adopts UUID v7 char(36) as the only supported type for FK columns
referencing the consumer app's users.id. bigint and ULID are out of scope.
See ADR-001 (this package) and
larabill ADR-006
for the canonical rationale, and STD-001 in the AichaDigital umbrella standards.
content.user_id_typeconfig key andCONTENT_USER_ID_TYPEENV var. The package no longer reads them.- Legacy agnostic helpers in
Support\MigrationHelper:getUserIdType(),detectUserIdType(),getIdTypeDescription(),isSupportedIdType(),agnosticIdColumn(). OnlyuserIdColumn()remains, simplified to emit UUID char(36) unconditionally.
content_posts.author_idis now alwayschar(36)UUID. The column was already emitted viaMigrationHelper::userIdColumn(...); with the helper simplified, it is UUID-only.Models\Post::$author_idPHPDoc updated fromint|string|nulltostring|nullto reflect the UUID-only contract.tests/TestCase.phpno longer setscontent.user_id_type(key removed).
tests/Integration/Mysql/MysqlIntegrationTestCase.phpandtests/Integration/Mysql/FreshInstallTest.php— verify the UUID-first contract against MySQL 8 with a fresh schema. Driven byLARACONTENT_TEST_MYSQL_*env vars (with fallback toLARABILL_TEST_MYSQL_*for umbrella-local convenience).- CI job
mysql-integrationrunning the new suite against a MySQL 8 service. docs/ADR-001-uuid-first.md— local ADR materializing STD-001 for this package.- README requirement section pointing at the shared
larabill/docs/setup-uuid.mdsetup guide.
- Apps already on UUID
users.id: no action required, the package keeps working. - Apps on bigint or ULID
users.id: not supported. Migrateusersto UUID v7 before installing — see the shared setup guide. Migrating an existing app's primary key is non-trivial and is out oflara-content's scope.
Initial alpha release.