Check release date on CI

[tyranron]

I often catch myself that I forgot to update the release date in CHANGELOG once preparing a new release. So, I've added such check to CI in the projects I maintain. Would be useful here too, I guess.

[tyranron]

ping @JelteF

[JelteF]

Afaict this will fail the github release creation if the date in the changelog is not today? I like that something checks for that, but when it checks seems like it's a bit too late. By then the tag has already been pushed and packages published.

[tyranron]

@JelteF yes, it checks when the Git tag is pushed, so if the date is incorrect, the GitHub release won't be created, and the tag could be re-applied to the next commit fixing it.

Regarding publishing to crates.io, it's usually done via CI in my projects. But as far as I recall, you were hesitant to that, to avoid leaking potential access to other your crates from this GitHub repo. Since then, crates.io added functionality for granular token access. It could be configured like this to not allow anything more:

If you're not hesitant to this idea anymore, I can also add publishing via CI again, and do the changelog check before anything is published. Git tag, however, is the only thing to be reapplied if CI fails.

[tyranron]

@JelteF thoughts?

[tyranron]

@JelteF ping

[tyranron]

@JelteF we even can go now with the trusted publishing if you'd like, so there would be no need to generate a token.