GraphQL Breaking Change Checker

Store Positioning

Store title: GraphQL Breaking Change Checker

Short description: Compare GraphQL schemas and classify breaking, dangerous, and safe changes before release.

SEO title: GraphQL Breaking Change Checker — API, schema, and developer QA

SEO description: Compare GraphQL schemas and classify breaking, dangerous, and safe changes before release. Use it to catch contract drift, schema mistakes, unsafe endpoint assumptions, and developer-tool quality issues before release.

Categories: SEO_TOOLS, DEVELOPER_TOOLS, AUTOMATION

Keywords: graphql, breaking, change, checker, schema, change monitor, api/developer qa

Fixed-Inclusive PPE Pricing

This actor uses pay-per-event pricing. Event prices include Apify platform usage; users are not expected to pay a separate platform-usage pass-through charge for the configured pricing model.

• Tier: A1 — API/developer QA
• Primary event: schema-validated at $0.00650 base
• Default max charge: $10.00
• Store discounts: FREE/BRONZE base, SILVER discounted, GOLD deepest approved discount

Event set:

• actor-start: base $0.00500, GOLD $0.00400. Graphql Breaking Change Checker: charged when actor start is completed. The price includes Apify platform usage; no separate usage pass-through is intended.
• schema-validated: base $0.00650, GOLD $0.00520. Graphql Breaking Change Checker: charged when schema validated is completed. The price includes Apify platform usage; no separate usage pass-through is intended.
• contract-rule-checked: base $0.00390, GOLD $0.00312. Graphql Breaking Change Checker: charged when contract rule checked is completed. The price includes Apify platform usage; no separate usage pass-through is intended.
• report-generated: base $0.05000, GOLD $0.04000. Graphql Breaking Change Checker: charged when report generated is completed. The price includes Apify platform usage; no separate usage pass-through is intended.

Public Task Concepts

• Validate GraphQL Breaking Change Checker before release
• Run a bounded GraphQL Breaking Change Checker QA check
• Audit graphql issues across supplied public inputs
• Extract evidence-backed graphql rows for client QA
• Generate developer QA evidence for GraphQL Breaking Change Checker

What It Does

Compare GraphQL schemas and classify breaking, dangerous, and safe changes before release.

This local package is part of the Junipr Apify actors 171-200 premium build for ChatGPT review.

What It Does Not Do

• It does not call live Apify APIs.
• It does not publish, upload Store assets, create public tasks, or configure live PPE.
• It does not claim publish readiness.
• It does not make unbounded network calls in the supplied examples path.

Input Fields

Seed shape: oldSchema/newSchema or endpoint, headers, strictMode, maxTypes, includeReport

The tiny fixture is available at examples/input.tiny.json and mirrored at fixtures/input.tiny.json for the local runner.

Output Fields

• changeType
• severity
• typeName
• fieldName
• argumentName
• oldValue
• newValue
• message
• breaking

Public Task Examples

Compare two GraphQL schemas for breaking changes

• Search intent: compare two graphql schemas for breaking changes
• Specific input: Fixture input shaped for compare two graphql schemas for breaking changes.
• Expected output: Dataset rows with changeType, severity, typeName, fieldName plus local KVS report evidence.
• Why run it: API teams, platform teams, DevRel would run this to get a bounded local proof before any live Apify review or production use.

Detect removed fields in a GraphQL release

• Search intent: detect removed fields in a graphql release
• Specific input: Fixture input shaped for detect removed fields in a graphql release.
• Expected output: Dataset rows with changeType, severity, typeName, fieldName plus local KVS report evidence.
• Why run it: API teams, platform teams, DevRel would run this to get a bounded local proof before any live Apify review or production use.

Flag enum removals before API deployment

• Search intent: flag enum removals before api deployment
• Specific input: Fixture input shaped for flag enum removals before api deployment.
• Expected output: Dataset rows with changeType, severity, typeName, fieldName plus local KVS report evidence.
• Why run it: API teams, platform teams, DevRel would run this to get a bounded local proof before any live Apify review or production use.

Review nullability changes in a schema diff

• Search intent: review nullability changes in a schema diff
• Specific input: Fixture input shaped for review nullability changes in a schema diff.
• Expected output: Dataset rows with changeType, severity, typeName, fieldName plus local KVS report evidence.
• Why run it: API teams, platform teams, DevRel would run this to get a bounded local proof before any live Apify review or production use.

Create a breaking-change report for API consumers

• Search intent: create a breaking-change report for api consumers
• Specific input: Fixture input shaped for create a breaking-change report for api consumers.
• Expected output: Dataset rows with changeType, severity, typeName, fieldName plus local KVS report evidence.
• Why run it: API teams, platform teams, DevRel would run this to get a bounded local proof before any live Apify review or production use.

Tests

• Actor-specific fixture tests live in test/graphql-breaking-change-checker.test.ts.
• Node-based local suites validate dataset schema conformance, output samples, local smoke runs, and PPE guard behavior.

FAQ

Is this live on Apify?

No. This is a local package for ChatGPT review only.

Is it publish-ready?

No. It needs later live tiny-run validation and console configuration before any publication decision.