chore(deps): update envelop (major) by renovate[bot] · Pull Request #813 · Escape-Technologies/graphql-armor

renovate · 2025-06-23T22:52:28Z

This PR contains the following updates:

Package	Change	Age	Confidence
@envelop/core (source)	`^5.2.3` → `^6.0.0`
@envelop/core (source)	`5.2.3` → `6.0.0`
@envelop/core (source)	`^5.0.0` → `^6.0.0`
@envelop/testing (source)	`8.1.3` → `11.0.0`
@envelop/types (source)	`5.2.1` → `6.0.0`

Release Notes

graphql-hive/graphql-yoga (@envelop/core)

`v6.0.0`

Compare Source

Major Changes

#4574
79b0e8b
Thanks @egoodwinx! - ### Breaking Changes
- Node: minimum supported version is now Node 22. Node 18 and 20 are no longer supported.
  Future releases will only support Node >=22.
- GraphQL: minimum supported version is now GraphQL 16. GraphQL 14 and 15 are no longer
  supported.
- Request body parsing: Yoga now limits request bodies to 25,000,000 bytes by default.
  Enforcing this limit streams the body through a byte counter, making POST body parsing
  asynchronous even for an in-memory body. As a result, yoga.fetch() can return a Promise where
  it previously returned a synchronous Response, even when all resolvers and plugins are
  synchronous.

Migration

If you're on Node 18/20, upgrade to Node 22 or later before upgrading this package.
If you're on graphql 14/15, upgrade to graphql 16 or 17 first.
Await yoga.fetch() and response body parsing instead of relying on synchronous results. Set
maxRequestBodySize: false in createYoga to disable the body-size limit and preserve
synchronous parsing for in-memory bodies, but only if you enforce an appropriate request-body
limit elsewhere.
#4623
be89d05
Thanks @ardatan! - ### Dependencies
- Bump @graphql-tools/utils to ^13.1.1, @graphql-tools/schema to ^11.0.0, and
  @graphql-tools/executor to ^4.1.2.

Incremental delivery

Yoga maps the GraphQL HTTP Accept header through INCREMENTAL_DELIVERY_SPECS from
@graphql-tools/utils onto executor incrementalSpec. multipart/mixed;incrementalSpec=v0.2
runs the v0.2 payload format and echoes that spec on Content-Type.
multipart/mixed;deferSpec=20220824 or bare multipart/mixed stays on v0.1. An unsupported
incremental spec yields 406.

A later incremental spec is a graphql-tools table row plus an executor publisher. Yoga, Hive
Gateway, and HTTP executors pick it up by bumping @graphql-tools/utils /
@graphql-tools/executor.

Breaking Changes

createGraphQLError is removed. Use new GraphQLError(message, options) from graphql. To
attach Yoga's experimental schema coordinate, use withSchemaCoordinate(error, coordinate) and
read with getSchemaCoordinate from @graphql-tools/utils.
mapMaybePromise is removed (was exported from Yoga / @envelop/core). Use
handleMaybePromise from @whatwg-node/promise-helpers.
Yoga no longer re-exports helpers that already live upstream:
- getSchemaCoordinate -> @graphql-tools/utils
- mergeSchemas -> @graphql-tools/schema
- DisposableSymbols -> @whatwg-node/server
- mapAsyncIterator / isPromise / fakePromise / handleMaybePromise / MaybePromise ->
  @whatwg-node/promise-helpers
@envelop/core utils no longer re-exports mapAsyncIterator or isPromise. Import from
@whatwg-node/promise-helpers.
Use asGetArgumentValuesVariables / coerceGetVariableValuesResult from @graphql-tools/utils
for GraphQL 16/17 VariableValues compatibility.

Migration

