-
Notifications
You must be signed in to change notification settings - Fork 38
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: Resolve whatBump is not a function error #105
fix: Resolve whatBump is not a function error #105
Conversation
commit: |
Thanks a lot, @oluwatobiss! This looks promising. One thing I don't really like is the Would like a helping hand here, so cc-ing @ayZagen, @will-stone, @egilsster, @LinuCC, @splincode, @tefanobartoletti, @andi1984-ds, @janbiasi, @chris-dura, @Tomas2D. Any chance you could give this a shot:
|
I can confirm that this version fixes the issue on my side. |
Sure! |
Updated! |
9.0.1 fixed most of our woes, but one project was still having issues. The version above solves those 🎉 thanks for addressing this! |
Released v9.0.2 Thanks a lot @oluwatobiss, you saved all of us! 🙏 |
This PR does the following:
ERROR whatBump is not a function
error by resolving the pendingpreset
promise and passing the appropriatewhatBump
argument tobumper.bump()
.release-it
to skip releasing a version. (Any accepted variation of awhatBump: false
configuration option would do the job..release-it.json
Example.release-it.js
ExamplePassing test's result
Resolves #101, resolves #103