fix: handle missing latest
tag during version check
#90
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
This PR makes two changes to how the calls to
npm view
andnpm publish
are made:npm view package-name
comes back empty due to [BUG]npm view package@latest
exits with code 0 and no output iflatest
tag does not exist npm/cli#6408, we will now retry withnpm view package-name@tag
, to try to get some informationnpm publish
fails because the requested version already exists, the action will not fail.Fixes #89
Change details
npmPublish
function is broken up to delegate to a newcompareAndPublish
function.npmrc
file is created, rather than two