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 on publish #550

Closed
bwp91 opened this issue Jul 7, 2020 · 1 comment · Fixed by #552
Closed

error on publish #550

bwp91 opened this issue Jul 7, 2020 · 1 comment · Fixed by #552
Labels

Comments

@bwp91
Copy link

bwp91 commented Jul 7, 2020

Hi
Since upgrading to 6.3.0 I am receiving the following error:

  ✔ Pushing tags
  ✖ Creating release draft on GitHub
    → Expected `options` to be of type `object` but received type `undefined`

✖ Expected `options` to be of type `object` but received type `undefined`

Steps to reproduce

Hopefully the log below is sufficient:

ben@BEN-MACBOOK homebridge-ewelink-sonoff % np          

Publish a new version of homebridge-ewelink-sonoff (current: 1.6.1-0)

Commits:
- auto get region  27d4d7b

Commit Range:
v1.6.1-0...master

Registry:
https://registry.npmjs.org/

? Select semver increment or specify new version prerelease 	1.6.1-1
? How should this pre-release version be tagged in npm? next

  ✔ Prerequisite check
  ✔ Git
  ↓ Cleanup [skipped]
  ✔ Installing dependencies using npm
  ✔ Running tests using npm
  ✔ Bumping version using npm
  ✔ Publishing package using npm
  ✔ Pushing tags
  ✖ Creating release draft on GitHub
    → Expected `options` to be of type `object` but received type `undefined`

✖ Expected `options` to be of type `object` but received type `undefined`
ben@BEN-MACBOOK homebridge-ewelink-sonoff %   

Expected behavior

For it to complete the last step and open the browser to github to draft the new release

Environment

np - 6.3.0
Node.js - v14.5.0 (with npm 6.14.5)
Git - git version 2.24.3 (Apple Git-128)
OS - macOS catalina 10.15.6 Beta

@dopecodez
Copy link
Collaborator

Thanks for raising this, @thepotterfamily . Turns out this was a bug on our part. Fixed with #552 .
@sindresorhus , could you merge this PR asap?

@dopecodez dopecodez added the bug label Jul 7, 2020
@dopecodez dopecodez linked a pull request Jul 7, 2020 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants