Weave Code
Laravel Version Laravel Package
akaunting/laravel-version
Akaunting's Laravel Version package offers a simple, config-driven way to manage and display your Laravel app's version number. Centralize release metadata, expose it via helpers, and keep version info consistent across your application. It's lightweight and easy to integrate.
Version management package for Laravel
Frequently asked questions about Laravel Version
- How do I install akaunting/laravel-version in a Laravel app?
- Install it with Composer using composer require akaunting/laravel-version. The package is a standard Laravel package with auto-discovery, so manual provider registration should not be needed in most applications. After installation, publish and set its config value to your application version. Validate Composer resolution against your Laravel and PHP versions first, because the package dates from the Laravel 5.5 to 8 era.
- Does akaunting/laravel-version support Laravel 9, 10, and 11?
- There is no evidence of official Laravel 9, 10, or 11 support; the last release was in March 2021 and the package targets the Laravel 5.5 to 8 and PHP 7.x era. Do not assume PHP 8.1+ compatibility or modern test coverage. Check the declared Composer constraints and run it in a sandbox on your exact framework and PHP matrix before adopting it. If you need current Laravel support, an in-house helper or generated version file is safer.
- How do I configure the application version with akaunting/laravel-version?
- The package is config-driven: you publish its config file and set the version value there. That gives you one canonical release string for display or comparison instead of scattering version literals through the codebase. Keep the value aligned with your build or release process so it does not drift. If your version is already known at build time, a CI-generated config file can remove the dependency entirely.
- How do I display the app version in Laravel using this package?
- Use the package's facade or helper surface to read the configured version string and render it wherever needed, such as an admin footer or support diagnostics. The public surface is intentionally small: get the version and compare versions. Wrap those calls behind a small internal service if you want to swap implementations later without touching call sites. Avoid calling the package directly from many views if you may replace it.
- Can akaunting/laravel-version compare semantic versions?
- The package exposes version comparison as part of its small public surface, but semantic-version comparison is the main correctness risk in this kind of utility. Prerelease tags, build metadata, and non-conforming version strings are where hand-rolled comparators often break. Test your real version formats before relying on it for update checks or feature gating. For critical comparisons, use a maintained semver library or a tested internal comparator.
- Is akaunting/laravel-version still maintained?
- The last release was 2021-03-05 and adoption is low, so treat it as effectively unmaintained until proven otherwise. It may be flagged as abandoned or stale by dependency scanning, which can fail CI gates in security-reviewed environments. The blast radius is small because the package is trivial and isolated, but the supply-chain risk is disproportionate to the value. If you adopt it, pin a commit or vendor the MIT-licensed code with a documented owner.
- What are good alternatives to akaunting/laravel-version?
- For most apps, config('app.version') or a CI-generated version.php file provides the same behavior with zero third-party risk. You can also bake build metadata into the container image or use a small internal AppVersion service. If you need robust semantic-version comparison, use a maintained semver library rather than a 2021-era convenience wrapper. The package is best treated as a speed option, not a capability enabler.
- Is akaunting/laravel-version safe to use in production?
- It is lightweight and introduces no runtime services, persistence, external calls, or middleware, so its runtime blast radius is low. The production concern is dependency hygiene: an unmaintained 2021 package with 38 stars may conflict with modern Laravel or PHP or fail dependency policy checks. Validate Composer resolution, config caching, and read-only container filesystems on your target stack. If your policy tolerates stale dependencies only for non-critical functions, isolate it behind an internal wrapper.
- How should I test akaunting/laravel-version in my Laravel application?
- Test your integration, not the package internals: assert that the configured version is exposed correctly and that any comparison logic handles your real release formats. Include prerelease, build-metadata, and malformed version strings if you use comparison for update checks or feature gating. Run the tests on your actual Laravel and PHP matrix, because the package has no demonstrated modern coverage. Also test with php artisan config:cache enabled to catch configuration assumptions.
- Does akaunting/laravel-version work with config caching and immutable deployments?
- It is config-driven, so it should work with Laravel's config cache as long as the version value is available at cache time. Confirm whether the package reads or writes a version file at runtime; if it does, verify that behavior on read-only container filesystems. For immutable deployments, generate the version during build and include it in the image or config cache. If the package writes at runtime, prefer a generated file or config value instead.
Weaver
How can I help you explore Laravel packages today?