-
Notifications
You must be signed in to change notification settings - Fork 14
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
Issue 1927: Skip publish for npm and nuget #27
Issue 1927: Skip publish for npm and nuget #27
Conversation
working-directory: 'hello-strongbox-nuget-mono' | ||
- run: nuget pack ./Hello.Strongbox.Nuget.Mono.nuspec | ||
working-directory: 'hello-strongbox-nuget-mono' | ||
- run: nuget push *.nupkg -SkipDuplicate |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
From NuGet CLI push command docs:
-SkipDuplicate
(5.1+) If a package and version already exists, skip it and continue with the next package in the push, if any.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fantastic! Thanks! :)
@@ -30,7 +60,13 @@ jobs: | |||
scope: '@strongbox' | |||
- run: npm install | |||
working-directory: 'hello-strongbox-npm' | |||
- run: npm publish | |||
- run: | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
npm info <existing_package_name>
returns a non-empty string (existing package's info).
Thanks for these follow-up fixes! :) |
Skip publishing non-Maven based artifacts
Refs strongbox/strongbox#1927
This is based off of the
issue-1927-nuget-examples
branch in #25.