-
Notifications
You must be signed in to change notification settings - Fork 471
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
Release 4.3.1 #372
Comments
@jonorossi - I think it would be good to wait a couple more days, hoping to get a further response in #371. If default value reproduction really causes problems (again), I'd like to fix it asap. Update: I've found a way to provoke the reported error (#371 (comment)), although I can't be sure at this point whether it's the same cause or a different one. Either way, I'll prepare a fix for what I've found, and if we don't hear back from @zplan within a few days, there's still some chance that his issue might be fixed. |
Maybe we should point @zvirja to our appveyor nuget’s for ci-builds while waiting. I am commuting right now will fish out a link when I get into the office. |
@fir3pho3nixx Thanks a lot. Unfortunately, that will not work, as I don't want to change our CI for that single case. Rather, I'm fine waiting for a couple of days before @zplan provides the scenario. |
I just got feedback from him over at Moq, seems I'm onto the right problem. I should have a fix ready today or tomorrow. |
@jonorossi Are we ready to proceed now? 😊 |
@stakx do we need to update the changelog for your changes in bcba394? Compare: v4.3.0...master We can make another release if the BadImageFormatException problem is fixed. |
@jonorossi - I've just submitted #388 (changelog entry) if you want to document #383 (fix for possible concurrency issue). Unfortunately, that PR didn't fix all of #193 (BadImageFormatException issue), though it might have resolved the |
@stakx no problem, don't worry I'm following along with that issue even though letting you guys work it out. |
Windsor upgrade imminent. :) |
@zvirja would like the fix for #369 released.
I was hoping we'd get as repro for #371 so we can fix that defect before making a bugfix release.
@castleproject/committers your input?
The text was updated successfully, but these errors were encountered: