No token found and can't prompt for login when running with --non-interactive for gpr-publish
See original GitHub issueWhen I run yarn publish in github action for GPR, I get following error
yarn publish v1.22.4
warning package.json: No license field
warning package.json: No license field
[1/4] Bumping version...
info Current version: 2.0.0-beta.3
[2/4] Logging in...
error No token found and can't prompt for login when running with --non-interactive.
info Visit https://yarnpkg.com/en/docs/cli/publish for documentation about this command.
##[error]Process completed with exit code 1.
Meanwhile it works fine for NPM publish flow. My workflow configuration: https://github.com/AjayPoshak/instagram-story/blob/master/.github/workflows/npmpublish.yml
Issue Analytics
- State:
- Created 3 years ago
- Reactions:20
- Comments:9 (2 by maintainers)
Top Results From Across the Web
No token found and can't prompt for login when running with ...
In my repo I have the workflow like this: - run: yarn publish env: NODE_AUTH_TOKEN: ${{ secrets.NPM_AUTH_TOKEN }} I've added NPM_AUTH_TOKEN ...
Read more >Yarn can't authenticate with Github Packages - but npm can
Using an automation token will not prompt for a one-time passcode, meaning that you can use it as a secret in your publish...
Read more >GitHub package — way to go for your private npm packages
Step-by-step guide on how to use a free GitHub package registry to store private npm packages (often needed for the design systems).
Read more >Read more - Aaron Powell
nSummary In this post we’ve seen how we can run the Docker CosmosDB ... nIt looks like the login screen to a Microsoft...
Read more >tldr-book.pdf
Execute 100 HTTP POST requests to a URL, using a JSON payload from a file: ... Upgrade Azure CLI and Extensions without prompting...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I got it working for me.
I had not set the
publishConfig.registry
in mypackage.json
. With that set it works perfectly.I had the same issue and adding
always-auth
andregistry-url
worked for me, as suggested in this other issue / comment.