KnpLabs / KnpLabs/phpstan-rules
Version number validation and changelog generation
Open
- Dominant language
- PHP
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
### The idea
It could be nice to have a version number validation regarding the semantic versioning. Maybe add a agentic check to validate if the release is actually a breaking change (major) ; new feature (minor) ; or a fix (patch) and so on...
**The solution has to be designed**
Contributor guide
Research direction
The issue names no files, tests, or entry points. Start by scoping the required semantic-version validation, release classification, and changelog generation behavior with the maintainers. Done requires an agreed design and clear validation and changelog outcomes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100