publish-npm-package: for maximum security, only display .npmrc when auto-generated

Author: giancosta86

actions/publish-npm-package/README.md

@@ -31,7 +31,7 @@ steps:
 
 1. Run `publish-github-pages` with the `optional` flag enabled.
 
-1. If the `.npmrc` file does not exist, generate a new one - publishing to the official npm registry and using the **NPM_TOKEN** environment variable as the authentication token.
+1. If the `.npmrc` file does not exist, generate a new one - publishing to the official npm registry and using the **NPM_TOKEN** environment variable as the authentication token. The `.npmrc` file will be displayed only if auto-generated.
 
 1. Run `pnpm publish`, with the value of `npm-token` injected into the **NPM_TOKEN** environment variable - accessible, for example, from the `.npmrc` configuration file.
 

actions/publish-npm-package/action.yml

@@ -108,11 +108,13 @@ runs:
           echo "🌟It seems you don't have a $npmConfigPath file - generating a default one..."
 
           echo '//registry.npmjs.org/:_authToken=${NPM_TOKEN}' > "$npmConfigPath"
-        fi
 
-        echo "🎀The content of the $npmConfigPath configuration file is:"
-        cat "$npmConfigPath"
-        echo "🎀🎀🎀"
+          echo "🎀Your auto-generated $npmConfigPath configuration file is:"
+          cat "$npmConfigPath"
+          echo "🎀🎀🎀"
+        else
+          echo "🌟You already have a custom $npmConfigPath file - ready to publish!"
+        fi
 
     - name: Publish to the registry
       shell: bash