Replies: 1 comment
-
🕒 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
👋 hey there GH community. I've really been struggling to publish github packages, Now I got a mono repo, called tools and the are different tools in it. like toolA, toolB, and each tool has different package.json and package name.
I want to build each tool as a package and publish them into the same repo. I found that this post mentioned that we need keep the package name same with the repo name. otherwise when you run npm publish, you will encounter a 403 error:
403 Forbidden - PUT https://npm.pkg.github.com/@xxxx/xx - Permission permission_denied: write_package
npm ERR! 403 In most cases, you or one of your dependencies are requesting
npm ERR! 403 a package version that is forbidden by your security policy.
Is there any workaround?
Beta Was this translation helpful? Give feedback.
All reactions