Nova Markdown Tui Laravel Package

Product Decisions This Supports

• Dependency hygiene / upgrade readiness: v1.3.2 is a patch-level fix for an implicitly nullable parameter ($resolveCallback) — a PHP 8.4 deprecation. This unblocks teams planning a PHP runtime upgrade, which is a scheduling decision, not a feature decision.
• Build vs. buy signal: The package exposes a resolver-callback extension point, meaning it is designed to be configured rather than forked. That favors "buy/install + configure" over in-house implementation for the narrow problem it solves.
• Roadmap impact: none. No new capabilities, no API surface change. Do not re-plan features around this release.
• Use cases: Wherever the product relies on the callback-driven resolution path (custom resolution logic supplied by the app), this release keeps that path deprecation-clean on modern PHP.
• Risk triage input: Treat as a routine bump for a maintenance window. No migration work, no user-facing behavior change expected.

When to Consider This Package

Adopt when:

• You are on (or moving to) PHP 8.4 and currently see implicit-nullable deprecation notices traced to this package's resolver callback.
• Your codebase passes a resolver callable into the package and you want a maintained upstream rather than a locally patched fork.
• You want a small, single-purpose dependency whose extension point is a callback — i.e., you value configurability over forking.

Look elsewhere or defer when:

• Maintenance appears stalled after this point. A patch that only silences a deprecation is a hygiene signal; it is not evidence of active feature investment. If you need new capability, evaluate alternatives.
• You are pinned below PHP 8.4 and have no deprecation noise — this release is optional; apply it on your normal cadence rather than urgently.
• You require a stable, versioned extension contract. A single patch release is not enough evidence to judge long-term API stability of the $resolveCallback signature; confirm the semantic-versioning policy before building hard against it.
• You need guarantees this assessment cannot make. No changelog history, benchmark, or security posture data was available here; run your own review before adopting in a regulated or high-blast-radius path.

How to Pitch It (Stakeholders)

To executives: This is a maintenance release, not a product change. A third-party PHP package we depend on shipped a small compatibility fix so it works cleanly on the newest PHP runtime. It costs us nothing to adopt, removes a class of deprecation noise, and de-risks our eventual PHP upgrade. No customer-visible impact, no budget ask.

To engineering: v1.3.2 is a one-line patch correcting an implicitly nullable $resolveCallback parameter — a PHP 8.4 deprecation. No breaking changes, no new features, no migration steps. Bump it in the normal dependency cadence; verify your resolver callbacks still type-check and that deprecation warnings from this package clear. Because the only signal we have is deprecation hygiene, treat the package as maintained but low-velocity — avoid deep coupling to the resolver API without confirming its versioning guarantees, and keep an eye on whether future releases add capability or only silence warnings.