-
Notifications
You must be signed in to change notification settings - Fork 83
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
7.11.1 introduces typescript compile error with aggregate-error #235
Comments
This was already encoded in the package-lock.json, but since package.json is the only one that gets published to consumers, it's important for this version update to be expressed in package.json since in fact 3.0.1 leads to a typescript compile error. Fixes octokit#235
Hi @AArnott, thanks for your opened issue. I just run an
Thanks once again for your opened issue :) |
@AArnott I've been able to reproduce the issue. Forcing |
This was already encoded in the package-lock.json, but since package.json is the only one that gets published to consumers, it's important for this version update to be expressed in package.json since in fact 3.0.1 leads to a typescript compile error. Fixes octokit#235
This was already encoded in the package-lock.json, but since package.json is the only one that gets published to consumers, it's important for this version update to be expressed in package.json since in fact 3.0.1 leads to a typescript compile error. Fixes #235
🎉 This issue has been resolved in version 7.11.2 🎉 The release is available on: Your semantic-release bot 📦🚀 |
#183 introduced a typescript compile break when it added a use of
AggregateError<T>
while still referencingaggregate-error ^3.0.1
. 3.0.1 does not define a genericAggregateError<T>
type, which leads octokit 7.11.1 consumers to encounter this typescript compiler error:Please update project.json to depend on
aggregate-error ^3.1.0
to fix the break and release a new npm package.The text was updated successfully, but these errors were encountered: