Skip to content

Version Packages (alpha)#4239

Closed
acao wants to merge 1 commit into
graphiql-6from
changeset-release/graphiql-6
Closed

Version Packages (alpha)#4239
acao wants to merge 1 commit into
graphiql-6from
changeset-release/graphiql-6

Conversation

@acao
Copy link
Copy Markdown
Member

@acao acao commented May 8, 2026

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to graphiql-6, this PR will be updated.

⚠️⚠️⚠️⚠️⚠️⚠️

graphiql-6 is currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, run changeset pre exit on graphiql-6.

⚠️⚠️⚠️⚠️⚠️⚠️

Releases

graphiql@6.0.0-alpha.0

Major Changes

Patch Changes

  • #4181 f1a210e Thanks @trevor-scheer! - Fix schema prop to skip introspection when IntrospectionQuery data is provided

    Previously, passing an IntrospectionQuery result as the schema prop would still trigger a network introspection request. The shouldIntrospect check only recognized GraphQLSchema instances (via isSchema), not raw introspection data. Now, when an IntrospectionQuery is passed, a schema is built from it directly using buildClientSchema and introspection is skipped.

  • #4211 e7b30c1 Thanks @davidjb! - Add *.css to sideEffects to allow import of CSS in Webpack Javascript

  • Updated dependencies [f1a210e, 6f5d5d2, 40359eb, 72e8970, e7b30c1]:

    • @graphiql/react@0.38.0-alpha.0
    • @graphiql/plugin-doc-explorer@0.4.2-alpha.0
    • @graphiql/plugin-history@0.4.2-alpha.0

@graphiql/react@0.38.0-alpha.0

Minor Changes

  • #4242 72e8970 Thanks @trevor-scheer! - Introduce the v6 OKLCH design-token system with both dark and light theme palettes. Tokens (--bg-canvas, --fg-default, --accent-blue, etc.) are stored as OKLCH triplets so opacity can be combined at the call site. Themes are keyed off data-theme (dark is the default; light activates explicitly or via prefers-color-scheme: light when no override is set). Existing v5 variables are unchanged; component styles continue to use them until they are migrated.

Patch Changes

  • #4181 f1a210e Thanks @trevor-scheer! - Fix schema prop to skip introspection when IntrospectionQuery data is provided

    Previously, passing an IntrospectionQuery result as the schema prop would still trigger a network introspection request. The shouldIntrospect check only recognized GraphQLSchema instances (via isSchema), not raw introspection data. Now, when an IntrospectionQuery is passed, a schema is built from it directly using buildClientSchema and introspection is skipped.

  • #4140 40359eb Thanks @trevor-scheer! - Remove react-compiler-runtime peer dependency

  • #4211 e7b30c1 Thanks @davidjb! - Add *.css to sideEffects to allow import of CSS in Webpack Javascript

  • Updated dependencies [914a547, 463df14, 4bb7909, 10f66d5]:

    • graphql-language-service@5.5.1-alpha.0
    • @graphiql/toolkit@0.12.0-alpha.0
    • monaco-graphql@1.7.4-alpha.0

@graphiql/toolkit@0.12.0-alpha.0

Minor Changes

  • #4199 463df14 Thanks @trevor-scheer! - Send spec-compliant Accept header (application/graphql-response+json) in createSimpleFetcher

cm6-graphql@0.2.2-alpha.0

Patch Changes

  • Updated dependencies [914a547, 10f66d5]:
    • graphql-language-service@5.5.1-alpha.0

codemirror-graphql@2.2.5-alpha.0

Patch Changes

  • Updated dependencies [914a547, 10f66d5]:
    • graphql-language-service@5.5.1-alpha.0

@graphiql/plugin-code-exporter@5.1.2-alpha.0

Patch Changes

@graphiql/plugin-doc-explorer@0.4.2-alpha.0

