GHA: switch to autogenerated release notes

[martinfleis]

No description provided.

[martinfleis]

@jGaboardi this sounds like a James task. Could you have a look into that? You were setting it up elsewhere. We should also remove the rendered changelog from the docs and link to release notes on GH instead.

[jGaboardi]

@martinfleis I will try to give this some attention over the weekend.

[jGaboardi]

Once I get started on this, until I get it right will we want to:

• iterate over v0.7.0.post{1...N}
• iterate over v0.8.0rc{1...N}
• something else?

[martinfleis]

I'd go with 0.8.0-alpha{1...N} as it reflects the best the nature of those releases as per semver. We're not at RC stage yet.

[jGaboardi]

Steps

1. open pr with new infrastructure - gha for release notes - #543 #604
2. decide on labels/tags for release.yml, etc. - gha for release notes - #543 #604
3. remove changelog from docs - gha for release notes - #543 #604
4. remove CHANGELOG.md - gha for release notes - #543 #604
5. merge once agreed
6. iterate tag+release over v0.8.0-alpha{1...N} until satisfied
7. prepare for actual v0.8.0
   1. add updated labels to Issues & PRs
   2. other?
8. later cut v0.8.0

[martinfleis]

• remove changelog from docs

[jGaboardi]

beginning alpha release attempts

• v0.8.0-alpha1 ❌ - see Update release.yml - troubleshoot release action failure #607
• v0.8.0-alpha2 ✅ - https://github.com/pysal/momepy/releases/tag/v0.8.0-alpha2
• v0.8.0-alpha3? (determine if commits are truncated to only the absolute most previous release)

[martinfleis]

I have updated tags in the relevant PRs since 0.7.0

[jGaboardi]

So we're all good to close this? Are we sure we don't want one final test release to make sure those new tags are picked up properly and looking nice? Probably not necessary, more a peace-of-mind thing.

[martinfleis]

So we're all good to close this?

I guess so?

Are we sure we don't want one final test release to make sure those new tags are picked up properly and looking nice?

let's YOLO it 😎