May 08, 2024

@envelop/core@5.0.1

Patch Changes

• #2215
  dc1222f
  Thanks @benjie! - feat: add useValidationRule() plugin

@envelop/opentelemetry@6.3.1

Patch Changes

• #2218
  75b73fb
  Thanks @EmrysMyrddin! - dependencies updates:

  • Updated dependency
    @opentelemetry/api@^1.8.0 ↗︎
    (from ^1.0.0, in dependencies)

• Updated dependencies
  [dc1222f]:

  • @envelop/core@5.0.1

@envelop/prometheus@10.0.0

Major Changes

• #2217
  7ac1d3c
  Thanks @EmrysMyrddin! - Adds a cache for metrics definition
  (Summary, Histogram and Counter).

  Fixes an issue preventing this plugin to be initialized multiple times, leading to metrics
  duplication error (ardatan/graphql-mesh#6545).

  Behavior Breaking Change:

  Due to Prometheus client API limitations, a metric is only defined once for a given registry. This
  means that if the configuration of the metrics, it will be silently ignored on plugin
  re-initialization.

  This is to avoid potential loss of metrics data produced between the plugin re-initialization and
  the last pull by the prometheus agent.

  If you need to be sure metrics configuration is up to date after a plugin re-initialization, you
  can either:

  • restart the whole node process instead of just recreating a graphql server at runtime
  • clear the registry using registry.clear() before plugin re-initialization:

    function usePrometheusWithReset() {
      registry.clear()
      return usePrometheus({ ... })
    }

  • use a new registry for each plugin instance:

    function usePrometheusWithRegistry() {
      const registry = new Registry()
      return usePrometheus({
        registry,
        ...
      })
    }

  Keep in mind that this implies potential data loss in pull mode.

  API Breaking Change:

  To ensure metrics from being registered multiple times on the same registry, the signature of
  createHistogram, createSummary and createCounter have been changed to now include the
  registry as a mandatory parameter.

  If you were customizing metrics parameters, you will need to update the metric definitions

  usePrometheus({
    execute: createHistogram({
  +   registry: registry
      histogram: new Histogram({
        name: 'my_custom_name',
        help: 'HELP ME',
        labelNames: ['opText'] as const,
  -     registers: [registry],
      }),
      fillLabelsFn: () => {}
    }),
    requestCount: createCounter({
  +   registry: registry
      histogram: new Histogram({
        name: 'my_custom_name',
        help: 'HELP ME',
        labelNames: ['opText'] as const,
  -     registers: [registry],
      }),
      fillLabelsFn: () => {}
    }),
    requestSummary: createSummary({
  +   registry: registry
      histogram: new Histogram({
        name: 'my_custom_name',
        help: 'HELP ME',
        labelNames: ['opText'] as const,
  -     registers: [registry],
      }),
      fillLabelsFn: () => {}
    }),
  })

Patch Changes

• Updated dependencies
  [dc1222f]:
  • @envelop/core@5.0.1

April 02, 2024

@envelop/graphql-jit@8.0.3

Patch Changes

• #2188
  3a32aa9
  Thanks @renovate! - dependencies updates:

  • Updated dependency graphql-jit@0.8.6 ↗︎
    (from 0.8.5, in dependencies)

@envelop/opentelemetry@6.3.0

Minor Changes

• #2201
  396bccb
  Thanks @dotansimha! - feat: exclude operations by using list of
  names or a custom function

• #2201
  396bccb
  Thanks @dotansimha! - feat: allow to use a custom function to
  resolve/sanitize variables

@envelop/sentry@9.0.0

Major Changes

• #2163
  7686b33
  Thanks @MarcelCutts! - Removed includedResolverArgs from
  SentryPluginOptions as it lead to no functionality.

March 18, 2024

@envelop/graphql-jit@8.0.2

Patch Changes

• #2177
  dded74e
  Thanks @renovate! - dependencies updates:

  • Updated dependency graphql-jit@0.8.5 ↗︎
    (from 0.8.2, in dependencies)

March 13, 2024

@envelop/prometheus@9.4.0

Minor Changes

• 5667fc3
  Thanks @ardatan! - Ability to change the name of the labels

January 24, 2024

@envelop/prometheus@9.3.1

Patch Changes

• 3dc808b
  Thanks @ardatan! - Remove unwanted labels from metrics

January 18, 2024

@envelop/prometheus@9.3.0

Minor Changes

• 37d4dac
  Thanks @ardatan! - Support subscriptions

January 18, 2024

@envelop/prometheus@9.2.0

Minor Changes

• #2142
  4c11530
  Thanks @ardatan! - - Ability to hide operationName and operationType
  in the labels
  • Count schema changes
  • Catch errors during the context creation

January 18, 2024

@envelop/opentelemetry@6.2.1

Patch Changes

• 5c8a3a2
  Thanks @ardatan! - Ability to propagate otel context

January 18, 2024

@envelop/opentelemetry@6.2.0

Minor Changes

• #2139
  9b83224
  Thanks @ardatan! - Subscriptions support, expose trace id in the
  extensions

Patch Changes

• #2130
  6b29a6d
  Thanks @Akryum! - Able to add a prefix to the span

December 12, 2023

@envelop/sentry@8.0.0

Major Changes

• aff6ea0
  Thanks @EmrysMyrddin! - Allow to provide the context type as a
  generic parameter

  Breaking Change: Since this introduces a typed context as a generic, TS will not always infer
  the correct type for you. If you have a custom Context type, please consider explicitly pass this
  context type as a generic argument:

  cont yoga = createYoga<CustomContext>({
    plugins: [
      useSentry<CustomContext>({
        //...
      })
    ]
  })