Skip to content

Bump @graphql-tools/utils, mockrtc and mockttp - #35

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/multi-d9373d0ca1
Open

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/multi-d9373d0ca1

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 2, 2026 •

Copy link
Copy Markdown
Contributor

Bumps @graphql-tools/utils to 12.1.0 and updates ancestor dependencies @graphql-tools/utils, mockrtc and mockttp. These dependencies need to be updated together.

Updates @graphql-tools/utils from 8.8.0 to 12.1.0

Changelog

Sourced from @​graphql-tools/utils's changelog.

12.1.0

Minor Changes

  • #8445 82457d1 Thanks @​ardatan! - Fix: Preserve symbol-keyed GraphQL extensions when building, merging, or extracting schemas.

    GraphQL.js v17 allows string | symbol keys on schema/type/field extensions (via toObjMapWithSymbols). @graphql-tools was dropping those symbol keys in two places:

    1. mergeDeep only walked enumerable string keys (for...in), so symbol extensions were lost when applying schemaExtensions.
    2. extractExtensionsFromSchema did not copy non-enumerable own symbol keys (enumerable symbols already survive object rest/spread; the explicit loop covers the non-enumerable case).

    Example (bug)

    import { makeExecutableSchema } from '@graphql-tools/schema'
    const META = Symbol('META')
    const schema = makeExecutableSchema({
    typeDefs: /* GraphQL */ type Query { hello: String },
    schemaExtensions: {
    schemaExtensions: {
    [META]: { source: 'app' },
    tagged: true,
    },
    types: {},
    },
    })
    // Before: only string keys survived
    // schema.extensions === { tagged: true }
    // After: symbol keys are preserved
    // schema.extensions[META] === { source: 'app' }
    // schema.extensions.tagged === true

    Schema extension merge/extract and resolver merging always enable { enumerable: true, nonEnumerable: true } so symbol keys survive in tools' own merge/extract paths on every supported GraphQL.js major. (GraphQL.js itself may still drop symbol keys from field configs below v17 when rebuilding types.)

    mergeDeep API

    mergeDeep now accepts an options object. The old positional boolean arguments still work but are deprecated.

    import { mergeDeep } from '@graphql-tools/utils'

... (truncated)

