From f97bc3e2ee3ef62b0442f8b8388e0bfaa37dd60d Mon Sep 17 00:00:00 2001 From: "Gudmundur D. Haraldsson" Date: Mon, 20 Nov 2023 11:33:44 +0000 Subject: [PATCH] Update SETUP.md --- docs/SETUP.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/SETUP.md b/docs/SETUP.md index 6a0c69af2..baaa5161b 100644 --- a/docs/SETUP.md +++ b/docs/SETUP.md @@ -121,7 +121,7 @@ Upgrading Node should be considered high-risk. Consider removing the dependency, if it is an NPM package. Can the functionality needed from the dependency be implemented directly into `vip-cli` or our own common libraries? If not, evaluate the following: 1. If the dependency is one of the [development dependencies](https://github.com/Automattic/vip-cli/blob/trunk/package.json) (`devDependencies`), and/or only used by one of those, the likelihood of customer-impacting failure is low. -1. Is the package used in the [deployment pipeline](RELEASING.md#deployments-to-production)? If it is, evaluate if any failure is likely to be silent. If that seems not to be the case, the risk of customer-impacting failure is low. +1. Is the package used in the [release process](RELEASING.md#releasing-a-new-version)? If it is, evaluate if any failure is likely to be silent. If that seems not to be the case, the risk of customer-impacting failure is low. #### Low risk dependencies