Patch Changes

  • #4231 6f5d5d2 Thanks @trevor-scheer! - Fix degraded type declarations in published packages

    Both packages import from @graphiql/react at build time but only declared it as a peer dependency. Yarn workspaces topologically orders builds via dependencies/devDependencies, not peerDependencies, so on a clean checkout these plugins built before @graphiql/react had emitted its dist/*.d.ts. vite-plugin-dts then ran tsc against unresolved @graphiql/react imports, fell back to any for any return type that flowed through useGraphiQL, and published .d.ts artifacts where hooks like useDocExplorer and useDocExplorerActions resolved to () => any instead of their real shapes.

    Adding @graphiql/react as a devDependency matches the pattern already in @graphiql/plugin-explorer and @graphiql/plugin-code-exporter and lets the build run in topological order.

  • #4140 40359eb Thanks @trevor-scheer! - Remove react-compiler-runtime peer dependency

  • #4211 e7b30c1 Thanks @davidjb! - Add *.css to sideEffects to allow import of CSS in Webpack Javascript

  • Updated dependencies [f1a210e, 40359eb, 72e8970, e7b30c1]:

    • @graphiql/react@0.38.0-alpha.0

@graphiql/plugin-explorer@5.1.2-alpha.0

Patch Changes

@graphiql/plugin-history@0.4.2-alpha.0

Patch Changes

  • #4231 6f5d5d2 Thanks @trevor-scheer! - Fix degraded type declarations in published packages

    Both packages import from @graphiql/react at build time but only declared it as a peer dependency. Yarn workspaces topologically orders builds via dependencies/devDependencies, not peerDependencies, so on a clean checkout these plugins built before @graphiql/react had emitted its dist/*.d.ts. vite-plugin-dts then ran tsc against unresolved @graphiql/react imports, fell back to any for any return type that flowed through useGraphiQL, and published .d.ts artifacts where hooks like useDocExplorer and useDocExplorerActions resolved to () => any instead of their real shapes.

    Adding @graphiql/react as a devDependency matches the pattern already in @graphiql/plugin-explorer and @graphiql/plugin-code-exporter and lets the build run in topological order.

  • #4140 40359eb Thanks @trevor-scheer! - Remove react-compiler-runtime peer dependency

  • #4211 e7b30c1 Thanks @davidjb! - Add *.css to sideEffects to allow import of CSS in Webpack Javascript

  • Updated dependencies [463df14, f1a210e, 40359eb, 72e8970, e7b30c1]:

    • @graphiql/toolkit@0.12.0-alpha.0
    • @graphiql/react@0.38.0-alpha.0

graphql-language-service@5.5.1-alpha.0

Patch Changes

graphql-language-service-cli@3.5.1-alpha.0

Patch Changes

  • Updated dependencies [ca83879, 914a547, 10f66d5]:
    • graphql-language-service-server@2.14.9-alpha.0
    • graphql-language-service@5.5.1-alpha.0

graphql-language-service-server@2.14.9-alpha.0

Patch Changes

  • #4187 ca83879 Thanks @trevor-scheer! - Bump required TypeScript runtime dependency from ^5.3.3 to ^5.8.0. This is preparatory work for adopting the TypeScript Native Preview (tsgo) compiler in a follow-up change, which tracks TypeScript 5.8 semantics. In practice ^5.3.3 already resolved to TS 5.8+ for most consumers; the new floor only affects consumers who pin TypeScript to 5.3–5.7 via resolutions or overrides.

  • #4222 10f66d5 Thanks @trevor-scheer! - Unpin and update graphql-config dependency

  • Updated dependencies [914a547, 10f66d5]:

    • graphql-language-service@5.5.1-alpha.0

monaco-graphql@1.7.4-alpha.0

Patch Changes

  • #4225 4bb7909 Thanks @trevor-scheer! - Fix hover crashing on the first line of a query

    GraphQLWorker.doHover was passing 0-indexed positions to getRange, which expects a 1-indexed SourceLocation (per the GraphQL spec). On the first line this caused Expected Parser stream to be available to be logged and hover to return null. On other lines it returned the range of the previous line's last token rather than the token under the cursor. Use getTokenAtPosition to compute the actual token range instead.

  • Updated dependencies [914a547, 10f66d5]:

    • graphql-language-service@5.5.1-alpha.0

vscode-graphql@0.13.3-alpha.0

Patch Changes

vscode-graphql-execution@0.3.3-alpha.0

Patch Changes

vscode-graphql-syntax@1.3.9-alpha.0

Patch Changes

  • #4183 2ef9389 Thanks @trevor-scheer! - Fix VS Code extension publishing scripts

  • #4143 7979bf5 Thanks @Netail! - Add syntax highlighting support for subscription operations.

  • #4144 f7e2a56 Thanks @jsmnbom! - Add text.html.vue as inline injection target.

    This PR broke tooling by changing the vue grammar scope from source.vue to text.html.vue. This adds text.html.vue as an additional injection target for GraphQL syntax highlighting so that it works in both cases.

@github-actions github-actions Bot force-pushed the changeset-release/graphiql-6 branch from 592aacf to 229c7fd Compare May 8, 2026 23:14
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 8, 2026

The latest changes of this PR are not available as canary, since there are no linked changesets for this PR.

trevor-scheer added a commit that referenced this pull request May 9, 2026
## Summary

Three stacked bugs have made `yarn license-check` a near-no-op, and the
alpha-release PR (#4239) recently surfaced one of them:

1. **`jsgl --local packages/*` was only ever checking one package.** The
shell expands the glob, but `--local` is a `string` flag, so only the
first arg (`packages/cm6-graphql`) is honored — every other workspace
package is silently ignored. Switched to `jsgl --local .` so
`js-green-licenses` walks the root + every `packages/*/package.json`
itself, and registers them all as local.

2. **`js-green-licenses` has a regex bug** at `checker.js:232`:
    ```js
