From da1eeea02b9b7adc3abec70c09819d7ec9fde854 Mon Sep 17 00:00:00 2001 From: HonkingGoose <34918129+HonkingGoose@users.noreply.github.com> Date: Fri, 10 Mar 2023 17:24:35 +0100 Subject: [PATCH] docs: replace unencrypted with plaintext (#20849) --- docs/usage/getting-started/private-packages.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/usage/getting-started/private-packages.md b/docs/usage/getting-started/private-packages.md index e9aaa54b5b..3fd93fbef6 100644 --- a/docs/usage/getting-started/private-packages.md +++ b/docs/usage/getting-started/private-packages.md @@ -231,7 +231,7 @@ The recommended approaches in order of preference are: 1. **Self-hosted hostRules**: Configure a hostRules entry in the bot's `config.js` with the `hostType`, `matchHost` and `token` specified 1. **Renovate App with private modules from npmjs.org**: Add an encrypted `npmToken` to your Renovate config -1. **Renovate App with a private registry**: Add an unencrypted `npmrc` plus an encrypted `npmToken` in config +1. **Renovate App with a private registry**: Add an plaintext `npmrc` plus an encrypted `npmToken` in config These approaches are described in full below. @@ -296,7 +296,7 @@ If you are using the main npmjs registry then you can configure just the `npmTok #### Add an encrypted npm token to Renovate config -If you don't want all users of the repository to see the unencrypted token, you can encrypt it with Renovate's public key instead, so that only Renovate can decrypt it. +If you don't want all users of the repository to see the plaintext token, you can encrypt it with Renovate's public key instead, so that only Renovate can decrypt it. Go to <https://app.renovatebot.com/encrypt>, paste in your npm token, select "Encrypt", then copy the encrypted result. -- GitLab