chore: order of releases in changelog

[2color]

chore: order of releases in changelog #492

[SgtPooki]

these are autogenerated. I wonder if something is misconfigured in semantic-release or there's a bug?

[achingbrain]

We've been through a couple of different release tools which format things differently, and code has been moved around without trimming the release logs, it's a bit of a mess.

[SgtPooki]

we should probably try to re-generate the changelog completely using semantic-release.

[achingbrain]

Notably I think some of the @helia/xxx code has been through at least semantic-release, semantic-release-monorepo, @anolilab/multi-semantic-release and now finally release-please 😅 .

[SgtPooki]

@achingbrain if we remove the changelogs in #483 can we get release-please to regenerate the full changelog?

[achingbrain]

I don't know tbh, but my guess would be no. I think it only considers changes since the last release tag, otherwise we'd see CI releases failing all over the place due to GitHub applying rate limiting (this happens when you stuff up the release-please config, for example).

[achingbrain]

Ok, I've updated the formatting of all changelogs to be consistent with the latest release tool.

I've also re-tagged all the old releases from the @helia/foo-vNNN format to foo-vNNN and removed the old tags so everything's consistent.

Please delete your local tags in any cloned copy of helia you have and fetch the updated list (this will prevent you re-creating the old tag formats if you accidentally run git push --tags, for example):

$ git tag -l | xargs git tag -d
$ git fetch

Hopefully going forwards everything autogenerated will be done just so.