Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.
If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!
Add custom tags to nuget packages
-
Is there a way to add custom tags to nuget packages on the feed?
I only see features such as package promotion and re packaging, but nothing that would let you add a custom tag to a package.I know I can add a tag to a powershell module psd1 and then upload, but I am looking for a way to do this on the fly in ProGet
Thanks
-
Hi @forbzie22_0253 ,
Tags are a field in the
nuspec
file, which is embedded within the NuGet package:
https://learn.microsoft.com/en-us/nuget/reference/nuspec#tagsAs such, we do not recommend using tags in NuGet, because they are "permanent" and you can't "untag" packages. It makes it hard to think of a tagging system that will be useful for the long-term: https://blog.inedo.com/nuget/best-practices-internal-nuget-packages/
-- Dean
-
Hi,
In other repository management systems there is the ability to create custom tags and assign these to packages on the repository, I think this is something that would be very useful since it allows you to mark a particular package with some custom tag, without having to repackage the package and republish to the feed.
Just to clarify, when I say tag, I mean tagging the package metadata on the ProGet feed, similar to what you already have in place for marking packages as unlisted and deprecated.
Just wanted to check if this was something that may be a feature in future
Thanks
-
From an API standpoint, I believe only npm packages support server-side tags. Rubygems might, but in any case we strongly advise against using them: https://blog.inedo.com/npm/smarter-npm-versioning-with-semver/
Server-side tagging is not likely something we will support in the future. Deprecation and Listing are really only there because many of the client APIs support them.
I'd need to see a strong, specific use case. If it's related to quality (e.g. dev, staging, prod), then it's a "hard no" because our solution to quality is prerelease version numbering/tagging with repackaging.
I do know that Sonatype Nexus has always supported tagging, but their repository is more of a "fileserver with server-side metadata" and ProGet is package-based. The only documented use case they have for tags has been quality, and our solution/approach is far superior.
Cheers,
Alex