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
Only publish to Gitlab registry #203
Comments
You could just overwrite nugetServer in config like described in the Readme but I guess that would not work with environment variables like CI_SERVER_URL. |
Yeah, I did think about that, but that would require a lot of workarounds to get it to work as smoothly and easily as just setting |
adds a flag that will skip publishing to NuGet server and only publish to (private) GitLab instance Contributes to #203
@fbjerggaard I think I managed to implement it, are you able to test it directly from the branch (by replacing package name with a git Url in package-json) or do you need a published NPM package? |
adds a flag that will skip publishing to NuGet server and only publish to (private) GitLab instance Contributes to #203
@Kampfmoehre Seems like I would need a published NPM package since |
I see, let's just publish it then as beta Edit: @fbjerggaard please try https://www.npmjs.com/package/@droidsolutions-oss/semantic-release-nuget/v/1.2.0-beta.1 |
Seems to work perfectly - the only issue I ran into was that it still required the |
This will be resolved in the final version, I'll wait a little bit until another issue that is also in the beta branch is resolved then I'll merge to release a final version. |
Awesome - thanks a lot for the prompt responses! |
This is included in v1.2.0. |
I have a need for publishing a package only to the GitLab registry, therefore I suggest adding a variable
publishToNuget
which defaults to true but allows the user to specify where to publish the package to.The way I see it, it should just be wrapping the following in an if-statement to check if the package should be published there.
Alternatively it could check whether
pluginConfig.nugetServer
is null - but that would break the current implementation.semantic-release-nuget/src/publish.ts
Lines 16 to 38 in 238a029
I am happy to provide a PR if this is a feature that is wanted.
The text was updated successfully, but these errors were encountered: