feat: schema version promotion by n1ru4l · Pull Request #8031 · graphql-hive/console

n1ru4l · 2026-05-10T21:07:33Z

Description

Introduces functionality for promoting a schema version from one target to another target (or the same target), making it the latest version within that target.

This enables workflows such as:

Promote schema version from one environment to another environment (staging to production)
Quick rollbacks to a specific previous schema version within one environment

A video walkthrough over this feature and implementation details exists here.

What should be reviewed?

I want Feedback on the UI
I am pretty confident with the database changes and API changes as they are covered with quite a few tests and I also manually confirmed all the behaviours many times 😄 Any comments on that are appreciated though

For either of those feel free to hit me up if you want to walk me through things.

CLI

A new CLI command schema:promote is introduced for promoting schema Version

# Promote specific version to target
hive schema:promote \
  --version 33172112-788d-469b-b06f-d5992b4f1ec7 \
  --to the-guild/graphql-hive/production

# Promote from target to target
hive schema:promote \
  --from the-guild/graphql-hive/staging \
  --to the-guild/graphql-hive/production

Permissions

A new permission schemaVersion:promote is introduced to restrict to which targets a schema version can be promoted.

New History UI

Alongside a new CLI command for performing these promotions this change also comes along a new UI for schema versions with more insights into the individual changes of the subgraphs.

A demo with some seeded history has been created on our dev environment.

More UI Screenshots

Database

The database was altered with new columns for storing the new data that is collected for subgraphs.
Refer to the migration file for a breakdown of all new introduced columns.

The database schema is fully backwards compatible. If any major issues occur on the business logic of the API, we can easily roll it back as all the changes introduced are additional.

GraphQL API

New fields have been added to determine the origin of a schema version (publish; delete; promotion)
A new mutation for promoting a schema version was introduced

Other

Closes #4021

github-actions · 2026-05-10T21:09:20Z

🚀 Snapshot Release (`alpha`)

The latest changes of this PR are available as alpha on npm (based on the declared changesets):

Package	Version	Info
`@graphql-hive/cli`	`0.60.0-alpha-20260601045530-fa604526b784e75a268b691ca903a3b75e03cab5`	npm ↗︎ unpkg ↗︎
`hive`	`11.2.0-alpha-20260601045530-fa604526b784e75a268b691ca903a3b75e03cab5`	npm ↗︎ unpkg ↗︎

n1ru4l · 2026-05-10T21:11:07Z

+    ALTER TABLE "schema_versions"
+      ALTER COLUMN IF EXISTS "action_id" DROP NOT NULL
+      , ADD COLUMN IF NOT EXISTS "origin" jsonb NULL
+      , ADD COLUMN IF NOT EXISTS "supergraph_changes" jsonb NULL


We store the public schema changes in a separate table schema_version_changes. However, we do not do anything with that table aside from loading the rows. No custom indices etc.

Thus I made the decision to add the column to store supergraph changes to the schema_versions table directly.

If nobody has objections I will refrain from introducing a new table for this.

github-actions · 2026-05-10T21:13:19Z

🐋 This PR was built and pushed to the following Docker images:

Targets: build

Platforms: linux/amd64

Image Tag: fa604526b784e75a268b691ca903a3b75e03cab5

gemini-code-assist

Code Review

This pull request introduces a schema version promotion feature, allowing users to promote a schema version from one target to another within a project. It includes a new database migration, GraphQL schema updates for the schemaVersionPromote mutation and PromotionSchemaLog type, and significant logic in SchemaPublisher and SchemaVersionStore to handle the promotion process and track version origins. Feedback includes identifying a missing crypto import that will cause runtime errors, a typo in a SQL string, and unsafe array access. Additionally, there are suggestions to update an incorrect migration comment, reconsider the use of a dummy field in the GraphQL schema, and evaluate if STITCHING projects should also support this feature.

n1ru4l · 2026-05-13T15:53:26Z

+    ALTER TABLE "schema_version_to_log"
+      ADD COLUMN IF NOT EXISTS type hive_subgraph_log_type DEFAULT NULL
+      , ADD COLUMN IF NOT EXISTS "previous_action_id" UUID DEFAULT NULL REFERENCES "schema_log"("id") ON DELETE CASCADE
+      , ADD COLUMN IF NOT EXISTS "schema_changes" JSONB DEFAULT NULL
+      , ADD COLUMN IF NOT EXISTS "subgraph_name" TEXT NULL
+    ;


This type stores now more complex information that serves the purpose of tracking how the subgraphs changed between schema versions.

n1ru4l · 2026-05-17T15:27:47Z

Updated integration tests to use SchemaVersion.meta and SchemaVersion.origin instead of the deprecated field SchemaVersion.log

n1ru4l · 2026-05-17T15:28:13Z

  message = 'Expected non-null value.',
 ): asserts value is T {
-  if (value === null) {
+  if (value == null) {


this helper was not doing what it should do 😆

n1ru4l · 2026-05-17T15:29:16Z

Updated to use the fields that are not deprecated.

n1ru4l · 2026-05-17T15:29:37Z

A bunch of tests tor the new schema version promote functionality

n1ru4l · 2026-05-17T15:30:03Z

New CLI command for promotion a schema version.

…sion

n1ru4l commented May 10, 2026

View reviewed changes

Comment thread packages/migrations/src/actions/2026.05.07T00-00-00.schema-version-promotion.ts Outdated

n1ru4l commented May 10, 2026

View reviewed changes

Comment thread packages/services/api/src/modules/schema/module.graphql.ts

gemini-code-assist Bot reviewed May 10, 2026

View reviewed changes

n1ru4l force-pushed the feat-schema-version-promotion branch 2 times, most recently from 91ca78a to 05a3f05 Compare May 10, 2026 21:18

Base automatically changed from chore-refactor-schema-version-store to main May 11, 2026 20:59

n1ru4l force-pushed the feat-schema-version-promotion branch 6 times, most recently from c0f20b4 to 9d6cac5 Compare May 13, 2026 10:49

n1ru4l changed the title ~~Feat schema version promotion~~ feat: schema version promotion May 13, 2026

n1ru4l commented May 13, 2026

View reviewed changes

Comment thread packages/migrations/src/actions/2026.05.07T00-00-00.schema-version-promotion.ts

n1ru4l commented May 13, 2026

View reviewed changes

n1ru4l force-pushed the feat-schema-version-promotion branch 3 times, most recently from 0688fb7 to 7c4350f Compare May 17, 2026 11:44

n1ru4l mentioned this pull request May 17, 2026

post schema version promotion cleanup tasks #8052

Open

n1ru4l commented May 17, 2026

View reviewed changes

n1ru4l force-pushed the feat-schema-version-promotion branch 3 times, most recently from a3681e8 to fd280ee Compare May 17, 2026 18:20

n1ru4l added 22 commits May 29, 2026 16:13

smaller screen size adjustments

414b8ab

download button + responsiveness on smaller screens for header

de22a8a

faster

963d3a7

cleanup

dd81fe9

speed

f6a22db

fix spacing

3701a1c

fix spacing and size

7620ac0

unify styles

c365d36

unify styles more

9c6cb29

moar

121c252

moar

68ebcd3

workerpool perf etc

bc6d5c5

add note about service url only changes

d3ab820

error component

4d156f0

lint

0ffe5ad

abandon tabs for monolitic schema

57cb656

use correct naming and fix wrong target being associated with the ver…

feb7164

…sion

fix

7144fc1

add test to show issues fixed by #8091

750fc55

did this cook the memory?

1cd44d2

ok

74a3632

just a tiny tiny small fix

1f340b8

n1ru4l force-pushed the feat-schema-version-promotion branch from ab1d72b to 1f340b8 Compare May 29, 2026 14:13

n1ru4l added 3 commits May 29, 2026 16:19

this was an accident

cf3d066

geee

a38c97a

now

fa60452

n1ru4l merged commit 51345a9 into main Jun 1, 2026
23 of 24 checks passed

n1ru4l deleted the feat-schema-version-promotion branch June 1, 2026 05:16

theguild-bot mentioned this pull request Jun 1, 2026

Upcoming Release Changes #8081

Merged

n1ru4l mentioned this pull request Jun 1, 2026

Use virtualization and worker threads for supergraph and subgraph rendering on schema history #8097

Open

Uh oh!

Conversation

n1ru4l commented May 10, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Description

CLI

Permissions

New History UI

Database

GraphQL API

Other

Uh oh!

Uh oh!

github-actions Bot commented May 10, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

🚀 Snapshot Release (alpha)

Uh oh!

n1ru4l May 10, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

github-actions Bot commented May 10, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

Code Review

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

n1ru4l May 13, 2026

Choose a reason for hiding this comment

Uh oh!

n1ru4l May 17, 2026

Choose a reason for hiding this comment

Uh oh!

n1ru4l May 17, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

n1ru4l May 17, 2026

Choose a reason for hiding this comment

Uh oh!

n1ru4l May 17, 2026

Choose a reason for hiding this comment

Uh oh!

n1ru4l May 17, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Milestone

Development

Uh oh!

3 participants

n1ru4l commented May 10, 2026 •

edited

Loading

github-actions Bot commented May 10, 2026 •

edited

Loading

🚀 Snapshot Release (`alpha`)

n1ru4l May 10, 2026 •

edited

Loading

github-actions Bot commented May 10, 2026 •

edited

Loading

n1ru4l May 17, 2026 •

edited

Loading