Weave Code
Nova Laravel Update Card Laravel Package
beyondcode/nova-laravel-update-card
A Laravel Nova card that displays your app's installed Laravel version alongside the latest release, flagging available framework updates at a glance so you can keep dependencies current and plan upgrades right from your Nova dashboard.
A Laravel Nova card that shows you if you're running the latest Version of Laravel.
Frequently asked questions about Nova Laravel Update Card
- What does beyondcode/nova-laravel-update-card do?
- It is a Laravel Nova dashboard card that compares the laravel/framework version installed in your app with the latest stable release on Packagist. It displays both versions and flags when an update is available. The card is informational only and does not perform upgrades.
- Is this package still maintained and safe for production?
- No. The repository is archived, the only release is 0.0.1 marked experimental, and the last release was August 2018. Archival means the maintainer will not ship fixes, compatibility updates, or security responses. Treat it as a reference implementation rather than a dependency for a shared or production dashboard.
- Do I need Laravel Nova to use this card?
- Yes. It is a Nova card and has no architectural home outside Laravel Nova, which is a paid, closed-source product. If your team does not run Nova, the evaluation ends there. In that case, reproduce the capability with composer outdated in CI, a scheduled Composer job posting to chat, or an internal status endpoint.
- Which Laravel and Nova versions does it support?
- The package was authored in the Nova 1.x era of 2018 and its Composer constraints were resolved against 2018 PHP and illuminate/* ranges. There is no documented support for current Laravel or Nova majors, and the card API may need rewriting. Test rendering in a disposable Nova environment before considering anything else.
- How does the card get the latest Laravel version?
- It queries Packagist for the latest stable laravel/framework release and compares it with your installed version. The outbound call's timeout, cache TTL, rate-limit handling, and failure behaviour are undocumented. That request also needs a security and privacy sign-off before use.
- Can I get the same functionality without Laravel Nova?
- Yes. The capability is framework-currency visibility, which fits naturally in CI or tooling you already operate. Use composer outdated, a scheduled Composer check that posts to chat, or a small internal status endpoint. These avoid owning an abandoned, unmaintained dependency.
- How do I install nova-laravel-update-card?
- Install it via Composer and register the card in your Nova service provider, then publish assets through Nova's tooling. Because the package targets the 2018 Nova 1.x card contract, installation into a current lockfile may conflict or force unrelated downgrades. Scope installation to a disposable Nova environment first.
- What happens if Packagist is unreachable or rate-limits the request?
- The behaviour is not documented, so it may show stale data, an error, or a misleading up-to-date state. The 2018-era client may also misparse modern release metadata. If the endpoint is offline or rate-limited, do not rely on the card's output.
- Does it notify me or block deployments when an update is available?
- No. It is a read-only widget that only displays version information on the Nova dashboard. It does not gate deploys, enforce policy, notify anyone, or track dependency drift beyond the framework itself. Use CI checks or monitoring for enforcement and alerting.
- Is there a better alternative for tracking Laravel updates?
- Yes, for most teams an internal implementation or existing tooling is cheaper. composer outdated, a CI step, or a scheduled job covers the same need without an archived dependency. Because the repo is archived, there is no upstream fix if the card breaks, so plan a fallback such as removing it or replacing it with your own card.
Weaver
How can I help you explore Laravel packages today?