Skip to content
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

Error: TypeError: Unable to determine the current version of @owner/repo on NPM. #24

Closed
cpotter302 opened this issue Dec 2, 2020 · 3 comments

Comments

@cpotter302
Copy link

Hello there, I am using npm https://npm.pkg.github.com as my npm package registry. Unfortunately i always get this error when it start my workflow.
Full log comes here:

Run JS-DevTools/npm-publish@v1
with:
token: ***
registry: https://npm.pkg.github.com
check-version: false
package: package.json
tag: latest
dry-run: false
Error: TypeError: Unable to determine the current version of @cpotter302/ubuntu-welcome-page on NPM.
Invalid Version:
at Object.getLatestVersion (/home/runner/work/_actions/JS-DevTools/npm-publish/v1/src/npm.ts:57:13)
at processTicksAndRejections (internal/process/task_queues.js:93:5)
at Object.npmPublish (/home/runner/work/_actions/JS-DevTools/npm-publish/v1/src/npm-publish.ts:16:26)
at main (/home/runner/work/_actions/JS-DevTools/npm-publish/v1/src/action/index.ts:28:19)

TypeError: Invalid Version:
at new SemVer (/home/runner/work/_actions/JS-DevTools/npm-publish/v1/dist/node_modules/semver/classes/semver.js:41:13)
at Object.getLatestVersion (/home/runner/work/_actions/JS-DevTools/npm-publish/v1/src/npm.ts:51:20)
at processTicksAndRejections (internal/process/task_queues.js:93:5)
at Object.npmPublish (/home/runner/work/_actions/JS-DevTools/npm-publish/v1/src/npm-publish.ts:16:26)
at main (/home/runner/work/_actions/JS-DevTools/npm-publish/v1/src/action/index.ts:28:19)

@RubenVerborgh
Copy link

Same error for us: https://github.com/solid/mashlib/runs/1510028311?check_suite_focus=true

The exact same workflow works fine on our other repositories.

@JamesMessinger
Copy link
Member

This should now be fixed by PR #19, which was just released as version 1.4.1

@RubenVerborgh
Copy link

@JamesMessinger Not really, but it is fixed by #25.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants