Skip to content

TypeError: Cannot read property 'name' of undefined #185

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

Closed
sgraham785 opened this issue Jan 10, 2020 · 2 comments
Closed

TypeError: Cannot read property 'name' of undefined #185

sgraham785 opened this issue Jan 10, 2020 · 2 comments
Labels

Comments

@sgraham785
Copy link

started seeing this error using semantic-release@15 running npx semantic-release --branch master --extends ./semantic-release/release-config.js

[8:54:45 PM] [semantic-release] › ✖  An error occurred while running semantic-release: { TypeError: Cannot read property 'name' of undefined
--
332 | at module.exports (/usr/local/lib/node_modules/@semantic-release/git/lib/prepare.js:69:38)
333 | at process._tickCallback (internal/process/next_tick.js:68:7)
334 | pluginName: '/usr/local/lib/node_modules/@semantic-release/git' }
335 | { TypeError: Cannot read property 'name' of undefined
336 | at module.exports (/usr/local/lib/node_modules/@semantic-release/git/lib/prepare.js:69:38)
337 | at process._tickCallback (internal/process/next_tick.js:68:7)
338 | pluginName: ·[32m'/usr/local/lib/node_modules/@semantic-release/git'·[39m }
339 | [Container] 2020/01/10 20:54:45 Command did not exit successfully npx semantic-release --branch master --extends ./semantic-release/release-config.js exit status 1

@pvdlg
Copy link
Member

pvdlg commented Jan 10, 2020

That's because you are using a version of this plugin that is meant for semantic-release 16.
There is a peerDependency defined that should have give you a warning when you do npm install.

@pvdlg pvdlg closed this as completed Jan 10, 2020
@pvdlg pvdlg added the support label Jan 10, 2020
@sgraham785
Copy link
Author

thanks. updating to semantic-release@16 fixes the issue, with no further changes for me

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

No branches or pull requests

2 participants