Closed
Description
Hello! Thanks for the great action.
I noticed it always fails saying
##[error]Error: Unable to determine the current version of @pkg/NAME on NPM.
...when you do a first publish of the package (when you're just starting a repository). You need to manually push the first version, and then it will work.
Is it intended or can be fixed? I guess we can add an error handler here.
Thank you.
Metadata
Metadata
Assignees
Type
Projects
Milestone
Relationships
Development
Participants
Activity
JamesMessinger commentedon Sep 7, 2020
Good catch. I never thought about that because in my workflow the initial publish is usually done manually, not by CI/CD. But it makes total sense that this package should support that use case.
I'll leave this issue open and mark it as a bug to be fixed. I may not have the time to fix it for a while, but you're welcome to submit a PR if you have the time.
Fix first-time package publishing, fixes JS-DevTools#11
Fix first-time package publishing, fixes JS-DevTools#11
Fix first-time package publishing, fixes JS-DevTools#11
Fix first-time package publishing, fixes JS-DevTools#11
nikitaeverywhere commentedon Sep 7, 2020
Here we go!
nikitaeverywhere commentedon Sep 9, 2020
Ping @JamesMessinger there seems to be 2 PRs already to fix it, please review 😁
varunsridharan commentedon Sep 28, 2020
@JamesMessinger great action. and i really need this feature. and waiting for your review on (#12 #13 ) pull request.
Merge pull request #1 from ZitRos/patch-2
Merge pull request #12 from ZitRos/patch-2
4 remaining items