import { GraphQLError } from 'graphql'
import { withSchemaCoordinate } from 'graphql-yoga'
import { mergeSchemas } from '@graphql-tools/schema'
import { getSchemaCoordinate } from '@graphql-tools/utils'
import { handleMaybePromise, isPromise, type MaybePromise } from '@whatwg-node/promise-helpers'
import { DisposableSymbols } from '@whatwg-node/server'

throw withSchemaCoordinate(new GraphQLError('not found'), 'Query.user')

#4574
79b0e8b
Thanks @egoodwinx! - ### Dependencies
- Bump @whatwg-node/server to ^0.13.0, @whatwg-node/fetch to ^0.12.0, and
  @whatwg-node/promise-helpers to ^2.0.0.
- Delegate to @whatwg-node/server's useLimitRequestBodySize instead of a hand-rolled byte counter,
  and swap in the native TransformStream when the incoming request already has a native
  ReadableStream body — piping it through the ponyfill TransformStream throws since they're
  different realms. Thread an optional fetchAPI param through handle/parseRequest/
  getResultForParams so callers can override which fetchAPI (native vs ponyfill) the rest of the
  pipeline uses.
- Unread request bodies are discarded after the response is decided (keep-alive friendly).
- Incoming global Request instances automatically use the native Fetch API
  (pickRightFetchAPI), so Next.js no longer needs fetchAPI: { Response }.

Breaking Changes

engines.node is now >=22.15.0 (aligned with whatwg-node 0.12+/0.13).
@envelop/core no longer exports mapMaybePromise (removed upstream in
@whatwg-node/promise-helpers v2). Use handleMaybePromise(() => value, ...) instead.
@whatwg-node/fetch no longer exports crypto; use the platform crypto global. TextEncoder
still comes from fetchAPI where hashing goes through Yoga’s FetchAPI.

Minor Changes

