- What is fico7489/laravel-revisionable-upgrade?
- It is a Laravel Composer package that augments the venturecraft/revisionable package with a set of extra helper methods for working with revision history on Eloquent models. It lets you track changes, store model snapshots, view diffs, and restore previous versions. It is not a standalone audit platform; it is a thin layer on top of an existing revisionable setup.
- How do I install fico7489/laravel-revisionable-upgrade?
- Install it with Composer alongside venturecraft/revisionable, then add the relevant trait to the Eloquent models you want to version. Because the package is old, pin the exact version in composer.lock and confirm any service provider or migration publishing steps against your Laravel version. Run a full Composer dependency and security audit before merging.
- Which Laravel and PHP versions does this package support?
- The last release was in 2020, so treat that as a compatibility warning rather than a guarantee. Validate it against your target matrix, especially Laravel 9, 10, and 11 with PHP 8.1 and above, and check the transitive constraints coming from venturecraft/revisionable. A short time-boxed spike in a branch is the fastest way to confirm real compatibility.
- Does it work without venturecraft/revisionable installed?
- No. The package is an augmentation of venturecraft/revisionable, so the upstream revisionable package must already be present and working in your application. If you are not using venturecraft/revisionable today, this package is not the right starting point. Look at a maintained audit package or a small in-house audit table instead.
- Is fico7489/laravel-revisionable-upgrade still maintained?
- Upstream activity is low, the last release dates to 2020, and the package has a small community footprint of roughly 53 GitHub stars. That means few public answers and limited maintainer responsiveness. If you adopt it, assign an internal owner, keep versions pinned, and budget for eventually forking or replacing it.
- Should I use this package for a new Laravel project?
- It is generally not recommended for greenfield work. The package only makes sense when your application already depends on venturecraft/revisionable and specifically needs the extra helper methods it provides. For new platforms, prefer a maintained auditing or revision package, or implement a compact in-house audit table you fully control.
- How do I restore a model to a previous revision?
- The package exposes helper methods for retrieving revisions and restoring earlier snapshots of a model. Before relying on this in production, confirm the rollback semantics against your own schema, since restoring overwrites current attribute values. Add regression tests that create, retrieve, and roll back revisions so behavior is locked in.
- What are the alternatives to laravel-revisionable-upgrade?
- Teams commonly choose a currently maintained audit or versioning package, or build a small audit table with a trait and model observer. The in-house route is often cheaper when you only need a handful of helper methods that this package adds. Either option avoids inheriting risk from a stale upstream dependency chain.
- How should I test revisions and rollbacks before going to production?
- Pilot the package on one low-risk model in staging with representative production-like data. Verify migrations, schema changes, revision creation, retrieval, diff output, rollback behavior, and any retention or pruning logic. Then run automated regression tests and a monitored production canary before expanding to more models.
- What are the scaling and storage concerns with revision history tables?
- Revision tables grow with every write, which means steady storage growth, index pressure, and possible write amplification on high-traffic models. Plan retention rules, archival, and pruning up front, and add indexes suited to how you query history. For very high-write models, consider asynchronous revision writes or a different audit design entirely.