fix(deps): update apollo graphql packages - autoclosed

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
apollo-server-express (source)	2.17.0 -> 2.26.2
graphql-subscriptions	1.1.0 -> 1.2.1
graphql-tag	2.11.0 -> 2.12.6

---

Warning

Some dependencies could not be looked up. Check the warning logs for more information.

---

Release Notes

apollographql/apollo-server (apollo-server-express)

v2.26.2

Compare Source

v2.26.1

Compare Source

v2.26.0

Compare Source

v2.25.4

Compare Source

v2.25.3

Compare Source

v2.25.2

Compare Source

v2.25.1

Compare Source

v2.25.0

Compare Source

v2.24.1

Compare Source

v2.24.0

Compare Source

v2.23.0

Compare Source

v2.22.2

Compare Source

v2.22.1

Compare Source

v2.22.0

Compare Source

v2.21.2

Compare Source

v2.21.1

Compare Source

v2.21.0

Compare Source

v2.20.0

Compare Source

v2.19.2

Compare Source

v2.19.1

Compare Source

v2.19.0

Compare Source

v2.18.2

Compare Source

v2.18.1

Compare Source

v2.18.0

Compare Source

apollographql/graphql-subscriptions (graphql-subscriptions)

v1.2.1

Compare Source

• Fix memory leak in withFilter. PR #​209

v1.2.0

Compare Source

• Add graphql@15 to peerDependencies.

apollographql/graphql-tag (graphql-tag)

v2.12.6

Compare Source

• Update peer dependencies to allow graphql ^16.0.0.
  
  @​brainkim in #​530

v2.12.5

Compare Source

• Also publish src/ directory to npm, enabling source maps.
  
  @​maclockard in #​403

v2.12.4

Compare Source

• Allow fragments to be imported by name when using the webpack loader.
  
  @​dobesv in #​257

v2.12.3

Compare Source

• Update tslib dependency to version 2.1.0.
  
  @​benjamn in #​381

v2.12.2

Compare Source

• Avoid using Object.assign to attach extra properties to gql.
  
  @​benjamn in #​380

v2.12.1

Compare Source

• To accommodate older versions of TypeScript, usage of the import type ... syntax (introduced by #​325) has been removed, fixing issue #​345.
  
  @​benjamn in #​352

v2.12.0

Compare Source

• The graphql-tag repository has been converted to TypeScript, adding type safety and enabling both ECMAScript and CommonJS module exports. While these changes are intended to be as backwards-compatible as possible, we decided to bump the minor version to reflect the significant refactoring.
  
  @​PowerKiKi and @​benjamn in #​325

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - 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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

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

[codecov-io]

Codecov Report

Merging #221 (c96b310) into master (a9fd5f9) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #221   +/-   ##
=======================================
  Coverage   77.75%   77.75%           
=======================================
  Files          94       94           
  Lines        1551     1551           
  Branches      176      180    +4     
=======================================
  Hits         1206     1206           
+ Misses        314      312    -2     
- Partials       31       33    +2     

Impacted Files	Coverage Δ
...shared/state/containers/chat/redux/chat.reducer.ts	75.00% <0.00%> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update a9fd5f9...c96b310. Read the comment docs.

[guardrails]

All previously detected findings have been fixed. Good job! 👍🎉

We will keep this comment up-to-date as you go along and notify you of any security issues that we identify.

---

👉 Go to the dashboard for detailed results.

📥 Happy? Share your feedback with us.

[codecov-commenter]

Codecov Report

Patch coverage has no change and project coverage change: -4.84% ⚠️

Comparison is base (3abce88) 78.54% compared to head (91c3650) 73.71%.
Report is 5 commits behind head on master.

❗ Current head 91c3650 differs from pull request most recent head 61c3ae8. Consider uploading reports for the commit 61c3ae8 to get more accurate results

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #221      +/-   ##
==========================================
- Coverage   78.54%   73.71%   -4.84%     
==========================================
  Files          94       54      -40     
  Lines        1701      970     -731     
  Branches      215      140      -75     
==========================================
- Hits         1336      715     -621     
+ Misses        351      241     -110     
  Partials       14       14              

see 40 files with indirect coverage changes

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it 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 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 old lockfile 
npm WARN old lockfile The package-lock.json file was created with an old version of npm,
npm WARN old lockfile so supplemental metadata must be fetched from the registry.
npm WARN old lockfile 
npm WARN old lockfile This is a one-time fix-up, please be patient...
npm WARN old lockfile 
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: @nestjs/schematics@7.1.2
npm WARN Found: typescript@4.0.3
npm WARN node_modules/typescript
npm WARN   peer typescript@">= 3.x" from react-docgen-typescript@1.20.4
npm WARN   node_modules/react-docgen-typescript
npm WARN     react-docgen-typescript@"^1.15.0" from react-docgen-typescript-loader@3.7.2
npm WARN     node_modules/react-docgen-typescript-loader
npm WARN     1 more (react-docgen-typescript-plugin)
npm WARN   10 more (react-docgen-typescript-loader, ...)
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer typescript@"^3.4.5" from @nestjs/schematics@7.1.2
npm WARN node_modules/@nestjs/schematics
npm WARN   @nestjs/schematics@"^7.1.0" from @nestjs/cli@7.5.1
npm WARN   node_modules/@nestjs/cli
npm WARN 
npm WARN Conflicting peer dependency: typescript@3.9.10
npm WARN node_modules/typescript
npm WARN   peer typescript@"^3.4.5" from @nestjs/schematics@7.1.2
npm WARN   node_modules/@nestjs/schematics
npm WARN     @nestjs/schematics@"^7.1.0" from @nestjs/cli@7.5.1
npm WARN     node_modules/@nestjs/cli
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: connected-react-router@6.3.0
npm ERR! Found: react-redux@7.1.0
npm ERR! node_modules/react-redux
npm ERR!   react-redux@"7.1.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer react-redux@"^6.0.0" from connected-react-router@6.3.0
npm ERR! node_modules/connected-react-router
npm ERR!   connected-react-router@"6.3.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: react-redux@6.0.1
npm ERR! node_modules/react-redux
npm ERR!   peer react-redux@"^6.0.0" from connected-react-router@6.3.0
npm ERR!   node_modules/connected-react-router
npm ERR!     connected-react-router@"6.3.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! 
npm ERR! For a full report see:
npm ERR! /tmp/worker/14b246/4c0487/cache/others/npm/_logs/2023-09-26T11_29_59_066Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/worker/14b246/4c0487/cache/others/npm/_logs/2023-09-26T11_29_59_066Z-debug-0.log