Keep A Changelog Laravel Package
phly/keep-a-changelog
Generates and maintains a Keep a Changelog–style CHANGELOG.md for PHP projects. Helps you create standardized release notes, add entries, and manage version sections consistently, making it easier to track changes and publish clear, human-readable changelogs.
Technical Evaluation
Architecture fit: The package is a lightweight PHP CLI tool compatible with Laravel's ecosystem via Composer. It operates independently of framework-specific logic, making it suitable for any PHP project including Laravel. Its non-intrusive design aligns with Laravel's modular architecture, as it doesn't require framework-specific dependencies or service container integration.
Integration feasibility: High. Installation via composer require phly/keep-a-changelog is trivial. CLI commands can be executed manually or scripted into Composer hooks (e.g., post-merge, post-release). CI/CD integration (e.g., GitHub Actions) is straightforward for automated validation during PRs or releases.
Technical risk: Moderate. Existing non-Keep-a-Changelog-compliant CHANGELOG.md files may require manual cleanup before adoption. Risk of versioning conflicts if the project uses non-SemVer conventions (though the tool enforces SemVer). Potential edge cases in parsing complex markdown structures (e.g., nested lists, custom headers) could cause parsing errors.
Key questions:
- How does the tool handle existing CHANGELOG.md entries that don't conform to Keep a Changelog standards? Is there a migration/fix command?
- Does it support custom category names beyond
Added/Changed/Fixed/Removed? (Critical for teams with unique taxonomy needs.) - What is the failure behavior during CI? (e.g., does it fail the build on invalid format
How can I help you explore Laravel packages today?