From 771a1cbf79e4645a42a25b7532557a4e6a2024bb Mon Sep 17 00:00:00 2001
From: Gar <gar+gh@danger.computer>
Date: Thu, 19 Aug 2021 08:48:14 -0700
Subject: chore(tests): fix snapshots

---
 tap-snapshots/test/lib/utils/config/definitions.js.test.cjs  | 6 ++++++
 tap-snapshots/test/lib/utils/config/describe-all.js.test.cjs | 6 ++++++
 2 files changed, 12 insertions(+)

(limited to 'tap-snapshots/test')

diff --git a/tap-snapshots/test/lib/utils/config/definitions.js.test.cjs b/tap-snapshots/test/lib/utils/config/definitions.js.test.cjs
index 01b137b8a..9d5fe79af 100644
--- a/tap-snapshots/test/lib/utils/config/definitions.js.test.cjs
+++ b/tap-snapshots/test/lib/utils/config/definitions.js.test.cjs
@@ -180,6 +180,12 @@ When publishing scoped packages, the access level defaults to \`restricted\`.
 If you want your scoped package to be publicly viewable (and installable)
 set \`--access=public\`. The only valid values for \`access\` are \`public\` and
 \`restricted\`. Unscoped packages _always_ have an access level of \`public\`.
+
+Note: Using the \`--access\` flag on the \`npm publish\` command will only set
+the package access level on the initial publish of the package. Any
+subsequent \`npm publish\` commands using the \`--access\` flag will not have an
+effect to the access level. To make changes to the access level after the
+initial publish use \`npm access\`.
 `
 
 exports[`test/lib/utils/config/definitions.js TAP > config description for all 1`] = `
diff --git a/tap-snapshots/test/lib/utils/config/describe-all.js.test.cjs b/tap-snapshots/test/lib/utils/config/describe-all.js.test.cjs
index d83e0f110..4e3efb916 100644
--- a/tap-snapshots/test/lib/utils/config/describe-all.js.test.cjs
+++ b/tap-snapshots/test/lib/utils/config/describe-all.js.test.cjs
@@ -30,6 +30,12 @@ If you want your scoped package to be publicly viewable (and installable)
 set \`--access=public\`. The only valid values for \`access\` are \`public\` and
 \`restricted\`. Unscoped packages _always_ have an access level of \`public\`.
 
+Note: Using the \`--access\` flag on the \`npm publish\` command will only set
+the package access level on the initial publish of the package. Any
+subsequent \`npm publish\` commands using the \`--access\` flag will not have an
+effect to the access level. To make changes to the access level after the
+initial publish use \`npm access\`.
+
 <!-- automatically generated, do not edit manually -->
 <!-- see lib/utils/config/definitions.js -->
 
-- 
cgit v1.2.3