You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In our company, we are maintaining the garlic project. Recently, we've tried pushing a new version of the nuget package created from this project to a github package repo. We're pushing the package with the dotnet nuget push command, specifying the source and access token as the key parameter. The commands runs successfully, but for some reason we cannot see the package, neither on the UI, nor in our IDEs. When we try to push it again with the same version, we get 409, which would mean that a package was already pushed. Please advise!
PackagesHost your dependencies, libraries, and production-ready code, right from your repositoryQuestion
1 participant
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Select Topic Area
Question
Body
In our company, we are maintaining the garlic project. Recently, we've tried pushing a new version of the nuget package created from this project to a github package repo. We're pushing the package with the dotnet nuget push command, specifying the source and access token as the key parameter. The commands runs successfully, but for some reason we cannot see the package, neither on the UI, nor in our IDEs. When we try to push it again with the same version, we get 409, which would mean that a package was already pushed. Please advise!
Beta Was this translation helpful? Give feedback.
All reactions