This change addresses issue #1440 where NPM OIDC authentication was broken
because the action was exporting a fake NODE_AUTH_TOKEN value by default.
NPM OIDC requires NODE_AUTH_TOKEN to either be unset or empty for proper
authentication. The fix only exports NODE_AUTH_TOKEN if it was explicitly
set by the user, allowing OIDC to work while maintaining backward compatibility
for users who explicitly provide tokens.
BREAKING CHANGE: Users who rely on the fake default token should now explicitly
provide NODE_AUTH_TOKEN in their workflows or use OIDC authentication.
Fixes#1440
Related: https://github.com/actions/setup-node/issues/1440
* Remove always-auth configuration handling from setup-node
* docs: update README to note always-auth removal
Update README to mention removal of always-auth input
* Clarify removal of 'always-auth' input in README
Updated the description of the 'always-auth' input removal for clarity.
* Updates
* Update
* Update
* Update
* Update
* Yarn sometimes prefers npmrc, so use same token
* Description
* Update readme
* Feedback
* Add type
* new toolkit and scoped registries
* npmrc in RUNNER_TEMP
* Dont always auth
* Try exporting blank token
* Get auth working for now pending runner changes
* Fix string interpolation for auth token.
* Don't export both userconfigs
* Update authutil.js
* Add single quotes for authString
* Fix the registry string.
* Use userconfig and append trailing slash
* Keep in root of repo
* Try just adding auth token
* Remove auth token
* Try changes again
* Add tests
* Npm and GPR samples
* Add types
