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

Upcoming Release Changes #6798

Merged
merged 1 commit into from
Dec 24, 2024
Merged

Upcoming Release Changes #6798

merged 1 commit into from
Dec 24, 2024

Conversation

theguild-bot
Copy link
Collaborator

@theguild-bot theguild-bot commented Dec 24, 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 master, this PR will be updated.

Releases

@graphql-tools/[email protected]

Minor Changes

  • #6789
    2c70d27
    Thanks @n1ru4l! - - New helper function getAbortPromise to get a
    promise rejected when AbortSignal is aborted

    • New helper function registerAbortSignalListener to register a listener to abort a promise when
      AbortSignal is aborted

    Instead of using .addEventListener('abort', () => {/* ... */}), we register a single listener to
    avoid warnings on Node.js like
    MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 abort listeners added. Use emitter.setMaxListeners() to increase limit.

@graphql-tools/[email protected]

Patch Changes

  • #6789
    2c70d27
    Thanks @n1ru4l! - Surpress the "possible EventEmitter memory leak
    detected." warning occuring on Node.js when passing a AbortSignal to execute.

    Each execution will now only set up a single listener on the supplied AbortSignal. While the
    warning is harmless it can be misleading, which is the main motivation of this change.

  • Updated dependencies
    [2c70d27]:

@graphql-tools/[email protected]

Patch Changes

@graphql-tools/[email protected]

Patch Changes

@graphql-tools/[email protected]

Patch Changes

@graphql-tools/[email protected]

Patch Changes

@graphql-tools/[email protected]

Patch Changes

@graphql-tools/[email protected]

Patch Changes

[email protected]

Patch Changes

@graphql-tools/[email protected]

Patch Changes

  • #6796
    ddfef2c
    Thanks @ardatan! - Avoid importing process and use it from
    globalThis. In some cases, cwd is not exported with this name in the environment in ESM scope.
  • Updated dependencies
    [2c70d27]:

@graphql-tools/[email protected]

Patch Changes

@graphql-tools/[email protected]

Patch Changes

@graphql-tools/[email protected]

Patch Changes

@graphql-tools/[email protected]

Patch Changes

@graphql-tools/[email protected]

Patch Changes

@graphql-tools/[email protected]

Patch Changes

@graphql-tools/[email protected]

Patch Changes

@graphql-tools/[email protected]

Patch Changes

@graphql-tools/[email protected]

Patch Changes

@graphql-tools/[email protected]

Patch Changes

@graphql-tools/[email protected]

Patch Changes

@graphql-tools/[email protected]

Patch Changes

@graphql-tools/[email protected]

Patch Changes

@graphql-tools/[email protected]

Patch Changes

@graphql-tools/[email protected]

Patch Changes

@graphql-tools/[email protected]

Patch Changes

@theguild-bot theguild-bot force-pushed the changeset-release/master branch from c28bb76 to 226a9e4 Compare December 24, 2024 12:00
@ardatan ardatan merged commit 8e15907 into master Dec 24, 2024
13 checks passed
@ardatan ardatan deleted the changeset-release/master branch December 24, 2024 12:02
Copy link
Contributor

github-actions bot commented Dec 24, 2024

💻 Website Preview

The latest changes are available as preview in: https://d1c2ac9a.graphql-tools.pages.dev

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