Could we be talking about the ‘StrumNotes’ or ‘Custom Wave Synth’ tools? Those two actually had a problem which causes the upgrade to pick them up on every Renoise session.
Technically, they were both simply auto-upgraded to the latest version and tested before packing and releasing. But they got released with a “AutoUpgrade” value set in the manifest, which caused the upgrade tool to pick them up every time.
Without this post, it could have gone unnoticed - now it’s fixed. Thanks!
Well, I did not put that in there, so apparently Renoise did that automatically at some point. Maybe that issue can be fixed in the future. If I have time in the following weeks, I might(!) upload a new version without this mysterious property, but it really would be good if this is fixed on the Renoise side.
No mystery there - the property is added when the tool was automatically converted by Renoise.
Otherwise, there would be no way of telling an auto-upgrade tool apart from the “official” version by the tool author when they otherwise have the same version number.
The proper way to deal with this is simply that tools.renoise.com should reject upgraded tools or offer to strip it away automatically.
Or just don’t automatically update if there is no newer version. Irrespective of this attribute, the version number matches the one it wants to update to. So, don’t update!