chore(deps): update dependency codecov to v3.8.3

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
codecov	3.8.2 → 3.8.3

---

Release Notes

codecov/codecov-node (codecov)

v3.8.3

Compare Source

Fixes

• #​329 fix: Test if response has two lines

Dependencies

• #​306 Bump eslint-config-prettier from 7.2.0 to 8.3.0
• #​305 Bump eslint from 7.21.0 to 7.25.0
• #​302 Bump mock-fs from 4.13.0 to 4.14.0
• #​308 Bump lodash from 4.17.19 to 4.17.21
• #​309 Bump ignore-walk from 3.0.3 to 3.0.4
• #​310 Bump hosted-git-info from 2.8.8 to 2.8.9
• #​325 Bump prettier from 2.2.1 to 2.3.2
• #​326 Bump actions/setup-node from 2.1.5 to 2.2.0
• #​328 Bump lint-staged from 10.5.4 to 11.0.1
• #​330 Bump eslint from 7.25.0 to 7.31.0
• #​331 Bump ws from 7.3.1 to 7.5.3
• #​332 Bump urlgrey from 0.4.4 to 1.0.0
• #​334 Bump husky from 6.0.0 to 7.0.1
• #​333 Bump teeny-request from 7.0.1 to 7.1.1

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • "every weekend"
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[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 click 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 warn Unknown env config "store". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @material-ui/core@4.9.14
npm error Found: react@17.0.2
npm error node_modules/react
npm error   react@"17.0.2" from the root project
npm error   peer react@"17.0.2" from @hot-loader/react-dom@17.0.2
npm error   node_modules/@hot-loader/react-dom
npm error     dev @hot-loader/react-dom@"17.0.2" from the root project
npm error   11 more (@testing-library/react, gatsby, gatsby-link, ...)
npm error
npm error Could not resolve dependency:
npm error peer react@"^16.8.0" from @material-ui/core@4.9.14
npm error node_modules/@material-ui/core
npm error   @material-ui/core@"4.9.14" from the root project
npm error   peer @material-ui/core@"^4.0.0" from @material-ui/icons@4.9.1
npm error   node_modules/@material-ui/icons
npm error     @material-ui/icons@"4.9.1" from the root project
npm error   1 more (@material-ui/lab)
npm error
npm error Conflicting peer dependency: react@16.14.0
npm error node_modules/react
npm error   peer react@"^16.8.0" from @material-ui/core@4.9.14
npm error   node_modules/@material-ui/core
npm error     @material-ui/core@"4.9.14" from the root project
npm error     peer @material-ui/core@"^4.0.0" from @material-ui/icons@4.9.1
npm error     node_modules/@material-ui/icons
npm error       @material-ui/icons@"4.9.1" from the root project
npm error     1 more (@material-ui/lab)
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-07-18T06_03_38_310Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-07-18T06_03_38_310Z-debug-0.log