After making a minor fix to my app on Splunkbase, can I update the app binary release but keep the same version number?

[wnguyen]

I uploaded an app onto Splunkbase but made a minor revision/bug fix that doesn't warrant a new version label. Can I update the app release while keeping the same version number?

[mglauser_splunk · Accepted solution]

The app needs to have at least one version available as a default. What you can do is:
1. Upload a dummy release with a separate version number
2. Set the dummy as the default (must be visible)
3. Delete the original version
4. Reupload the updated package with the original version name
5. From there, you set the newly uploaded package as default and delete the dummy

[acharlieh]

I do not know that it is possible, but even if there is a way, please don't... Instead just increment the PATCH part of your version number and upload a new one, unpublishing the old one if necessary afterwards.

It is called out in semantic versioning as something you MUST not do, but for the sake of illustration let's assume that we find out that you are able to re-upload a different artifact with the same version number. If someone previously downloaded a version without the fix, how would they know that there's an updated version with a fix? If they report a bug against this version, how do you know if they are reporting against version X with the fix or version X without the fix? This confusion is prevented easily by just incrementing the version for published artifacts.