const version = versionSpec.replace(/^[^~]/, ''); // [^~] = "not tilde"
    ```
It's meant to strip a leading `^` so the local-package short-circuit at
line 234 can match, but `[^~]` matches any first non-tilde char — so a
pinned `5.5.1-alpha.0` becomes `.5.1-alpha.0` and the lookup misses.
Patched via `patch-package`: `/^[^~]/` → `/^[~^]/`. This is the same fix
as the (forever-unmerged) upstream PR
[google/js-green-licenses#230](google/js-green-licenses#230).

3. **Seven previously-hidden findings surface** once `--local .`
actually walks the tree — all permissive in practice. Allowlisted them
in `js-green-licenses.json`:
- `BlueOak-1.0.0` (permissive, but not in jsgl's default green list):
`glob`, `minimatch`, `minipass`, `path-scurry`, `lru-cache`
   - non-SPDX-in-manifest MIT: `spawn-command`, `spawndamnit`

Without this, alpha release PRs (and eventually any main release that
bumps a cross-workspace dep) fail `Check Licenses` because the bumped
workspace deps aren't on npm yet and the local-skip was misfiring.

`google/js-green-licenses` is archived, so a follow-up to replace it
with a maintained tool will land separately.

## Test plan

- [x] Reproduced the original `VersionNotFoundError` locally on
`changeset-release/graphiql-6` HEAD
- [x] After the fix, `yarn license-check` exits 0 on both
`changeset-release/graphiql-6` (alpha state, includes
`graphql-language-service@5.5.1-alpha.0`) and `main`
- [x] `yarn format-check` passes
- [ ] CI green
@github-actions github-actions Bot force-pushed the changeset-release/graphiql-6 branch from 229c7fd to 544a2d1 Compare May 9, 2026 01:43
@github-actions github-actions Bot force-pushed the changeset-release/graphiql-6 branch from 544a2d1 to 5caf875 Compare May 9, 2026 02:39
@benjie benjie closed this May 11, 2026
@benjie benjie reopened this May 11, 2026
@benjie benjie closed this May 11, 2026
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.

2 participants