Add Check version job to release workflow

[szepeviktor]

@BrianHenryIE It is too late because the release is already published, but ...

[BrianHenryIE]

I really like this but I don't think it solves the issue completely/in the ideal way. What will happen with this is I will create a release and click publish, then this will give the benefit of a "workflow failed" email for me to act on. I wonder could we expand on this to delete the existing release, capture the content, create the change and then create a new release?! (I'm ad-libbing here). Would that have any impact on Packagist? I.e. I think this repo has a webhook that pushes the release to Packagist, would pushing a new release with the same version number be a problem?

Thanks, as always, for your contributions.

[szepeviktor]

The above forth-and-back "solution" is also error prone.
Moving a git tag causes caching issues on Packagist.
Currently everything begins with the manual creation of a tag+release.

All I can think of is a manual workflow that checks everything and creates a release.

This is well-known, frequently seen problem!