-
-
Notifications
You must be signed in to change notification settings - Fork 49
Description
Suggestion
Problem statement
Right now we need a lot of manual actions in order to bump the version:
-
Update pubspec semantic version and build version
-
Update and review the CHANGELOG manually, because it's the source of truth of what has updated in the version. Automatic GitHub release notes are raw and too noisy. Maybe we could force the PR authors to always update CHANGELOG, so we don't lose the actual valuable stuff. But even so like that, that still could be too noisy for a regular user, that wants to know that's changed between the versions, so this would require a final validation from a release manager.
-
PR and merge
Solution
I suppose we could automate it with some kind workflow with AI.
It would go like so:
- User asks to update 1 of 3 numbers in semver. The wokrflow updates it and automatically increments the build number. This step could, or could not involve AI, depends on whether we want AI help to decide, which version to bump or not.
- AI generates a CHANGLOG entry based on the sctructure we put into its prompt and asks the user, if that's OK, or they want to edit it
- After approval, workflow makes a new commit into master
Additional:
As a final step, we need to put the link to human-readable CHANGELOG into the release decscription, so it goes before the automatically generated one
Metadata
Metadata
Assignees
Labels
Projects
Status