-
Notifications
You must be signed in to change notification settings - Fork 157
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update-VSTeamNuGetPackageVersion is missing project path #421
Comments
Question. Do you get an exception or not? Does this work for you? I am asking because I tried e.g. Get-VSTeamFeed and the docs say also you need a project in the URL, but it works without:
|
@asbiin I tested it and the cmdlet is not wrong, but also not complete. The current cmdlet can only update packages if they are an org wide feed. If it's a project feed then you need the project. I will change the cmdlet to support both. |
@SebastianSchuetze YEs that's exactly he behavior. project feed have been introduced some months ago. |
Merged the code to fix it. So, it is closed. But currently we cannot release because of a bug in the pipeline can't figure out currently. |
The
Update-VSTeamNuGetPackageVersion
cmdlet does not include theproject
in the api call.See microsoft documentation: the template is
The
{project}
should be part of the API call, or we can see it is not included invsteam/Source/Public/Update-VSTeamNuGetPackageVersion.ps1
Line 31 in 7325dbd
The text was updated successfully, but these errors were encountered: