Artifactory: Why does the deployment of NuGet Pre-release versions allow overwriting without Delete/Overwrite permissions

Artifactory: Why does the deployment of NuGet Pre-release versions allow overwriting without Delete/Overwrite permissions

AuthorFullName__c
Gabriel Noghryan
articleNumber
000006062
ft:sourceType
Salesforce
FirstPublishedDate
2024-03-25T12:55:37Z
lastModifiedDate
2024-03-25
VersionNumber
3

Artifactory: Why does the deployment of NuGet Pre-release versions allow overwriting without Delete/Overwrite permissions?

When attempting to push a NuGet package to an Artifactory Local NuGet repository using the 'api/nuget' path, users may encounter 403 responses when trying to overwrite an existing package with a simple versioning scheme (e.g., 1.0.0). This response is expected, as it indicates a lack of Delete/Overwrite permissions.

But here's where it gets interesting: if your package version contains a dash followed by some text (like '1.0.0-pre' or '1.0.0-test'), the upload goes through smoothly, even if there's already a package with the same name. This means the package pre-release version with the dash can overwrite the existing one without any extra permissions.