-
Notifications
You must be signed in to change notification settings - Fork 213
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
fix: ensure that we can define dependency argument in config #743
Conversation
@joaomoreno If you can take a look at this it would be awesome, that is a real blocker for our switch from npm to yarn for building, as we cannot add custom command line arguments to vsce calls. |
Sadly I am unable to request the failed job rerun. I am sure it was a glitch and that has nothing to do with this PR. |
Please approve GHA run. |
Any chance to get this merged? Asking as I do not want to miss it from the next release. Thanks! |
🎉 This PR is included in version 2.9.2 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Commander documentation states that when using negative commands, if you do not already have a non-negative command it sets the default to
true
, which is what broke the logic for loading defaults frompackage.json
.Fixes: #742
Reference: https://www.npmjs.com/package/commander#other-option-types-negatable-boolean-and-booleanvalue