fix: public package check in libnpmpublish (#6530)

Removes a stray "true" in the boolean expression which determines whether the package's access is "public". Does not change behavior. Signed-off-by: Brian DeHamer <[email protected]>
npm · Jun 13, 2023 · 29622c1 · 29622c1
1 parent 7701105
commit 29622c1
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/workspaces/libnpmpublish/lib/publish.js b/workspaces/libnpmpublish/lib/publish.js
@@ -272,7 +272,7 @@ const ensureProvenanceGeneration = async (registry, spec, opts) => {
   // the package is always private and require `--access public` to publish
   // with provenance.
   let visibility = { public: false }
-  if (true && opts.access !== 'public') {
+  if (opts.access !== 'public') {
     try {
       const res = await npmFetch
         .json(`${registry}/-/package/${spec.escapedName}/visibility`, opts)