We’re excited to announce graph artifacts in Public Preview—bringing versioned, immutable schema packages to GraphOS.
Previously, managing supergraph schema deployments meant routers often pulled the “latest” schema, making it difficult to lock to a specific version for testing, roll back safely when issues arose, or audit which exact schema was running at a given time. Teams needed the same deployment controls for schemas that they have for application code.
Graph artifacts are designed to give you that control. With every schema publish, GraphOS automatically creates an immutable artifact identified by a unique SHA-256 digest. You can pin your router to that specific artifact, enabling you to:
-
Promote with confidence from staging to production using the exact same schema version
-
Roll back instantly by switching to a previous artifact reference—no republishing required
-
Maintain consistency across distributed router deployments with a single artifact SHA
-
Audit deployments with a timeline of which schema was running when
Graph artifacts require Apollo Router v2.7 or later and work seamlessly with the Apollo GraphOS Operator for Kubernetes deployments.
If you’re managing production supergraphs and want more control over schema releases, we encourage you to try graph artifacts and share your feedback in this thread. We’re particularly interested in hearing about your CI/CD integration experiences and which upcoming features matter most to your workflows (like custom tags or Rover CLI support). Check out the blog post to get started.