Replies: 2 comments
-
I've been waiting for 3 years, don't know what they are thinking about. |
Beta Was this translation helpful? Give feedback.
-
🕒 Discussion Activity Reminder 🕒 This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions: 1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as 2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own. 3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution. Note: This dormant notification will only apply to Discussions with the Thank you for helping bring this Discussion to a resolution! 💬 |
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Question
Body
Our organization decided to make public the npm package that we had been publishing via Github Packages, as we do not want to store Personal Access Token(PAT) in plaintext in the .npmrc file. However, I still need PAT to install the package(I deleted the .npmrc file, then I got 404 error when installing the package).
I thought that making the package public would eliminate the need for PAT, am I wrong?
Is there any way to install a package that is public in GIthub Packages without PAT?
Beta Was this translation helpful? Give feedback.
All reactions