#4575
862447a
Thanks @egoodwinx! - Use
@graphql-hive/logger and add correlated, per-request
logging (closes #4048)

Every request now gets its own logger, available as context.log (and serverContext.log in
plugin hooks), tagged with a requestId. Everything logged while handling a request can be
correlated by that id.

The request id is taken from the host integration if it already assigned one (e.g. Fastify's
request.id), otherwise from the incoming x-request-id header, otherwise generated. It is also
sent back in the x-request-id response header. Configure it with the new requestId option:
```
createYoga({
  requestId: {
    // don't trust the incoming header, recommended when clients can reach the server directly
    trustHeader: false,
    headerName: 'x-correlation-id',
    generateRequestId: () => myId()
  }
})
```
Pass requestId: false to disable it.

At the info level, a single "Request processed" line is logged per request with the method,
path, operation name and type, response status, error count and duration. At the debug level,
more details about request processing are logged.

Masked errors are now logged with the request's logger, so they can be traced back to the request
that caused them. Custom maskError functions receive the request's context as an optional fourth
argument.

The @envelop/newrelic, @envelop/auth0, @envelop/resource-limitations, @envelop/statsd,
@envelop/graphql-jit, @envelop/response-cache and @envelop/response-cache-cloudflare-kv
plugins accept a new log option for their own messages, instead of always writing to the
console.

@envelop/response-cache's shouldCacheResult now also receives the GraphQL context.

Breaking Changes

The @graphql-yoga/logger package has been removed. graphql-yoga re-exports Logger,
MemoryLogWriter and LogLevel from @graphql-hive/logger instead.
createLogger and the YogaLogger type are no longer exported. Use new Logger(options)
instead.
The logging option now takes boolean | Logger | LogLevel, where Logger is the one from
@graphql-hive/logger.
yoga.logger has been renamed to yoga.log.
The logger option of useGraphiQL and useHealthCheck has been removed. They now log through
the request's logger.
@graphql-yoga/nestjs now logs through Nest's Logger by default instead of not logging at
all. Pass logging: false to keep the previous behaviour. logging: true on Fastify no longer
logs through Fastify's logger, pass it explicitly instead (see below).
@envelop/apollo-federation, @envelop/auth0, @envelop/graphql-jit, @envelop/newrelic,
@envelop/resource-limitations, @envelop/response-cache,
@envelop/response-cache-cloudflare-kv and @envelop/statsd now have a peer dependency on
@graphql-hive/logger that you must install.
@envelop/apollo-federation's logger option now expects a Logger from
@graphql-hive/logger and defaults to new Logger() instead of console.

Migration

Create loggers with Logger:

- import { createLogger } from 'graphql-yoga';
+ import { Logger } from 'graphql-yoga';

  createYoga({
-   logging: createLogger('debug'),
+   logging: new Logger({ level: 'debug' }),
  });

Use log instead of logger on the Yoga instance:

  const plugin = {
    onYogaInit({ yoga }) {
-     yoga.logger.info('ready');
+     yoga.log.info('ready');
    },
  };

Prefer the request-scoped logger inside resolvers and plugin hooks so the logs carry the request
id:

const resolvers = {
  Query: {
    hello: (_, __, context) => {
      context.log.debug('resolving hello')
      return 'world'
    }
  }
}

If you use any of the @envelop/* plugins listed above, install the logger:

npm i @graphql-hive/logger

If you depended on @graphql-yoga/logger directly, switch to @graphql-hive/logger:

- import { Logger } from '@graphql-yoga/logger';
+ import { Logger } from '@graphql-hive/logger';

To keep logging through Fastify's logger in @graphql-yoga/nestjs:

import { Logger } from 'graphql-yoga'
import { PinoLogWriter } from '@graphql-hive/logger/writers/pino'

// in your yoga driver options
logging: new Logger({ writers: [new PinoLogWriter(app.log)] })

Patch Changes

Updated dependencies
[862447a,
79b0e8b]:
- @envelop/types@6.0.0
- @envelop/instrumentation@2.0.0

`v5.6.1`

Compare Source

Patch Changes

#4577
7bff35c
Thanks @egoodwinx! - Add homepage and bugs.url to package.json
files
Updated dependencies
[7bff35c]:
- @envelop/instrumentation@1.0.1
- @envelop/types@5.2.2

`v5.6.0`

Minor Changes

#4545
94ebe5b
Thanks @egoodwinx! - Update to support graphql-js 17

Bump package versions, fix expected typing, and update compatability with subscribe.

`v5.5.1`

Patch Changes

#2868
0bfde27
Thanks @n1ru4l! - Pass latest mergable context to useErrorHandler
hook when the error originates from a context extension.

`v5.5.0`

Minor Changes

#2113
d3d83bc
Thanks @andrew0! - Handle incremental execution errors in
useErrorHandler

`v5.4.0`

Minor Changes

0434fbd
Thanks @ardatan! - Export documentStringMap to set a value for
getDocumentString externally

`v5.3.2`

Patch Changes

#2665
92948d8
Thanks @EmrysMyrddin! - Fix getters and setters being stripped
away. The value was copied at plugin creation instead of copying the getter and setter (if any).

`v5.3.1`

Patch Changes

#2611
8dd5bda
Thanks @EmrysMyrddin! - Add a withState override to ease the
typing of plugins whith the same state for all scopes.

`v5.3.0`

Minor Changes

#2607
3ebaa3b
Thanks @EmrysMyrddin! - Added new withState plugin utility
for easy data sharing between hooks.

graphql-hive/graphql-yoga (@envelop/testing)

`v11.0.0`

Compare Source

Major Changes

#4574
79b0e8b
Thanks @egoodwinx! - ### Breaking Changes
- Node: minimum supported version is now Node 22. Node 18 and 20 are no longer supported.
  Future releases will only support Node >=22.
- GraphQL: minimum supported version is now GraphQL 16. GraphQL 14 and 15 are no longer
  supported.
- Request body parsing: Yoga now limits request bodies to 25,000,000 bytes by default.
  Enforcing this limit streams the body through a byte counter, making POST body parsing
  asynchronous even for an in-memory body. As a result, yoga.fetch() can return a Promise where
  it previously returned a synchronous Response, even when all resolvers and plugins are
  synchronous.

Migration

If you're on Node 18/20, upgrade to Node 22 or later before upgrading this package.
If you're on graphql 14/15, upgrade to graphql 16 or 17 first.
Await yoga.fetch() and response body parsing instead of relying on synchronous results. Set
maxRequestBodySize: false in createYoga to disable the body-size limit and preserve
synchronous parsing for in-memory bodies, but only if you enforce an appropriate request-body
limit elsewhere.
#4623
be89d05
Thanks @ardatan! - ### Dependencies
- Bump @graphql-tools/utils to ^13.1.1, @graphql-tools/schema to ^11.0.0, and
  @graphql-tools/executor to ^4.1.2.

Incremental delivery

Yoga maps the GraphQL HTTP Accept header through INCREMENTAL_DELIVERY_SPECS from
@graphql-tools/utils onto executor incrementalSpec. multipart/mixed;incrementalSpec=v0.2
runs the v0.2 payload format and echoes that spec on Content-Type.
multipart/mixed;deferSpec=20220824 or bare multipart/mixed stays on v0.1. An unsupported
incremental spec yields 406.

A later incremental spec is a graphql-tools table row plus an executor publisher. Yoga, Hive
Gateway, and HTTP executors pick it up by bumping @graphql-tools/utils /
@graphql-tools/executor.

Breaking Changes

createGraphQLError is removed. Use new GraphQLError(message, options) from graphql. To
attach Yoga's experimental schema coordinate, use withSchemaCoordinate(error, coordinate) and
read with getSchemaCoordinate from @graphql-tools/utils.
mapMaybePromise is removed (was exported from Yoga / @envelop/core). Use
handleMaybePromise from @whatwg-node/promise-helpers.
Yoga no longer re-exports helpers that already live upstream:
- getSchemaCoordinate -> @graphql-tools/utils
- mergeSchemas -> @graphql-tools/schema
- DisposableSymbols -> @whatwg-node/server
- mapAsyncIterator / isPromise / fakePromise / handleMaybePromise / MaybePromise ->
  @whatwg-node/promise-helpers
@envelop/core utils no longer re-exports mapAsyncIterator or isPromise. Import from
@whatwg-node/promise-helpers.
Use asGetArgumentValuesVariables / coerceGetVariableValuesResult from @graphql-tools/utils
for GraphQL 16/17 VariableValues compatibility.

Migration

import { GraphQLError } from 'graphql'
import { withSchemaCoordinate } from 'graphql-yoga'
import { mergeSchemas } from '@graphql-tools/schema'
import { getSchemaCoordinate } from '@graphql-tools/utils'
import { handleMaybePromise, isPromise, type MaybePromise } from '@whatwg-node/promise-helpers'
import { DisposableSymbols } from '@whatwg-node/server'

throw withSchemaCoordinate(new GraphQLError('not found'), 'Query.user')

Patch Changes

Updated dependencies
[862447a,
79b0e8b,
be89d05,
79b0e8b]:
- @envelop/core@6.0.0
- @envelop/types@6.0.0

`v10.2.3`

Compare Source

Patch Changes

#4607
d8b8860
Thanks @enisdenjo! - dependencies updates:
- Updated dependency
  @graphql-tools/utils@^12.0.3 ↗︎
  (from ^11.2.2, in dependencies)

`v10.2.2`

Compare Source

Patch Changes

#4604
c6febdc
Thanks @enisdenjo! - dependencies updates:
- Updated dependency
  @graphql-tools/utils@^11.2.2 ↗︎
  (from ^11.2.0, in dependencies)

`v10.2.1`

Compare Source

Patch Changes

#4577
7bff35c
Thanks @egoodwinx! - Add homepage and bugs.url to package.json
files
Updated dependencies
[7bff35c]:
- @envelop/types@5.2.2
- @envelop/core@5.6.1

`v10.2.0`

Minor Changes

#4545
94ebe5b
Thanks @egoodwinx! - Update to support graphql-js 17

Bump package versions, fix expected typing, and update compatability with subscribe.

Patch Changes

Updated dependencies
[94ebe5b]:
- @envelop/core@5.6.0

`v10.1.1`

Patch Changes

Updated dependencies
[0bfde27]:
- @envelop/core@5.5.1

`v10.1.0`

Patch Changes

#2827
dc2327d
Thanks @renovate! - dependencies updates:
- Updated dependency
  @graphql-tools/utils@^11.0.0 ↗︎
  (from ^10.0.0, in dependencies)
Updated dependencies
[d3d83bc]:
- @envelop/core@5.5.0

`v10.0.0`

Patch Changes

Updated dependencies
[0434fbd]:
- @envelop/core@5.4.0

`v9.0.0`

Patch Changes

Updated dependencies
[3ebaa3b]:
- @envelop/core@5.3.0

graphql-hive/graphql-yoga (@envelop/types)

`v6.0.0`

Compare Source

Major Changes

#4574
79b0e8b
Thanks @egoodwinx! - ### Breaking Changes
- Node: minimum supported version is now Node 22. Node 18 and 20 are no longer supported.
  Future releases will only support Node >=22.
- GraphQL: minimum supported version is now GraphQL 16. GraphQL 14 and 15 are no longer
  supported.
- Request body parsing: Yoga now limits request bodies to 25,000,000 bytes by default.
  Enforcing this limit streams the body through a byte counter, making POST body parsing
  asynchronous even for an in-memory body. As a result, yoga.fetch() can return a Promise where
  it previously returned a synchronous Response, even when all resolvers and plugins are
  synchronous.

Migration

If you're on Node 18/20, upgrade to Node 22 or later before upgrading this package.
If you're on graphql 14/15, upgrade to graphql 16 or 17 first.
Await yoga.fetch() and response body parsing instead of relying on synchronous results. Set
maxRequestBodySize: false in createYoga to disable the body-size limit and preserve
synchronous parsing for in-memory bodies, but only if you enforce an appropriate request-body
limit elsewhere.

Minor Changes

#4575
862447a
Thanks @egoodwinx! - Use
@graphql-hive/logger and add correlated, per-request
logging (closes #4048)

Every request now gets its own logger, available as context.log (and serverContext.log in
plugin hooks), tagged with a requestId. Everything logged while handling a request can be
correlated by that id.

The request id is taken from the host integration if it already assigned one (e.g. Fastify's
request.id), otherwise from the incoming x-request-id header, otherwise generated. It is also
sent back in the x-request-id response header. Configure it with the new requestId option:
```
createYoga({
  requestId: {
    // don't trust the incoming header, recommended when clients can reach the server directly
    trustHeader: false,
    headerName: 'x-correlation-id',
    generateRequestId: () => myId()
  }
})
```
Pass requestId: false to disable it.

At the info level, a single "Request processed" line is logged per request with the method,
path, operation name and type, response status, error count and duration. At the debug level,
more details about request processing are logged.

Masked errors are now logged with the request's logger, so they can be traced back to the request
that caused them. Custom maskError functions receive the request's context as an optional fourth
argument.

The @envelop/newrelic, @envelop/auth0, @envelop/resource-limitations, @envelop/statsd,
@envelop/graphql-jit, @envelop/response-cache and @envelop/response-cache-cloudflare-kv
plugins accept a new log option for their own messages, instead of always writing to the
console.

@envelop/response-cache's shouldCacheResult now also receives the GraphQL context.

Breaking Changes

The @graphql-yoga/logger package has been removed. graphql-yoga re-exports Logger,
MemoryLogWriter and LogLevel from @graphql-hive/logger instead.
createLogger and the YogaLogger type are no longer exported. Use new Logger(options)
instead.
The logging option now takes boolean | Logger | LogLevel, where Logger is the one from
@graphql-hive/logger.
yoga.logger has been renamed to yoga.log.
The logger option of useGraphiQL and useHealthCheck has been removed. They now log through
the request's logger.
@graphql-yoga/nestjs now logs through Nest's Logger by default instead of not logging at
all. Pass logging: false to keep the previous behaviour. logging: true on Fastify no longer
logs through Fastify's logger, pass it explicitly instead (see below).
@envelop/apollo-federation, @envelop/auth0, @envelop/graphql-jit, @envelop/newrelic,
@envelop/resource-limitations, @envelop/response-cache,
@envelop/response-cache-cloudflare-kv and @envelop/statsd now have a peer dependency on
@graphql-hive/logger that you must install.
@envelop/apollo-federation's logger option now expects a Logger from
@graphql-hive/logger and defaults to new Logger() instead of console.

Migration

Create loggers with Logger:

- import { createLogger } from 'graphql-yoga';
+ import { Logger } from 'graphql-yoga';

  createYoga({
-   logging: createLogger('debug'),
+   logging: new Logger({ level: 'debug' }),
  });

Use log instead of logger on the Yoga instance:

  const plugin = {
    onYogaInit({ yoga }) {
-     yoga.logger.info('ready');
+     yoga.log.info('ready');
    },
  };

Prefer the request-scoped logger inside resolvers and plugin hooks so the logs carry the request
id:

const resolvers = {
  Query: {
    hello: (_, __, context) => {
      context.log.debug('resolving hello')
      return 'world'
    }
  }
}

If you use any of the @envelop/* plugins listed above, install the logger:

npm i @graphql-hive/logger

If you depended on @graphql-yoga/logger directly, switch to @graphql-hive/logger:

- import { Logger } from '@graphql-yoga/logger';
+ import { Logger } from '@graphql-hive/logger';

To keep logging through Fastify's logger in @graphql-yoga/nestjs:

import { Logger } from 'graphql-yoga'
import { PinoLogWriter } from '@graphql-hive/logger/writers/pino'

// in your yoga driver options
logging: new Logger({ writers: [new PinoLogWriter(app.log)] })

`v5.2.2`

Patch Changes

#4577
7bff35c
Thanks @egoodwinx! - Add homepage and bugs.url to package.json
files

Configuration

📅 Schedule: (UTC)

Branch creation
- At any time (no schedule defined)
Automerge
- At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

changeset-bot · 2025-08-19T17:45:07Z

⚠️ No Changeset found

Latest commit: 8b3bd1a

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

codecov-commenter · 2025-08-19T17:46:56Z

⚠️ Please install the to ensure uploads and comments are reliably processed by Codecov.

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 92.19%. Comparing base (d095114) to head (8b3bd1a).
❗ Your organization needs to install the Codecov GitHub app to enable full functionality.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #813   +/-   ##
=======================================
  Coverage   92.19%   92.19%           
=======================================
  Files          17       17           
  Lines         397      397           
  Branches      128      128           
=======================================
  Hits          366      366           
  Misses         31       31

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

renovate Bot force-pushed the renovate/major-envelop branch from 9fc941b to 3d12a38 Compare August 19, 2025 17:45

renovate Bot force-pushed the renovate/major-envelop branch from 3d12a38 to 9e02ee5 Compare August 31, 2025 10:46

renovate Bot force-pushed the renovate/major-envelop branch from 9e02ee5 to a67f247 Compare November 9, 2025 18:15

renovate Bot changed the title ~~chore(deps): update dependency @envelop/testing to v9~~ chore(deps): update dependency @envelop/testing to v10 Nov 9, 2025

renovate Bot force-pushed the renovate/major-envelop branch from a67f247 to 9ba2bf1 Compare December 31, 2025 17:04

renovate Bot force-pushed the renovate/major-envelop branch from 9ba2bf1 to ab27fca Compare January 23, 2026 17:49

renovate Bot force-pushed the renovate/major-envelop branch from ab27fca to 5278699 Compare February 14, 2026 17:29

renovate Bot force-pushed the renovate/major-envelop branch from 5278699 to 41ca29e Compare March 5, 2026 17:21

renovate Bot force-pushed the renovate/major-envelop branch from 41ca29e to a16c65e Compare April 8, 2026 17:21

renovate Bot force-pushed the renovate/major-envelop branch from a16c65e to 15ea51d Compare April 24, 2026 14:49

renovate Bot force-pushed the renovate/major-envelop branch from 15ea51d to c88d122 Compare May 28, 2026 17:18

renovate Bot changed the title ~~chore(deps): update dependency @envelop/testing to v10~~ chore(deps): update envelop to v10 Jun 2, 2026

renovate Bot changed the title ~~chore(deps): update envelop to v10~~ chore(deps): update envelop (major) Jun 22, 2026

renovate Bot changed the title ~~chore(deps): update envelop (major)~~ chore(deps): update dependency @envelop/testing to v10 Jun 25, 2026

renovate Bot force-pushed the renovate/major-envelop branch from c88d122 to 69335d3 Compare August 22, 2026 10:42

renovate Bot force-pushed the renovate/major-envelop branch from 69335d3 to ef8b16c Compare September 8, 2026 00:35

renovate Bot force-pushed the renovate/major-envelop branch from ef8b16c to e63eba0 Compare September 19, 2026 17:49

renovate Bot force-pushed the renovate/major-envelop branch 3 times, most recently from 6550533 to 92e0c00 Compare October 13, 2026 12:09

renovate Bot force-pushed the renovate/major-envelop branch 2 times, most recently from b8896fc to a8d3e8d Compare October 25, 2026 20:51

renovate Bot changed the title ~~chore(deps): update dependency @envelop/testing to v10~~ chore(deps): update envelop (major) Oct 25, 2026

renovate Bot force-pushed the renovate/major-envelop branch from a8d3e8d to 56c5dc3 Compare October 26, 2026 18:10

chore(deps): update envelop

8b3bd1a

renovate Bot force-pushed the renovate/major-envelop branch from 56c5dc3 to 8b3bd1a Compare November 5, 2026 22:22

tiankaima mentioned this pull request Nov 7, 2026

chore(graphql): coordinate Yoga 6 and Armor/Envelop security upgrade Life-USTC/server#1493

Open

Navigation Menu

Repository navigation

chore(deps): update envelop (major) - #813

chore(deps): update envelop (major)#813
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/major-envelop

renovate Bot commented Jun 23, 2025 •

edited

Loading

Uh oh!

changeset-bot Bot commented Aug 19, 2025 •

edited

Loading

Uh oh!

codecov-commenter commented Aug 19, 2025 •

edited

Loading

Uh oh!

This branch has not been deployed

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Conversation

renovate Bot commented Jun 23, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release Notes

Major Changes

Migration

Incremental delivery

Breaking Changes

Migration

Breaking Changes

Minor Changes

Breaking Changes

Migration

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Minor Changes

Minor Changes

Patch Changes

Patch Changes

Minor Changes

Major Changes

Migration

Incremental delivery

Breaking Changes

Migration

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Major Changes

Migration

Minor Changes

Breaking Changes

Migration

Patch Changes

Configuration

Uh oh!

changeset-bot Bot commented Aug 19, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

⚠️ No Changeset found

Uh oh!

codecov-commenter commented Aug 19, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Codecov Report

Uh oh!

This branch has not been deployed

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

renovate Bot commented Jun 23, 2025 •

edited

Loading

changeset-bot Bot commented Aug 19, 2025 •

edited

Loading

codecov-commenter commented Aug 19, 2025 •

edited

Loading