Blt Laravel Package

Product Decisions This Supports

• Laravel upgrade planning: v1.1.0 adds Laravel 13 support, so this dependency is no longer a blocker for planning the next major Laravel upgrade. Put it in the Laravel 13 migration workstream rather than treating it as a separate project.
• Build vs. buy / dependency strategy: a small, maintained Laravel package with forward framework compatibility is a reasonable substitute for internal glue code. Reassess only if internal maintenance cost drops below the cost of adopting and tracking this dependency.
• Supply-chain and security review: SHA-pinned GitHub Actions and explicit minimum permissions improve the package’s CI posture. This is useful evidence for a security review, but it is pipeline hygiene, not a runtime security guarantee.
• Release risk: this is a minor release with no breaking changes called out. It can go into routine dependency updates; no feature freeze or migration budget is triggered.

When to Consider This Package

• You are on Laravel and want dependencies that track upcoming major versions rather than pinning you to older releases.
• You value visible maintenance hygiene — pinned CI actions, least-privilege workflows — as a signal of project health.
• You are standardizing on Blumilk tooling or a Laravel template and want aligned version support.
• Look elsewhere if you need a broad, documented feature set: these release notes contain no feature detail, so validate actual capabilities against your use case before committing.
• Look elsewhere if your organization requires long-term support guarantees from a large maintainer, or if depending on Copilot-assisted CI changes without deeper code review is a policy concern.

How to Pitch It (Stakeholders)

Executive summary: v1.1.0 is a low-risk maintenance release. The material change is Laravel 13 compatibility, which reduces future upgrade risk. The CI hardening is good engineering hygiene, not a product change. No breaking changes are indicated, so no budget or migration project is triggered now.

Engineering summary: minor-version bump with explicit Laravel 13 support and SHA-pinned GitHub Actions using least-privilege permissions. Include it in the next routine dependency update and run it through the existing test suite, since the release notes are sparse. If this package is on a critical path, attach a compatibility check to the Laravel 13 upgrade epic rather than creating a standalone work item.