Commits
  • 3634233 chore(release): update monorepo packages versions (#8505)
  • a75d725 fix(utils): keep argument types of defined directives in pruneSchema (#8493)
  • 98673c3 fix(utils): coerce GraphQL 17 argument defaults in getArgumentValues (#8513)
  • 82457d1 fix: preserve symbol-keyed schema extensions (#8445)
  • 691cbd7 build(deps): bump the actions-deps group across 1 directory with 16 updates (...
  • 28d08e8 chore(release): update monorepo packages versions (#8486)
  • fd95dc9 fix(utils): skip empty descriptions in getDescriptionNode (#8499)
  • a73dd1d build(deps-dev): bump the actions-deps group across 1 directory with 3 update...
  • 944121e Upcoming Release Changes (#8483)
  • 19f5b33 fix(utils): compare path keys to proto at the property access (#8482)
  • Additional commits viewable in compare view
Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for @​graphql-tools/utils since your current version.


Updates mockrtc from 0.4.0 to 0.5.2

Commits
  • 2afa16e 0.5.2
  • 1c152a9 Fix release workflow
  • 904c00b Fix flake in events tests
  • e7b6aa3 Don't throw for already-closed connections during setup
  • 108a7a8 Fix flaky behaviour caused by libdatachannel shutdown race
  • b5fee32 Work around flaky behaviour caused by a libdatachannel channel race
  • f0639b1 Bump assorted outdated devdeps
  • 38ad980 Update graphql-tools to latest to dedupe with Mockttp
  • c26c23b 0.5.1
  • 2d7673a Update GHA steps
  • Additional commits viewable in compare view
Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for mockrtc since your current version.


Updates mockttp from 3.17.0 to 4.6.5

Release notes

Sourced from mockttp's releases.

v4.0.0

import * as mockttp from 'mockttp';
const https = await mockttp.generateCACertificate();
const server = getLocal({ https });
server.forPost()
.forHostname("example.com")
.delay(500)
.thenReply(200, "Hello world");
server.forAnyWebSocket()
.withHeaders({ cookie: 'abcd' })
.thenPassThrough({
transformRequest: {
matchReplaceQuery: [/username=(.*)/, 'role=admin&username=$1']
}
});
await server.start();

Notable changes

  • Advanced URL rewriting: with a selection of new request transform options to separately rewrite and match/replace with regexes against the protocol, hostname, path & query, for both HTTP requests & websockets.
  • Support for multi-step rules, where a step can be non-final, allowing chaining of behaviour. The first new non-final step that's supported is a new delay(X) step, which you can add to any rule to wait Xms before running the next step. More to come (open an issue with ideas!)
  • Added support for inbound SOCKS proxying, enabled with the socks: true option.
  • Added support for unknown-protocol blind data passthrough, with the passthrough: ['unknown-protocol'] option. With this enabled, non-HTTP traffic will be recognized, and automatically proxied untouched through Mockttp to its destination. This is only possible when a connection destination is provided separately, with an HTTP or SOCKS tunnel (i.e. this isn't supported in direct connections). All proxied data is fully observable via the new raw-passthrough-* events.
  • Added support for connection-tagging via proxy authentication (with SOCKS & HTTP proxies). To add a tag to all data on a connection, authenticate with username metadata and a password containing JSON like {"tags":["tag1", ...]} (255 character length limit). The password can be base64 encoded if required. SOCKS proxying also supports a custom authentication method (0xDA) to attach metadata to a connection without length limits, but this requires custom client support. The resulting data is available in the tags field of all request events and similar fired by this connection later.
  • Client-side usage (getRemote or browser usage) no longer requires use of http-encoding, zstd-codec, brotli-wasm or similar, simplifying many browser testing use cases. Instead all decoding is handled transparently on the server-side. Automatic encoding can also be disabled completely using the new messageBodyDecoding: 'none' Mockttp client option, which will expose only encoded (or no-encoding-required) data and require you to manually handle encoded cases (throwing an error if you try to read encoded data without doing so).

💥 Breaking changes

  • The minimum Node version is now Node v20. v18 will still work, for now, but may stop working unpredictably in any future release.
  • Proxying:
    • Explicitly proxy destinations are now consistently used in preference to host/:authority header values if both are available but don't match. This could previously be inconsistent in some cases, but we now assume if you attempt to proxy to a server, then that's the 'real' destination, and this is reflected in the url property and elsewhere.
    • Proxy-connection & proxy-authorization headers are now always preprocessed and stripped up front. Previously this happened during upstream proxying, so these headers could be visible in events and similar, which is probably not what you expected. This applies even for direct requests (GET https://google.com) that don't create a separate tunnel.
    • When using Node 22.13+, extra default headers will no longer be added automatically to proxied requests. This previously resulted in automatic addition of transfer-encoding and connection headers. This will no longer be applied by default. If your request is already normal valid HTTP this will not cause a problem. If not (unlikely unless you're building HTTP requests without a proper client) then you will need to fix your request or use a beforeRequest callback to manually do so.
    • When modifying a proxied request with the various passthrough options, if you modify the body we now enforce that you include valid framing headers, and we set them if you don't. This is probably what you want (if you modify the body, you want to set the right content-length so that it is delivered). This is as cautious as possible, so in practice this should only correct invalid cases that would be invalid HTTP otherwise.
    • When redirecting proxied traffic, you can no longer use thenForwardTo with a beforeRequest callback. Internally, forwarding is now part of the transformRequest options, which can't be used with the corresponding callback. Instead, return a url from your beforeRequest callback directly.
    • Upstream ECONNRESET errors are now only simulated downstream if simulateConnectionErrors is set, like other connection issues (this was previously inconsistent for backward compatibility).
  • Events:
    • TLS event connectHostname, connectPort and hostname properties have been removed as they were ambiguous. Instead depending on your use case you will want one of:
      • event.destination for the tunnel target hostname & port
      • event.tlsMetadata.sniHostname for the servername specified in the TLS SNI extension.
    • hostname has been removed from request & websocket events too, as it wasn't clear where this came from. Instead depending on your use case you will want one of:
      • event.url to get the effective URL of the request

... (truncated)

Commits
  • 10be585 4.6.5
  • 72dfe16 Add workaround for TLS socket bug
  • 7a5a46c Update node to match server on latest 24
  • 621c77e Update typescript to fix asn1 build error
  • cdb9fee 4.6.4
  • fee19d1 Update TLS impersonate for latest Chrome/BoringSSL matching
  • 6c29c41 Merge pull request #216 from theluckystrike/fix/mockttp-getjson-type
  • 35a7138 Type getJson() for every JSON value, with an optional type argument
  • d3ba3db Bump @​graphql-tools/utils to v12
  • e352313 Merge pull request #215 from theluckystrike/fix/mockttp-payer-proof
  • Additional commits viewable in compare view
Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for mockttp since your current version.


@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Nov 2, 2026
@socket-security

socket-security Bot commented Nov 2, 2026 •

Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Updatedmockrtc@​0.4.0 ⏵ 0.5.279 +2100100 +187 +4100
Updatedmockttp@​3.17.0 ⏵ 4.6.59510010093 +3100

View full report

@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/multi-d9373d0ca1 branch from c4d2c0a to a483400 Compare November 2, 2026 12:18
Bumps [@graphql-tools/utils](https://github.com/ardatan/graphql-tools/tree/HEAD/packages/utils) to 12.1.0 and updates ancestor dependencies [@graphql-tools/utils](https://github.com/ardatan/graphql-tools/tree/HEAD/packages/utils), [mockrtc](https://github.com/httptoolkit/mockrtc) and [mockttp](https://github.com/httptoolkit/mockttp). These dependencies need to be updated together.


Updates `@graphql-tools/utils` from 8.8.0 to 12.1.0
- [Release notes](https://github.com/ardatan/graphql-tools/releases)
- [Changelog](https://github.com/ardatan/graphql-tools/blob/master/packages/utils/CHANGELOG.md)
- [Commits](https://github.com/ardatan/graphql-tools/commits/@graphql-tools/utils@12.1.0/packages/utils)

Updates `mockrtc` from 0.4.0 to 0.5.2
- [Commits](httptoolkit/mockrtc@v0.4.0...v0.5.2)

Updates `mockttp` from 3.17.0 to 4.6.5
- [Release notes](https://github.com/httptoolkit/mockttp/releases)
- [Commits](httptoolkit/mockttp@v3.17.0...v4.6.5)

---
updated-dependencies:
- dependency-name: "@graphql-tools/utils"
  dependency-version: 12.1.0
  dependency-type: indirect
- dependency-name: mockrtc
  dependency-version: 0.5.2
  dependency-type: direct:production
- dependency-name: mockttp
  dependency-version: 4.6.5
  dependency-type: direct:development
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/multi-d9373d0ca1 branch from a483400 to 4ccd459 Compare November 15, 2026 20:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants