0.8.1

[helfer]

Thanks to @DxCx for fixing a bug where queries over HTTP GET would not go through validation.

[helfer]

Oh, now I see what's going on. I thought it was my mistake, but Lerna is auto-updating dependencies. Well how nice of Lerna ... 🙄

Fibers v2 does't compile on Node 4, so we can't update it as long as we want to keep support for Fibers. Trying to find out how to keep Lerna from doing that, but might have to resume tomorrow.

[helfer]

This line here is the problem. Fibers should not be updated. We might have to use a specific version range >= 1.0.15 < 2.0.0 here, but I don't know if that would work, and to test it we either have to dig through the lerna source, or try a new release...

[helfer]

Maybe we can downgrade to a version of lerna that doesn't do the auto-updating.

[DxCx]

@helfer does it happen even if you request specified version?

[helfer]

Well, now that's clearly a bug and not consistent with the lerna docs... Updating fibers=1.0.15 to 2.0.0

[helfer]

Ah, I found the issue. It has nothing to do with Lerna at all. It's the prerelease script in package.json. @DxCx what was the rationale for adding check-updates to the lerna release cycle? In other words, if I remove it, are we losing anything? I'd rather have something like greenkeeper take care of the dependencies.

[DxCx]

Ohh right, sorry i forgot about that, but yeah, back then we had some issue after release and it happend because one of the inner packages was not updated by greenkeeper. Anyway, we decided together on this behavior after it happened, we just both forgot about it :)

…

On Wed, 14 Jun 2017 at 5:11 Jonas Helfer ***@***.***> wrote: Ah, I found the issue. It has nothing to do with Lerna at all. It's the prerelease script in package.json. @DxCx <https://github.com/dxcx> what was the rationale for adding check-updates to the lerna release cycle? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#425 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABB8W2H5alUect9dQ0DX6CbsxA3G0ApDks5sD0FFgaJpZM4N4CWs> .

[helfer]

Haha, I guess we both forgot about it! Well I've removed it for now because it was causing problems with fibers. We'll need to find another way to keep dependencies updated if we can't pin a certain version. In any case, I think we should run the version updates manually so we can fix them by hand if necessary.