Remove automated commits from release notes

[ds-cbo]

Not sure where else to put this, but could you please keep pre-commit.ci and dependabot commits out of the release notes? They make it very hard to see what actually changed, which makes my life as a dependency update reviewer much harder.

For example, the 8.1.0 release notes contain the following line 12 times, vs 24 real changes (not counting 3 dependabots)

[pre-commit.ci] pre-commit autoupdate by https://github.com/pre-commit-ci in https://github.com/pypa/setuptools_scm/pull/...

If you really want to keep them (though I doubt their usefulness in release notes), could you at least move them to a dedicated "Automated commits" block?

[shenxianpeng]

How about using release-drafter? we used it in cpp-linter org and it works well HERE. It can automatically label PRs, automatically classify them, and guess new versions. Finally, the publisher opens the Draft release and clicks to publish. I can draft a PR for reference If you are interested.

UPDATE: GitHub Releases also support classifying release notes automatically by creating a .github/release.yml file if not prefer to use 3rd tools above.

[RonnyPfannschmidt]

the intent is to migrate towards using towncrier and/or scriv to produce the changelog fragments and using those to fill in the release