aha, I did that by automatic reflex - I should have started a discussion to see what process you guys have.

The process I usually follow is:
- fix version 'A.B.C-dev' in the pubspec and CHANGELOG as the first submit of any dev cycle, where C is one higher than the previous release version.
- work, listing major changes to the CHANGELOG as I submit them
- make a release by removing the '-dev' from version in pubspec and CHANGELOG, and applying a tag 'vA.B.C' to that commit. At this point I might also change the A.B.C to A.C.0 or B.0.0 if it ends up being a larger version step.
- pub lish that commit
- repeat from step 1

Some of that can / should be automated by a release script probably, but I still haven't made one :)  I like that the version '0.2.0' will correspond to a single commit and tag of the repo.

That is just my process though, and I'm happy to follow any other process here.