If they’re not telling you in the patch notes it’s probably because there is so much code churn that to retroactively document every fixed bug would amount to too much work.
That being said: if you have good git commit messages and pr bodies this process is very much automatic (at least ton GitHub) releases can have a bunch of notes from the merged prs automatically such as “PR #3964 Fixed thing at place when condition”.
Also sometimes if I don’t want to admit just how badly I screwed up, I put “#Fix 824 : fixed various issues” as opposed to “#Fix824 : fix to repair the fact I put the wrong select statement in the query in the last upgrade” because who wants to have THAT in the notes?
If they’re not telling you in the patch notes it’s probably because there is so much code churn that to retroactively document every fixed bug would amount to too much work.
That being said: if you have good git commit messages and pr bodies this process is very much automatic (at least ton GitHub) releases can have a bunch of notes from the merged prs automatically such as “PR #3964 Fixed thing at place when condition”.
Also sometimes if I don’t want to admit just how badly I screwed up, I put “#Fix 824 : fixed various issues” as opposed to “#Fix824 : fix to repair the fact I put the wrong select statement in the query in the last upgrade” because who wants to have THAT in the notes?