-
Notifications
You must be signed in to change notification settings - Fork 249
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Not able to publish the package to npm. #321
Comments
Ok, had some issues in my yaml. First of all:
I have NPM_TOKEN set in my Github, but I am not able to set my GITHUB_TOKEN becuase github does not allow token name that starts with GITHUB_ |
So I just changed the name for GITHUB_TOKEN and instead in my publish.yaml I have it like this: But the error is still 404. I don't know what am I suppose to do now |
GITHUB_TOKEN is already provided by GitHub, you don't have to add it to your secrets, you can just use it
|
Im having the same problem, trying to publish to npm but I always get the same message: |
Using github actions.
My publish.yaml looks like this:
When I push the changes to githug the release action is successful but I get this message:
"body": "This PR was opened by the [Changesets release](https://github.com/changesets/action) GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.\n\n\n# Releases\n## @crypties/[email protected]\n\n### Patch Changes\n\n- 052b371: Initial publish\n",
When I merge the PR then I get the errror:
The text was updated successfully, but these errors were encountered: