Release notes 8.13.0
Hi there!
Could you please publish release notes for 8.13.0?
The diff looks pretty big: https://github.com/brianc/node-postgres/compare/pg%408.12.0...pg%408.13.0
Thanks a lot
Can we please have release notes? We can't upgrade without knowing what's changed.
Bump on this!
@brianc
https://github.com/brianc/node-postgres/blob/master/CHANGELOG.md#pg8130
Sorry but the PR linked in the changelog changes just 2 lines of code and add 1 test, while the comparison between v8.12 and v8.13 are 807 additions and 1,558 deletions.
A better detail on the changelog would be appreciated.
Also v8.13.1 is missing.
I recommend you to use semantic-release or similar in the future so you can automate and improve the process of the releases and changelog. There are at least 4 different (but closed) issues about changelog, so it's a problem that developers are now feeling. Since pg is a core library in any project, we can't upgrade without knowing the changes and the reason of the changes, as @markedwards said.
cc @MyNameIsNeXTSTEP Could you please help?
@kirrg001 I'd like to Give me a little guiadence what to do exactly please
The git diff https://github.com/brianc/node-postgres/compare/[email protected]@8.13.0 looks very big. It contains 28 commits, 807 additions and 1,558 deletions.
The community was wondering why the public changelog only contains one change:
Add ability to specify query timeout on https://github.com/brianc/node-postgres/pull/3074.
Could you please double check and confirm that this is the only customer facing change?
Thanks a lot!
@kirrg001 If i understood you correctly, here what i've done so far.
As I explored the comparing changes I have found these customer facing changes (which customers may face using the lib) not inluded in the current changelog description for v8.13.0:
Could you please update your CHANGELOG?
Furthermore, it would be really helpful for the community if you could start using GH releases as well.
Thank you!
@brianc FYI
Fwiw, I am happy with current release practices and grateful for all the hard work and contributions over the years. Thank you!
Straight forward enough to use git to see what files changed between releases.
Just use the github releases please @brianc , it's extremely simple:
- people make changes, merge some PRs
- go to releases, click New release, click "Generate release notes"
- click publish and all the changes will be very clear for everyone
In this way you save time on creating tags, updating changelog, etc