AssemblyInfo mismatch

[Michael21107]

Despite the first and now-only release being titled as 'v0.1.1', the AssemblyInfo listed version 1.0.0 at that point, and lists it to this day.

[SSStuart]

Good point.
I haven't touched this project in a while, and the code isn't quite up to my standards anymore 😄, but I'll fix that for the next release, soon™️.

[Michael21107]

According to Semantic Versioning, which I strongly suggest you follow, once a versioned software (DLL) is released, all future releases should have a higher version number.

[SSStuart]

Yes, the next release should be 0.1.2
(I 've only increased the revision number for now, as there is no associated release)

[Michael21107]

Following Semantic Versioning, I'm pretty sure that you ''MUST'' increase the number from public releases (their actual code), so since a DLL was released with v1.0.0, any future release should be at least v1.0.1.
However, I would consider adding a space to the AssemblyName (DLL name) so it's ''prettier,'' and then I think you could deprecate any DLLs with the name (AssemblyName) without a space, and start versioning from the beginning again (should begin with v0.1.0 if it's not stable)

[SSStuart]

Oh, okay, I didn't understand it that way.

Since the assembly version of the existing release wasn't defined (using the default value), I'm considering it as ~"0.0.0", I was thinking of just removing the first release and replacing it by a new release.
(if I had already “officially” published this plugin outside of this repo, I would not do that)

[Michael21107]

You created a release with 1.0.0...

[SSStuart]

(I'm not sure why I closed this issue)