generated from JS-DevTools/template-node-typescript
-
Notifications
You must be signed in to change notification settings - Fork 77
Issues: JS-DevTools/npm-publish
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Publishing fails if package doesn't exist yet
#16
by rikoe
was closed Oct 8, 2020
updated Oct 8, 2020
Getting 404 for first-time publish attempt
#23
by IdanAdar
was closed Jan 2, 2021
updated Jan 2, 2021
Error: TypeError: Unable to determine the current version of @owner/repo on NPM.
#24
by cpotter302
was closed Jan 2, 2021
updated Jan 2, 2021
TypeError: Unable to parse package.json
#32
by softmarshmallow
was closed Mar 14, 2021
updated Mar 14, 2021
Package successfully publishes to npmjs but also throws a 403
#37
by Yrlish
was closed May 6, 2021
updated May 6, 2021
Publish function always reports publishing to NPM even when alternative registry is used
#40
by rorysedgwick
was closed May 13, 2022
updated May 13, 2022
Any way to don't publish if not already published?
#48
by ftzi
was closed Apr 7, 2023
updated Apr 7, 2023
Token Authentication Failure on Publish to Custom Registry
#33
by MitchCroft
was closed Apr 7, 2023
updated Apr 7, 2023
Warning: Unexpected input(s) 'greater-version-only'
on action run
#52
by WillsterJohnson
was closed Apr 7, 2023
updated Apr 7, 2023
Add an option to only allow incremental package versions to be published
#43
by Tohaker
was closed Apr 7, 2023
updated Apr 7, 2023
Action does not publish non-scoped package to NPM
#53
by WillsterJohnson
was closed Apr 7, 2023
updated Apr 9, 2023
Previous Next
ProTip!
Find all open issues with in progress development work with linked:pr.