Skip to content

Upcoming Release Changes #2786

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.

Sign up for GitHub

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

Jump to bottom
Open
github-actions wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Upcoming Release Changes #2786

github-actions wants to merge 1 commit into from

Conversation

@github-actions
Copy link
Contributor

@github-actions github-actions bot commented Nov 26, 2025 •
edited
Loading

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

@envelop/[email protected]

Major Changes

  • #1323
    cecd3f6
    Thanks @ardatan! - Rate Limiter no longer gets attached to the
    resolvers and use onExecute hook instead. This improves performance by reducing the number of
    function calls, and issues with multiple plugins trying to wrap the same resolver.

    onRateLimitError no longer receives info object, but receives type and field instead.
    interpolateMessage also receives type and field instead of info.

    onRateLimitError({
    error: string;
    identifier: string;
    context: unknown;
-   info: GraphQLResolveInfo;
+   type: GraphQLNamedOutputType;
+   field: GraphQLField<any, any>;
})
    interpolateMessage(
    message: string,
    identifier: string,
    params: {
        root: unknown;
        args: Record<string, unknown>;
        context: unknown;
-       info: GraphQLResolveInfo;
+       type: GraphQLNamedOutputType;
+       field: GraphQLField<any, any>;
    }
): string

Patch Changes

@envelop/[email protected]

Minor Changes

@envelop/[email protected]

Minor Changes

  • #2747
    49346b2
    Thanks @cecchi! - Add option to ignore default resolvers in
    opentelemetry instrumentation

    To reduce telemetry data volume and noise in traces, it is recommended to ignore resolvers with
    the default implementation since they probably doesn't do anything worth tracking.

    Usage

    import { execute, parse, specifiedRules, subscribe, validate } from 'graphql'
import { envelop, useEngine } from '@envelop/core'
import { useOpenTelemetry } from '@envelop/opentelemetry'

const getEnveloped = envelop({
  plugins: [
    useEngine({ parse, validate, specifiedRules, execute, subscribe }),
    // ... other plugins ...

    useOpenTelemetry({
      resolvers: true,
      defaultResolvers: false // explicitly disable default resolvers tracing. Defaults to `true`
    })
  ]
})

Patch Changes

@envelop/[email protected]

Minor Changes

  • #2747
    49346b2
    Thanks @cecchi! - Add option to ignore default resolvers in
    opentelemetry instrumentation

    To reduce telemetry data volume and noise in traces, it is recommended to ignore resolvers with
    the default implementation since they probably doesn't do anything worth tracking.

    Usage

    import { execute, parse, specifiedRules, subscribe, validate } from 'graphql'
import { envelop, useEngine } from '@envelop/core'
import { useOpenTelemetry } from '@envelop/opentelemetry'

const getEnveloped = envelop({
  plugins: [
    useEngine({ parse, validate, specifiedRules, execute, subscribe }),
    // ... other plugins ...

    useOpenTelemetry({
      resolvers: true,
      defaultResolvers: false // explicitly disable default resolvers tracing. Defaults to `true`
    })
  ]
})

Patch Changes

@envelop/[email protected]

Patch Changes

@envelop/[email protected]

Patch Changes

@envelop/[email protected]

Patch Changes

@envelop/[email protected]

Patch Changes

@envelop/[email protected]

Patch Changes

@envelop/[email protected]

Patch Changes

@envelop/[email protected]

Patch Changes

@envelop/[email protected]

Patch Changes

@envelop/[email protected]

Patch Changes

@envelop/[email protected]

Patch Changes

@envelop/[email protected]

Patch Changes

@envelop/[email protected]

Patch Changes

@envelop/[email protected]

Patch Changes

@envelop/[email protected]

Patch Changes

@envelop/[email protected]

Patch Changes

@envelop/[email protected]

Patch Changes

@envelop/[email protected]

Patch Changes

@envelop/[email protected]

Patch Changes

@envelop/[email protected]

Patch Changes

@envelop/[email protected]

Patch Changes

@envelop/[email protected]

Patch Changes

@envelop/[email protected]

Patch Changes

@envelop/[email protected]

Patch Changes

@envelop/[email protected]

Patch Changes

@envelop/[email protected]

Patch Changes

@envelop/[email protected]

Patch Changes

@envelop/[email protected]

Patch Changes

@envelop/[email protected]

Patch Changes

@envelop/[email protected]

Patch Changes

@envelop/[email protected]

Patch Changes

@envelop/[email protected]

Patch Changes

@envelop/[email protected]

Patch Changes

@github-actions github-actions bot force-pushed the changeset-release/main branch 6 times, most recently from 5979a7f to b1ad63c Compare December 2, 2025 18:29
@github-actions github-actions bot force-pushed the changeset-release/main branch 6 times, most recently from 6686457 to 912cfb0 Compare December 8, 2025 17:00
@github-actions github-actions bot force-pushed the changeset-release/main branch 16 times, most recently from 3e0f016 to a7e8ae3 Compare December 16, 2025 01:19
@github-actions github-actions bot force-pushed the changeset-release/main branch from a7e8ae3 to dd5b7b4 Compare December 16, 2025 01:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants