[Bug]: Rider plugin 10.0.0 is actually a previous version?

[martindisch]

Description

I've updated my Rider plugin to 10.0.0, which according to the source should be a no-op (version change only).

But I noticed that the settings have regressed to the previous state before you implemented the global run on save.

Is it possible that an older executable has been uploaded?

Steps to Reproduce

Update Rider plugin

Expected Behavior

Provides global run on save option

Actual Behavior

Only general (solution-specific) settings available, like we had in the past

[belav]

Ugh sorry - I think what happened is I published 10.0.0 from my local main branch which was out of date and didn't contain the global save option. I hid 10.0.0 and published a new 10.0.1 but it won'[t be available until jetbrains approves it.

If you go back to 2.3.0 you'll get the global save option. 10 didn't have any new features. I was just getting the version to be significantly different than the csharpier version to try to avoid confusion from users reporting bugs and not realizing the plugins are independant of csharpier itself.

[martindisch]

Thanks for looking into it :)

[martindisch]

10.0.1 seems available now and the issue is resolved.

[martindisch]

I think this may have happened again somehow. I'm on version 10.0.4 and the setting is no longer there. I'm also a bit confused about what has happened to the Git history. According to GitHub, you merged #1798 originally adding the feature on January 1st

But now the commit is conspicuously missing from the current main branch on GitHub.

[belav]

I had a number of things in main that I didn't want released, and created 1.3.0-dev. I don't recall exactly how I went about that, but it seems there are a few commits there that should be in main. I'll get a new rider plugin version submitted shortly. Sorry for messing this up a second time!

[martindisch]

10.0.5 seems to work again, thanks for the quick fix :)