Sonatype Nexus Repository 3.71.0 & chocolatey

[daemenseth]

Since upgrading to version 3.71.0 and migrating to the new database, we've encountered issues with Chocolatey due to Sonatype’s lack of support for deprecated NuGet v2 API requests.

Questions:

Is there an option in Sonatype to enable support for deprecated API requests to maintain backward compatibility?
Alternatively, is there a recommended approach to handle these legacy requests in Sonatype?
While there is a workaround available from Chocolatey, using choco feature disable --name='usePackageRepositoryOptimizations', it’s not ideal because it requires a client-specific setting.

Thank you for any guidance or recommendations!

[daemenseth]

the problem is the chocolatey upgrade comand has issues on a nuget hosted repository with the index.json specified.
In a nuget group on the nexus there is no issue.
For more information see also this [post}(https://github.com/chocolatey/choco/issues/3506#issuecomment-2474658940)

[mrprescott]

Unfortunately, we aren't planning to rebuild support for deprecated NuGet API endpoints in the foreseeable future, but we are aware there is an issue here. We'll leave this issue open to accumulate demand.

[daemenseth]

@mrprescott can you confirm if there is a known bug with Sonatype Nexus and Chocolatey using v3 nuget repo's.
That is what Chocolatey says in this thread: chocolatey/choco#3506

Is there something we can do together to fix this issue?

[TK5-Tim]

Is there a timeline to resolve this issue?

[mrprescott]

@TK5-Tim We're not planning any changes relating to this issue in the immediate future, but we are monitoring demand.

[daemenseth]

@mrprescott Could you confirm if there are any known issues with Sonatype Nexus and Chocolatey? Is this issue related to Chocolatey due to the use of deprecated features?

Chocolatey mentions there is a known issue on the Nexus side, but it doesn't appear in Sonatype's public issue tracker:
See this link