-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Bug introduced when "Removing accept header previews" Merged #2523
Comments
Hi! Sorry about that, I'll have a PR to fix it done soon. It looks like the areas affected are:
|
Thanks @JonruAlveus for getting this knocked out! I'll start working up a release for this now. ❤️ Thank you @casstait for the catch and sorry for the trouble! 🥇 |
As a side note, this next release has #2521 in it where we made both SDKs .NET Standard 2.0 |
Thanks for the awesomely fast turnaround time, @JonruAlveus and @nickfloyd! |
Hi there!
I believe a bug was introduced in version
1.0.1
from the PR that removed accept header previews.What used to occur was:
Where the
AcceptHeaders
was passed as a fourth argument to thePUT
method in theAPIConnection
class.What now occurs is:
Where the
AcceptHeaders
is removed and thetwoFactorAuthenticationCode
are set to null and the three argumentPUT
method now uses:Requiring and ensuring the
twoFactorAuthenticationCode
to be not null.This will throw an error now for any use of the
Put<T>(Uri uri, object data, string twoFactorAuthenticationCode)
method with thetwoFactorAuthenticationCode
set to null.We have reverted to version
1.0.0
but would like this to be fixed up as we'd like to use the functionality introduced in #2465.Stack trace:
Version Affected:
1.0.1
When was bug introduced:
https://github.com/octokit/octokit.net/pull/2515/files#diff-280ab49c2b24a3635079b0e7005677658e0043dbdfa48639e5fc637c71da2066R841
The text was updated successfully, but these errors were encountered: