Hi @chrisblankde, Can you please tell me what metadata you are trying to update? If it is just the version, you can use the Repackage API. If it is something other than the version, in ProGet 2023, we added the ability to edit the upack metadata directly in ProGet. You can do that by navigating to the package version in your universal package feed and then click "Edit Package" in the upper right corner. If neither of those options works for you, then what you suggested (download/extract/edit/repack/upload) would be the way to handle this. Thanks, Dan

Thanks, yeah, that seems to work. I changed my pipeline code to not send any title metadata to ProGet, which returned that field in the UI to its original behavior. I also found that rebuilding an existing package, and sent to ProGet with the updated pipeline, has the same effect.

Currently assets do not have any user-definable metadata like this, I guess because that would make them a lot like packages? Assets also aren't intended to be like a "SharePoint replacement", which is why we don't want to put a lot of extra features like versioning, etc. These are also hard to replicate, etc. That being said, we are open to changes, so please consider using the Feature Request Process. Note that, we also want to evaluate "why" and "how this would be used", and that's part of the feature/change process.

You can do this... GET /upack/«feed-name»/search?query=«search-query»&count=«max-items» This is the same API that the ProGet Web Application uses to show results to users, and returns a list of packages similar to the packages endpoint.