-
Notifications
You must be signed in to change notification settings - Fork 106
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
chore!: upgrade got to 11.8.5 #225
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is a breaking change, as it raises the minimum Node.js version?
Also for some reason the tests haven't been triggered |
Ah, you're correct. The requirement for got v11 is |
Added the change to the minimum supported node version requirement to this PR as well just to make sure it doesn't get lost, if we choose to merge this. |
A couple of things:
|
Looks like a dependency from this got version ( |
Any update? |
See #224 (comment), merging this change needs to be coordinated properly. |
Based on #226 (comment) discussions. I think we should just upgrade instead of waiting for cc: @malept |
We're not waiting for |
What are the reasons that are stopping this PR from being merged now? I want to push for this PR to be merged. The most important reason, as I understand it so far, is the impact of the minimum node version |
If this impact is so important to us that we cannot merge this PR in a short time, is there another way, for example, if we fork |
🎉 This PR is included in version 2.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Bumps the dependency on
got
to version 11.8.5, fixing a dependabot alert.got
also now includes its own type definitions, so the dependency on@types/got
could be removed as well.