A simple text field for version control requires manual input, which leaves room for incomplete entries and adds extra effort.
An automated suggestion would pre-fill release notes based on actual changes, reducing the risk of missing or low-quality input and making it easier to trace issues in deployment history. With a small set of predefined settings, versioning rules and numbering could be applied consistently.
Even as a small feature, this could be very useful to rollback or distinguish between minor commits and larger changes (such as migrations), based on all changes since the previous deploy.
I would expect this to look something like this, but I assume the SEs will come up with something better:
- Automatic draft generation: pre-filled release notes based on all changes since last deploy
- Editable suggestion: users can adjust before finalizing, but never start from empty
- Version numbering rules: configurable (e.g. incremental / semantic / date-based)
- Traceability: direct link between version notes and actual implemented changes
