Manuel

> The issue, however, is that any breaking changes in Apollo Server would also result in breaking changes for Parse Server. I think it depends on risks and benefits of...

> [@mtrezza](https://github.com/mtrezza) I haven’t yet investigated the full impact of using Inversion of Control (IoC) by injecting an Apollo configuration or instance through Parse Server. However, it could be a...

> @mtrezza i improved the system btw: this update need to drop node 18 for parse-server Marked as breaking change; can be merged with Parse Server 9 which will drop...

Note that there is apparently a bug regarding introspection, see https://github.com/parse-community/parse-server/issues/9900. Does this PR address that issue as well?

@Moumouls could you fix the conflict?

@Moumouls All breaking change PRs for PS9 release are being prepared; could you please fix this conflict so the CI passes?

@coderabbitai List all breaking changes for this PR, for the change log entry.

BREAKING CHANGE: Upgrade to Apollo Server 5 and GraphQL express 5 integration; GraphQL introspection now requires using `masterKey` or setting `graphQLPublicIntrospection: true`.

The CI fails consistently for these tests: ``` 1) ParseGraphQLServer Auto API Schema Data Types should support files - Failed: Cannot read properties of null (reading 'someClass') 2) ParseGraphQLServer Auto...

Since this is a perf improvement, this PR should add a perf benchmark as well. The current [benchmark](https://github.com/parse-community/parse-server/actions/runs/20002561065?pr=9964) shows no significant improvement or degradation, which is a good sign so...