Re: Marking packages as deprecated

Hi everyone,

We are trying to implement deprecated packages. For us is important, this is a feature to comunicate to all teams that package is no more "available", will not receive more updates in that version.

For example, we have a nuget package "1.0.0" and we continuous develop and maintain this version for a long term support, we make hotfixs "1.0.x" and new features "1.x.x", at certain point we deliver "2.x" and we will continuous send updates and support version "1.x", but we want some of this packages to be marked as depreacated. With this feature teams will no this version will end in a near term and they need to plan movement for "2.x".

For us is important to have deprecated package feature. Do you have plans for that?

Thank you

This API is from proget, not nuget.org

If I request to proget API findpackagesbyid a package that does not exist, it returns 200, and yes, with no content.

My question is, is it possible proget webapi return 404?

If not, do you know someway in nuget.exe to verify that, if does not existe return some kind of warning?

Our problem is:
Project A > 1.0.0

• dependency to newtonsoft.json 11.0.0

Project A > 1.1.0

• dependency to newtonsoft 13.0.0

Project B

• dependency to A 1.0.0

Whenever we made an update to Project A 1.1.0, if we do not insert in nuget.config feed of nuget.org, the answer is: No packages to update

We expect: Warning: dependency constraint xpto

Hello,
When I made an request to a non-exist package, it returns 200 instead 404

GET http://XXX/nuget/YYY/FindPackagesById()?id='Newtonsoft.Json'&semVerLevel=2.0.0
OK http://XXX/nuget/YYY/FindPackagesById()?id='Newtonsoft.Json'&semVerLevel=2.0.0

This package does no exist in feed YYY

How can have a 404 when a package does not exist?

Thank you