Switch back to a caret range for history

[timdorr]

This should be published as 1.0.3. Should fix both the warnings from history (removed in 1.16.0) and any errors about unmet peerDependencies.

Also, note this is on the 1.0.x branch.

[mjackson]

Thanks, @timdorr!

[mjackson]

Wonder why the Travis build didn't run here...

[timdorr]

We only build master

[mjackson]

Ah, crap. We should build PRs too. Otherwise we'll never know when it's safe to merge.

[mjackson]

It's my fault

[timdorr]

We do build PRs, but only those against master. This is the rare one not against master 😄

[mjackson]

oh, wait. so i didn't need to do this?

[mjackson]

maybe i just need to add 1.0.x to the only clause in the travis config?

[timdorr]

Yeah, we can whitelist the ones we want. I think you have to change the Travis file on master. But I'm not a Travis expert :)

[mjackson]

ok, I'm going to try pushing a modification to .travis.yml to this branch only. Then at least we can see how the build goes before we cut 1.0.3. Sorry for the confusion.

[timdorr]

BTW, the errors we're seeing on Travis I have seen before when going to at least history 1.14.0, so it looks like the behavior of those APIs changed just enough to break the tests. Fixed tests were put in on this PR, so I can replicate that for 1.0.3.

[taion]

@timdorr Can you cherry-pick in the test fixes for this PR then?

[timdorr]

Yep, I will.

[mjackson]

I think at least some of the errors were triggered by a bad expect release I made late last week. It's fixed now. I'm going to re-run the build.

[mjackson]

Ah, maybe not :/ @timdorr Do you think the fixes in #2659 will help?

[timdorr]

Yeah, since the fact that push/pushState was called with certain args isn't a good test. Testing the effects of that call is a good test. It's better in #2659.

[mjackson]

ok, great. If you can cherry-pick and get the build green let's ship 1.0.3. Thanks, btw :)

[timdorr]

Uh, I hate to be the bearer of bad news, but we missed a warning in 1.16.0. It's still coming up with how Link is implemented 😭

[timdorr]

Bonus points: The warning is backwards. It should be testing that query is not defined. Whoops!

[taion]

Oops.

[timdorr]

If we can push remix-run/history#190 as 1.16.1, all the warnings should go away. But this should be good as-is for now.

[taion]

Oops. Finger slipped. This should have been ^1.16.1, eh? Sorry.

[timdorr]

Not needed. Once 1.16.1 exists, then this 1.0.3 can be published.