Laravel Nova News Laravel Package

Product Decisions This Supports

• Upgrade sequencing and platform roadmap: 1.1.0 raises the runtime floor to PHP ^8.2. This is the only decision-relevant content in the release. It forces a cross-team conversation: anyone still running PHP 8.1 must either upgrade their runtime before taking this version, or pin to 1.0.5. Treat it as a breaking change in practice despite the minor version bump.
• Infrastructure / hosting budget: If any environment (shared staging, legacy client deployment, container base image) is on 8.1, this release is the trigger to schedule that platform work or accept staying on the pinned version. There is no middle path — you cannot consume 1.1.0 on 8.1.
• Build vs. buy for editorial/news content in the admin panel: The package remains a thin Nova module for publishing news items inside an existing Laravel Nova admin. It does not justify building an in-house equivalent unless Nova itself is already being reconsidered; the surface area is small and the maintenance signal (regular dependency PRs, test suite modernised to Pest 2 / PHPUnit 10) is positive.
• Roadmap impact: none. No new features, no deprecated APIs, no configuration or migration changes. 1.1.0 should not appear on a product roadmap — it belongs in a maintenance/tech-debt lane.
• Dependency hygiene as a leading indicator: Moving to Pest 2, PHPUnit 10, Orchestra Testbench 8.12 and Pint 1.13 signals an actively maintained test suite. That lowers the risk of adopting this package long-term and reduces the chance of a forced migration later when the test stack goes EOL. Use it as a positive data point when scoring vendor/supplier health.
• Support matrix documentation: If you ship this package to multiple client projects, 1.1.0 is a good moment to formalise a support matrix (package version → PHP version → Laravel/Nova version) so account teams stop asking engineering ad hoc.

When to Consider This Package

Adopt when:

• You are already running Laravel Nova and need lightweight news/announcement publishing in the admin panel — no custom front end, no CMS migration required.
• Your fleet is on PHP 8.2+ (or you have a funded upgrade path), so the new floor is a non-event.
• You want a small, low-ceremony module rather than a full CMS; the scope of this package is intentionally narrow.
• You value a maintained test stack — the dev dependency refresh is a credible signal the maintainer is keeping the suite current.

Look elsewhere when:

• You are pinned to PHP 8.1 or below for contractual, hosting or legacy-reason constraints. Staying on 1.0.5 is viable short term, but you inherit a package whose next maintenance releases will drift further from your runtime.
• You do not use Laravel Nova. Nova is a paid, licensed product; this package is worthless without it, and the licence cost — not the package — is the real budget line.
• You need a full editorial workflow: scheduling, revisions, multi-channel publishing, taxonomy, media libraries. This package does not attempt that.
• Bus factor matters. This is a small-team, low-cadence package; if news publishing is business-critical, weigh that against a supported commercial CMS.
• You need a versioned LTS/support commitment. There is no evidence of one.

How to Pitch It (Stakeholders)

For executives: Release 1.1.0 of our Laravel Nova news module is a maintenance release — no new capability, and no cost. The one decision it creates is a platform requirement: it now requires PHP 8.2 instead of 8.1. That is a routine infrastructure upgrade, not a feature investment. Approving the PHP 8.2 migration unlocks this and future updates for free; declining it means we pin an older version and accept that we stop receiving maintenance fixes. Recommend: approve the PHP 8.2 upgrade on the normal infra cadence, adopt 1.1.0 once environments are confirmed, and keep this package off the product roadmap.

For engineering: 1.1.0 is dependency-only. PHP ^8.1 → ^8.2; dev dependencies moved to Orchestra Testbench 8.12, PHPUnit 10.3, Pest 2.19, Pest Faker 2.0, Pint 1.13. No application code, config, or migration changes. Practical impact: minor version bump but functionally breaking for PHP 8.1 consumers — verify CI images and deploy targets before merging. Expect a small amount of test-suite churn if we carry our own tests around this package (PHPUnit 9 → 10 deprecations, Pest 1 → 2 API changes). No action required on the Nova or Laravel versions we run.