colmsnowplow
commented
2 years ago Looking good. This needs a 'Prepared for release' commit (it's past tense in this repo for historical consistency, normally it's 'Prepare for release' confusingly).
That commit should:
- Update the changelog
- Update the readme where necessary
- Update the version number everywhere it's referenced (version file, main.go, and readme in this project I believe)
For the changelog, use the date you reckon you'll merge to master - if it happens on a different time you can update it and squash just before merging.
Here's an example of a previous one for this project: https://github.com/snowplow/sql-runner/commit/6f3439fb9b4cacff75fd2eaa9cf67d53422c2207
Coverage decreased (-0.1%) to 21.512% when pulling f4acd3cce66ee8806d5f1ceb9a013b0aa8a98112 on release/0.9.8 into 98fcb9f430684164f4f70b9bddfe5df35f5e96b0 on master.