From d7e14f6d02e0fefb8ddf7552408d44032233246c Mon Sep 17 00:00:00 2001 From: Matt Travi Date: Fri, 31 Mar 2023 15:09:10 -0500 Subject: [PATCH] docs(artifactory): removed details about using artifactory with legacy auth since we no longer support legacy auth in the npm plugin and artifcatory can use modern auth with more recent versions --- docs/support/FAQ.md | 8 -------- 1 file changed, 8 deletions(-) diff --git a/docs/support/FAQ.md b/docs/support/FAQ.md index c19a05af..f0b2cdcd 100644 --- a/docs/support/FAQ.md +++ b/docs/support/FAQ.md @@ -158,14 +158,6 @@ Or with the `publishConfig.access` key in your project's `package.json`: } ``` -## Can I use semantic-release to publish a package on Artifactory? - -Any npm compatible registry is supported with the [`@semantic-release/npm`](https://github.com/semantic-release/npm) plugin. For Artifactory versions prior to 5.4, the legacy authentication has to be used (with `NPM_USERNAME`, `NPM_PASSWORD` and `NPM_EMAIL` [environment variables](https://github.com/semantic-release/npm#environment-variables)). - -See [npm registry authentication](https://github.com/semantic-release/npm#npm-registry-authentication) for more details. - -See [Artifactory - npm Registry](https://www.jfrog.com/confluence/display/RTF/Npm+Registry#NpmRegistry-AuthenticatingthenpmClient) documentation for Artifactory configuration. - ## Can I manually trigger the release of a specific version? You can trigger a release by pushing to your Git repository. You deliberately cannot trigger a _specific_ version release, because this is the whole point of semantic-release.