bump for cypress 3.2.0

[Pomax]

Cypress got updated to 3.2.0, so it might be worth explicitly updating the dependency in package.json and then running an npm patch release.

[Robdel12]

Hey there! When I was doing some testing with the latest cypress I ran into a lot of issues with domains: cypress-io/cypress#3717 So I'd be a little wary locking to that version.

Also, we specify "^3.1.3" which will grab the latest patch version (3.2.0 in this case)

I believe it should update in your project if you install 3.2.0 (and had an older version previously)

[Pomax]

it does, but npm's had a ton of fun gaffs the last year or so, so at this point a good package-lock.json is a locked down package-lock.json that absolutely never respects ^ and just pulls the exact version so it's on a known good version =)

That said, it sounds like 3.2.0 is not a good version =(

[Robdel12]

Ah, yeah, I hear you there! I usually run npm update @percy/cypress (or yarn upgrade @percy/cypress) to update the lockfiles

[djones]

Closing this one since our package-lock.json file has resolved to version cypress@3.2.0.

We usually bump the version requirements in the package.json if a particular version of @percy/cypress requires a higher version of a dependency. This #80 is a good example of that.