Disable the unmaintained graphql-schema-linter - #8894
Merged
Conversation
graphql-schema-linter has had no release or commit since May 2022, and its peer dependency range pins graphql to ^15 || ^16. Since graphql is installed only to satisfy that peer, the whole GraphQL npm install was held back from graphql v17. GRAPHQL_BIOME still lints GraphQL files.
nvuillam
requested review from
Kurt-von-Laven,
bdovaz and
echoix
as code owners
September 4, 2026 04:07
Contributor
✅
|
…chema-linter # Conflicts: # Dockerfile # flavors/cupcake/Dockerfile # flavors/go/Dockerfile
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

Summary
peerDependenciespingraphqlto^15.0.0 || ^16.0.0. Sincegraphqlis installed only to satisfy that peer, the unmaintained linter was holding the whole GraphQL npm install back from graphql v17 (see chore(deps): update dependency graphql to v17 #8150, which fails with a hardERESOLVE).Follows the same pattern as the already-disabled
COFFEE_COFFEELINT:disabled: true+disabled_reasonin the descriptor, with the linter to be removed in a future version.Changes
megalinter/descriptors/graphql.megalinter-descriptor.yml—disabled: true+disabled_reasonmake megalinter-build: mainDockerfile, the 15 flavors that shipped the linter,linters_matrix.json,all_flavors.jsonCHANGELOG.mdentry under Disabled lintersTest plan
graphql/graphql-schema-linterdisappear from every image)GRAPHQL_BIOMEstill runs on.graphqlfiles