The version of the CHANGELOG on the website has not been updated since v1.5.2

[wilfwilson]

I noticed this because the new 'release' GitHub Actions workflow (erroneously) removed this file, and then when inspecting the file I noticed that it was way out of date.

Presumably the latest version of the CHANGELOG used to be automatically copied into the gh-pages branch when making a release, but this must have been stopped at some point.

See https://digraphs.github.io/Digraphs/CHANGELOG.html

[wilfwilson]

I've just updated this manually, but I'll try to get a solution so that it gets updated automatically in the future.

The last time that it was updated was also the last release that I made in 2022, shortly after my last academic job ended. James made the releases after that, until I made the v1.10.1 release last week. For those releases up to v1.5.2, I had been using the semirel.py script, whereas I guess @james-d-mitchell then went on to use something else. I'll try and copy whatever semirel.py was doing into the current setup (I guess just copying the CHANGELOG.md file into the gh-pages branch at the appropriate point).

[james-d-mitchell]

Sounds good, I didn't notice this previously, should be easy enough to resolve as you mention.

[wilfwilson]

A generalised version of this functionality will become part of the GAP actions, and then we can use that (I might do be the one to implement it). See gap-actions/update-gh-pages#7 and gap-actions/update-gh-pages#5.

[wilfwilson]

I've implemented it at gap-actions/update-gh-pages#8, and once that PR is merged and the v1 tag updated, then we can merge #807 and this issue will finally be resolved.

[wilfwilson]

As of the v1.12.1 release, this is now taken care of by the "Release" GitHub actions workflow.

In particular, I did not manually make the latest update to the CHANGELOG that's on the website, see https://digraphs.github.io/Digraphs/CHANGELOG.html, which (as of writing) concerns version v1.12.1.