Update dependency cross-env to v7

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
cross-env	6.0.3 -> 7.0.3

---

Release Notes

kentcdodds/cross-env

v7.0.3

Compare Source

Bug Fixes

• add maintenance mode notice (fe80c84)

v7.0.2

Compare Source

Reverts

• Revert "fix: signal handling (#​227)" (2a1f44c), closes #​227

v7.0.1

Compare Source

Bug Fixes

• signal handling (#​227) (8a9cf0e)

v7.0.0

Compare Source

Features

• update dependencies (#​223) (4ec6f40)

BREAKING CHANGES

• Drop Node 8 support

---

Configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, click this checkbox.

---

This PR has been generated by WhiteSource Renovate. View repository job log here.

[merge-mamba]

Potential Conflict Warning

This pull request has changes that overlap with branches below. You might want to check in with the other
branch authors before you merge to avoid a conflict. 🐍

renovate/dotenv-10.x (@renovate-bot)

• package.json (modified)

renovate/nodemon-2.x (@renovate-bot)

• package.json (modified)

renovate/cross-env-7.x (@renovate-bot)

• package.json (modified)

renovate/supertest-6.x (@renovate-bot)

• package.json (modified)

renovate/knex-0.x (@renovate-bot)

• package.json (modified)

renovate/pg-8.x (@renovate-bot)

• package.json (modified)

Something wrong? Got a suggestion? Email me or leave feedback here.

[renovate]

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you check the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: knex@0.21.21
npm ERR! Found: pg@7.18.2
npm ERR! node_modules/pg
npm ERR!   pg@"^7.15.2" from the root project
npm ERR!   peer pg@">5.0" from pg-pool@2.0.10
npm ERR!   node_modules/pg-pool
npm ERR!     pg-pool@"^2.0.10" from pg@7.18.2
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peerOptional pg@"^8.3.0" from knex@0.21.21
npm ERR! node_modules/knex
npm ERR!   knex@"^0.21.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: pg@8.7.1
npm ERR! node_modules/pg
npm ERR!   peerOptional pg@"^8.3.0" from knex@0.21.21
npm ERR!   node_modules/knex
npm ERR!     knex@"^0.21.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate-cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate-cache/others/npm/_logs/2021-08-17T10_07_35_320Z-debug.log

[viezly]

Pull request by bot. No need to analyze