Weave Code
Versioning Laravel Package
laravel-enso/versioning
Laravel Enso Versioning provides transparent versioning for Eloquent models, automatically recording changes and letting you review or restore previous revisions. It integrates with the Enso ecosystem for permissions and UI-driven version management.
Prevents update conflicts in Laravel
Frequently asked questions about Versioning
- How do I install laravel-enso/versioning in a Laravel app?
- Install it with Composer using composer require laravel-enso/versioning, then verify that its Laravel and PHP constraints match your application. Because the upstream package is archived and has no releases since March 2023, pin the exact commit or fork it before relying on it. Run migrations and exercise versioning on a representative model in a branch first.
- Which Laravel and PHP versions are supported by laravel-enso/versioning?
- The available context does not provide a guaranteed compatibility matrix, and the archived state means future Laravel releases will not be tracked. Treat any stated constraints as a starting point and test against your exact Laravel, PHP, and database versions. Add compatibility tests before upgrading Laravel or PHP.
- Does laravel-enso/versioning require the Laravel Enso ecosystem?
- It is designed to integrate with Enso for permissions and UI-driven version management, so coupling to Enso conventions is a real risk. Confirm whether the versioning traits, middleware, or service providers depend on Enso-specific packages. If you are outside Enso, evaluate a small spike or a native implementation before adopting it.
- How does laravel-enso/versioning prevent update conflicts in Eloquent models?
- It provides transparent versioning for Eloquent models by recording changes and supporting review or restore of previous revisions, which supports an optimistic concurrency approach. The exact conflict-detection mechanism is not clearly guaranteed in the available context, so inspect the code for version columns, timestamps, or middleware. Test concurrent edits to confirm the conflict response contract.
- Can I review and restore previous model revisions with laravel-enso/versioning?
- Yes, the package records model changes and lets you review or restore previous revisions, with Enso integration for permissions and UI-driven management. Make sure restore actions are authorized and audited in your application. Test restores across relations, soft deletes, and transactions.
- Is laravel-enso/versioning still maintained and safe for production?
- It is archived, has low adoption, and has had no releases since March 2023, so it should not be treated as a strategic upstream dependency. Production use requires internal ownership, a pinned fork, security review, and tests. The core optimistic-locking pattern is sound, but this implementation may be stale.
- Does laravel-enso/versioning handle API, queued, and bulk updates?
- The available context does not confirm coverage for API writes, queue workers, bulk operations, or model events. You must test every write path, including mass updates and jobs, because middleware or trait-based checks can be bypassed. Define how conflict exceptions surface to API clients and web users.
- What alternatives exist for optimistic concurrency control in Laravel?
- A common alternative is a native version column or updated_at check with compare-and-swap logic in Eloquent updates, backed by database constraints and clear conflict responses. Maintained auditing or versioning packages can help with revision history, but verify they also enforce concurrency control. For small teams, a focused in-house implementation may be cheaper than forking an archived package.
- How should I fork and maintain laravel-enso/versioning internally?
- Fork the MIT-licensed code under an internal namespace, pin the commit, and update Composer constraints for your Laravel and PHP matrix. Add tests for conflict detection, restore behavior, bulk writes, queues, and transactions before rollout. Assign an owner for security patches, Laravel upgrades, and documentation.
- How does laravel-enso/versioning behave under high write contention?
- The pattern adds write-time conflict checks, which can increase retries or failed writes when many users edit the same records. Measure conflict rates on high-concurrency paths and define retry and user-resolution policies. Avoid silent retries that overwrite user intent or mask stale data.
Weaver
How can I help you explore Laravel packages today?