Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Version Packages #3763

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Version Packages #3763

wants to merge 1 commit into from

Conversation

acao
Copy link
Member

@acao acao commented Sep 1, 2024

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 main, this PR will be updated.

Releases

[email protected]

Minor Changes

  • #3762 76b3cc8 Thanks @mavenskylab! - The cm6-graphql package currently specifies exact versions for its peer dependencies on @codemirror packages. This is causing conflicts when projects use newer versions of these packages, leading to multiple instances being installed.

  • #3782 6b88593 Thanks @acao! - officially deprecate graphql@15 support, as our types and other runtime capabilities ceased to be compatible in 2022 or 2023, but the regression tests were disabled
    graphql-language-service is where the bug is, which is used by all of the libraries and applications in graphiql monorepo.

Patch Changes

[email protected]

Minor Changes

  • #3782 6b88593 Thanks @acao! - officially deprecate graphql@15 support, as our types and other runtime capabilities ceased to be compatible in 2022 or 2023, but the regression tests were disabled
    graphql-language-service is where the bug is, which is used by all of the libraries and applications in graphiql monorepo.

Patch Changes

[email protected]

Minor Changes

  • #3782 6b88593 Thanks @acao! - officially deprecate graphql@15 support, as our types and other runtime capabilities ceased to be compatible in 2022 or 2023, but the regression tests were disabled
    graphql-language-service is where the bug is, which is used by all of the libraries and applications in graphiql monorepo.

Patch Changes

@graphiql/[email protected]

Minor Changes

  • #3782 6b88593 Thanks @acao! - officially deprecate graphql@15 support, as our types and other runtime capabilities ceased to be compatible in 2022 or 2023, but the regression tests were disabled
    graphql-language-service is where the bug is, which is used by all of the libraries and applications in graphiql monorepo.

Patch Changes

@graphiql/[email protected]

Minor Changes

  • #3782 6b88593 Thanks @acao! - officially deprecate graphql@15 support, as our types and other runtime capabilities ceased to be compatible in 2022 or 2023, but the regression tests were disabled
    graphql-language-service is where the bug is, which is used by all of the libraries and applications in graphiql monorepo.

Patch Changes

@graphiql/[email protected]

Minor Changes

  • #3782 6b88593 Thanks @acao! - officially deprecate graphql@15 support, as our types and other runtime capabilities ceased to be compatible in 2022 or 2023, but the regression tests were disabled
    graphql-language-service is where the bug is, which is used by all of the libraries and applications in graphiql monorepo.

Patch Changes

@graphiql/[email protected]

Minor Changes

  • #3782 6b88593 Thanks @acao! - officially deprecate graphql@15 support, as our types and other runtime capabilities ceased to be compatible in 2022 or 2023, but the regression tests were disabled
    graphql-language-service is where the bug is, which is used by all of the libraries and applications in graphiql monorepo.

Patch Changes

[email protected]

Minor Changes

  • #3782 6b88593 Thanks @acao! - officially deprecate graphql@15 support, as our types and other runtime capabilities ceased to be compatible in 2022 or 2023, but the regression tests were disabled
    graphql-language-service is where the bug is, which is used by all of the libraries and applications in graphiql monorepo.

Patch Changes

[email protected]

Minor Changes

  • #3782 6b88593 Thanks @acao! - officially deprecate graphql@15 support, as our types and other runtime capabilities ceased to be compatible in 2022 or 2023, but the regression tests were disabled
    graphql-language-service is where the bug is, which is used by all of the libraries and applications in graphiql monorepo.

Patch Changes

[email protected]

Minor Changes

  • #3782 6b88593 Thanks @acao! - officially deprecate graphql@15 support, as our types and other runtime capabilities ceased to be compatible in 2022 or 2023, but the regression tests were disabled
    graphql-language-service is where the bug is, which is used by all of the libraries and applications in graphiql monorepo.

Patch Changes

[email protected]

Minor Changes

  • #3782 6b88593 Thanks @acao! - officially deprecate graphql@15 support, as our types and other runtime capabilities ceased to be compatible in 2022 or 2023, but the regression tests were disabled
    graphql-language-service is where the bug is, which is used by all of the libraries and applications in graphiql monorepo.

Patch Changes

[email protected]

Patch Changes

[email protected]

Patch Changes

[email protected]

Patch Changes

Copy link
Contributor

github-actions bot commented Sep 1, 2024

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

@github-actions github-actions bot force-pushed the changeset-release/main branch 7 times, most recently from 6f56309 to fe16a60 Compare September 15, 2024 09:49
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