generated from JS-DevTools/template-node-typescript
-
Notifications
You must be signed in to change notification settings - Fork 76
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
Upgrade Action to use node 16 instead of node 12
bug
Something isn't working
#61
by ericcornelissen
was closed Apr 8, 2023
Warning: Unexpected input(s) 'greater-version-only'
on action run
#52
by WillsterJohnson
was closed Apr 7, 2023
working-directory not respected
bug
Something isn't working
#51
by gravitypersists
was closed Apr 20, 2023
Error: Input required and not supplied: token
question
Further information is requested
#31
by lastdoctor
was closed Apr 7, 2023
Checking for npm package existence should ignore tag and check against all versions
bug
Something isn't working
#35
by rikoe
was closed Apr 20, 2023
If tag isn't specified, fall back to publishConfig
enhancement
New feature or request
#36
by rikoe
was closed Apr 20, 2023
Support NPM Package Provenance
enhancement
New feature or request
#88
by sachaw
was closed May 1, 2023
Specify Something isn't working
ignore-scripts
when publishing
bug
#47
by jamietanna
was closed Apr 20, 2023
Initial publish
bug
Something isn't working
good first issue
Good for newcomers
#11
by nikitaeverywhere
was closed Oct 1, 2020
Add an option to only allow incremental package versions to be published
#43
by Tohaker
was closed Apr 7, 2023
Extend package argument to handle directory, file, or archive
enhancement
New feature or request
#81
by razor-x
was closed Apr 20, 2023
Unable To Publish To Github Package Registry !!
more info needed
More information is needed to resolve the issue
#14
by varunsridharan
was closed Oct 2, 2020
Error: TypeError: Unable to determine the current version of @owner/repo on NPM.
#24
by cpotter302
was closed Jan 2, 2021
Previous Next
ProTip!
Find all open issues with in progress development work with linked:pr.