I guess it's normal as it's not automated yet, but winget is still on 1.0.0-rc2 where it should be v1.0.0

Thanks :)

I guess it's normal as it's not automated yet, but winget is still on 1.0.0-rc2 where it should be v1.0.0

Hmm... The PR has been merged on the release date. But winget still shows the old version...

microsoft/winget-pkgs#195980

Hmm x2, 1.0.0 has actually been successfully published.

According to the docs, 1.0.0 should be bigger than 1.0.0-rc2, but it is not. It seems that part 0 is not bigger than 0-rc2...

See comparisons Table
The -rc causes Version B to have a string in the second Part where Version A does not
https://github.com/microsoft/winget-pkgs/blob/master/doc/Authoring.md#examples-of-version-comparisons

See comparisons Table
The -rc causes Version B to have a string in the second Part where Version A does not

See "Comparison Result" in the table. It says Version A which means 1.2 > 1.2-rc

Version A	Version B	Comparison Result	Explanation
1.2	1.2-rc	Version A	The -rc causes Version B to have a string in the second Part where Version

Could try with a dot (after the word rc) next time. I remember a similar thing from the past i think version compare in php does it similarly, this is why we use v20.1.0-rc.3 and so on in talk.
Otherwise we just never publish rcs there again