Skip to content

Prepare the stable GraphiQL 6 release - #4598

Merged
trevor-scheer merged 28 commits into
graphiql-6from
trevor/graphiql-6-final-cutover
Nov 1, 2026
Merged

trevor-scheer merged 28 commits into
graphiql-6from
trevor/graphiql-6-final-cutover

Conversation

@trevor-scheer

@trevor-scheer trevor-scheer commented Sep 29, 2026 •

Copy link
Copy Markdown
Contributor

The v6 branch is still in Changesets prerelease mode, with pending notes describing both the v5 → v6 changes and iterations during the beta/RC cycle. This prepares the inputs for the automated stable release PR: consolidate those notes and mark prerelease mode for exit. Package versions, generated changelogs, and the lockfile remain at their prerelease values.

The 37 pending notes were all specific to v6; none came from unreleased main work. They are consolidated into 24 consumer-facing entries. Visual changes live in the reskin entry, transport behavior and hooks live in the transport entry, and prerelease-only pinning/promotion notes are removed. Published prerelease changelog history is preserved.

pre.json is set to mode: "exit". Merging this PR into graphiql-6 lets the existing Changesets workflow open or update its release PR with stable versions, dependency ranges, changelogs, and lockfile changes. Merging that generated release PR triggers publication. This preparation does not consume the pending changesets or publish packages.

The read-only release plan produces: GraphiQL / code exporter / language service 6.0.0; React, toolkit, the remaining plugins, cm6-graphql, and the versioned VS Code extensions 1.0.0; Monaco GraphQL 2.0.0; CodeMirror GraphQL / language service server 3.0.0; language service CLI 4.0.0. VS Code syntax stays at 1.3.13.

Release preparation (this PR)

  • Preserve the operation/method controls and reactive transport APIs from Join Run, operation selection, and request method controls #4673 and selection styling from Unify selection styling with GraphQL pink #4674.
  • Consolidate pending changesets into the net v5 → v6 changes, including the current transport API contract and discovery behavior.
  • Mark prerelease mode for exit, retaining the pending changesets for the automated release PR.
  • Verify the expected stable release plan; leave generated versions, changelogs, and lockfile changes to the automated release PR.
  • Point the esm.sh GraphQL worker helper and matching declaration at monaco-graphql@2.
  • Cut graphiql-5 from current main (eeaa50e4085aa19de328da253834aef204f07324) for v5 maintenance. Preserve its previous tip (ed31b72f04f2d1f100361b4c32718be3130ee550) under graphiql-5-original.

Automated release PR

  • Merge this preparation into graphiql-6 and let Changesets open its release PR (Version Packages #4676).
  • Review Version Packages #4676's stable versions, internal dependency ranges, changelogs, and lockfile.
  • On Version Packages #4676, refresh the five plugins' remaining @graphiql/react RC peer ranges to ^1.0.0 and verify the lockfile (no further lockfile change was needed). Confirm no internal beta/RC ranges remain in active manifests or workspace examples.
  • Merge the generated release PR at the intended release time; let the workflow publish and verify the expected versions under npm latest.

After stable publication

  • Land Finish GraphiQL 6 post-release CDN cleanup #4675 after regenerating and smoke-testing both CDN examples and confirming release automation has moved to main.
  • Before the first v5 patch release, configure publishing from graphiql-5 with a maintenance tag such as v5, so it cannot replace v6 under latest.

The main CDN example continues using published RC packages until stable packages exist. Its stable URLs and integrity hashes are regenerated in #4675 after publication.

Supersedes #4587. Refs #4219.

@changeset-bot

changeset-bot Bot commented Sep 29, 2026 •

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: bf584a2

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes changesets to release 16 packages
Name Type
@graphiql/plugin-collections Major
@graphiql/react Major
graphiql Major
monaco-graphql Major
@graphiql/plugin-query-builder Major
@graphiql/toolkit Minor
@graphiql/plugin-doc-explorer Minor
@graphiql/plugin-history Patch
cm6-graphql Patch
codemirror-graphql Patch
@graphiql/plugin-code-exporter Patch
graphql-language-service-cli Patch
graphql-language-service-server Patch
graphql-language-service Patch
vscode-graphql-execution Patch
vscode-graphql Patch

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@trevor-scheer trevor-scheer changed the title Finish GraphiQL 6 examples and release references Prepare the stable GraphiQL 6 release Nov 1, 2026
@trevor-scheer
trevor-scheer marked this pull request as ready for review November 1, 2026 03:35
@trevor-scheer
trevor-scheer enabled auto-merge (squash) November 1, 2026 03:37
@trevor-scheer
trevor-scheer merged commit c2e792b into graphiql-6 Nov 1, 2026
13 checks passed
@trevor-scheer
trevor-scheer deleted the trevor/graphiql-6-final-cutover branch November 1, 2026 03:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant