Skip to content

fix: update auto merge on patch or minor - #287

Merged
notaphplover merged 1 commit into
masterfrom
renovate/auto-merge-on-patch-or-minor
Oct 19, 2026
Merged

fix: update auto merge on patch or minor#287
notaphplover merged 1 commit into
masterfrom
renovate/auto-merge-on-patch-or-minor

Conversation

@inversify-app

@inversify-app inversify-app Bot commented Oct 19, 2026

Copy link
Copy Markdown
Contributor

Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence Type Update Pending
@graphql-codegen/cli (source) ^7.4.5 → ^7.4.6 age confidence dependencies patch
@graphql-codegen/typescript (source) ^6.1.1 → ^6.1.2 age confidence dependencies patch
@graphql-tools/merge (source) 9.2.6 → 9.2.8 age confidence dependencies patch
@graphql-tools/schema (source) ^10.1.3 → ^10.1.5 age confidence dependencies patch
@graphql-tools/utils (source) 12.0.3 → 12.1.0 age confidence devDependencies minor
@inversifyjs/http-core (source) ^5.6.3 → ^5.9.0 age confidence peerDependencies minor
@inversifyjs/http-express (source) 5.6.3 → 5.9.0 age confidence devDependencies minor
@inversifyjs/http-fastify (source) 5.6.3 → 5.9.0 age confidence devDependencies minor
@types/node (source) 24.19.1 → 24.19.2 age confidence devDependencies patch
@vitest/coverage-v8 (source) 5.0.3 → 5.0.5 age confidence devDependencies patch
fastify (source) 5.12.5 → 5.12.7 age confidence devDependencies patch
graphql-ws (source) 6.3.0 → 6.4.1 age confidence dependencies minor
knip (source) 6.40.0 → 6.41.0 age confidence devDependencies minor 6.42.0
node (source) 24.21.0 → 24.22.0 age confidence minor
pnpm (source) 12.10.1 → 12.14.0 age confidence tool-constraint minor
pnpm (source) 12.10.1 → 12.14.0 age confidence packageManager minor
prettier (source) 3.9.9 → 3.9.10 age confidence devDependencies patch
prettier (source) ^3.9.9 → ^3.9.10 age confidence dependencies patch
vitest (source) 5.0.3 → 5.0.5 age confidence devDependencies patch

Release Notes

dotansimha/graphql-code-generator (@​graphql-codegen/cli)

v7.4.6

Compare Source

Patch Changes

  • #​10985
    d8aa07f
    Thanks @​eddeee888! - Build with strict: true, which changes
    these emitted type declarations:

    • @graphql-codegen/cli: mkdirp returns Promise<string | undefined>, and the require (-r)
      CLI option's default is typed never[] instead of any[].
    • @graphql-codegen/visitor-plugin-common: BaseResolversVisitor and BaseTypesVisitor
      SchemaDefinition()/SchemaExtension() return null instead of any.
    • @graphql-codegen/visitor-plugin-common: BaseSelectionSetProcessor.typeCache is keyed by
      Location | undefined.
    • @graphql-codegen/visitor-plugin-common: SelectionSetToObject.buildSelectionSet returns
      typeInfo as { name: string; type: string } | null.
    • @graphql-codegen/visitor-plugin-common: getPossibleTypes accepts null as the type, which
      graphql 15's schema.getType() can return.
    • @graphql-codegen/visitor-plugin-common: removeDescription returns nodes with
      description: undefined instead of any.
    • @graphql-codegen/typescript: TsIntrospectionVisitor's constructor takes pluginConfig as
      TypeScriptPluginConfig | undefined, DirectiveDefinition() returns null and
      ObjectTypeDefinition() returns string | null.
    • @graphql-codegen/client-preset: the babel preset accepts options as
      ClientBabelPresetOptions | null | undefined.
    • @graphql-codegen/testing: mockGraphQLServer returns nock.Scope | null.
    • @graphql-codegen/graphql-modules-preset: a schema without extensions (graphql 15) throws the
      "requires to use GraphQL SDL" error instead of a TypeError.

    Generated output is unchanged.

  • Updated dependencies
    [d8aa07f]:

dotansimha/graphql-code-generator (@​graphql-codegen/typescript)

v6.1.2

Compare Source

Patch Changes

  • #​10985
    d8aa07f
    Thanks @​eddeee888! - Build with strict: true, which changes
    these emitted type declarations:

    • @graphql-codegen/cli: mkdirp returns Promise<string | undefined>, and the require (-r)
      CLI option's default is typed never[] instead of any[].
    • @graphql-codegen/visitor-plugin-common: BaseResolversVisitor and BaseTypesVisitor
      SchemaDefinition()/SchemaExtension() return null instead of any.
    • @graphql-codegen/visitor-plugin-common: BaseSelectionSetProcessor.typeCache is keyed by
      Location | undefined.
    • @graphql-codegen/visitor-plugin-common: SelectionSetToObject.buildSelectionSet returns
      typeInfo as { name: string; type: string } | null.
    • @graphql-codegen/visitor-plugin-common: getPossibleTypes accepts null as the type, which
      graphql 15's schema.getType() can return.
    • @graphql-codegen/visitor-plugin-common: removeDescription returns nodes with
      description: undefined instead of any.
    • @graphql-codegen/typescript: TsIntrospectionVisitor's constructor takes pluginConfig as
      TypeScriptPluginConfig | undefined, DirectiveDefinition() returns null and
      ObjectTypeDefinition() returns string | null.
    • @graphql-codegen/client-preset: the babel preset accepts options as
      ClientBabelPresetOptions | null | undefined.
    • @graphql-codegen/testing: mockGraphQLServer returns nock.Scope | null.
    • @graphql-codegen/graphql-modules-preset: a schema without extensions (graphql 15) throws the
      "requires to use GraphQL SDL" error instead of a TypeError.

    Generated output is unchanged.

  • Updated dependencies
    [d8aa07f,
    5078faf]:

ardatan/graphql-tools (@​graphql-tools/merge)

v9.2.8

Compare Source

Patch Changes

  • #​8445 82457d1 Thanks @​ardatan! - dependencies updates:

  • #​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'

// Deprecated (still supported)
mergeDeep([a, b], false, true, false, true)
//                ^proto ^arrays ^len  ^non-enumerable symbols only

// Preferred
mergeDeep([a, b], {
  respectPrototype: false,
  respectArrays: true,
  respectArrayLength: false,
  respectSymbols: {
    enumerable: true, // merge `obj[sym] = value` keys
    nonEnumerable: true, // copy defineProperty(..., { enumerable: false }) symbols
  },
})

respectSymbols defaults to { enumerable: false, nonEnumerable: false } (symbols dropped), matching the historical default. The legacy 5th positional flag still maps to { nonEnumerable: true } only.

Resolver map types (IResolvers / field resolver extensions and type __extensions) now use ExtensionsObject (Record<string | symbol, any>), so symbol-keyed resolver extensions type-check under GraphQL.js v17+.

v9.2.7

Compare Source

Patch Changes
ardatan/graphql-tools (@​graphql-tools/schema)

v10.1.5

Compare Source

Patch Changes

  • #​8445 82457d1 Thanks @​ardatan! - dependencies updates:

  • #​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'

// Deprecated (still supported)
mergeDeep([a, b], false, true, false, true)
//                ^proto ^arrays ^len  ^non-enumerable symbols only

// Preferred
mergeDeep([a, b], {
  respectPrototype: false,
  respectArrays: true,
  respectArrayLength: false,
  respectSymbols: {
    enumerable: true, // merge `obj[sym] = value` keys
    nonEnumerable: true, // copy defineProperty(..., { enumerable: false }) symbols
  },
})

respectSymbols defaults to { enumerable: false, nonEnumerable: false } (symbols dropped), matching the historical default. The legacy 5th positional flag still maps to { nonEnumerable: true } only.

Resolver map types (IResolvers / field resolver extensions and type __extensions) now use ExtensionsObject (Record<string | symbol, any>), so symbol-keyed resolver extensions type-check under GraphQL.js v17+.

v10.1.4

Compare Source

Patch Changes
ardatan/graphql-tools (@​graphql-tools/utils)

v12.1.0

Compare Source

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'

// Deprecated (still supported)
mergeDeep([a, b], false, true, false, true)
//                ^proto ^arrays ^len  ^non-enumerable symbols only

// Preferred
mergeDeep([a, b], {
  respectPrototype: false,
  respectArrays: true,
  respectArrayLength: false,
  respectSymbols: {
    enumerable: true, // merge `obj[sym] = value` keys
    nonEnumerable: true, // copy defineProperty(..., { enumerable: false }) symbols
  },
})

respectSymbols defaults to { enumerable: false, nonEnumerable: false } (symbols dropped), matching the historical default. The legacy 5th positional flag still maps to { nonEnumerable: true } only.

Resolver map types (IResolvers / field resolver extensions and type __extensions) now use ExtensionsObject (Record<string | symbol, any>), so symbol-keyed resolver extensions type-check under GraphQL.js v17+.

Patch Changes

  • #​8513 98673c3 Thanks @​ardatan! - fix(utils): coerce GraphQL 17 argument defaults in getArgumentValues via local input coercion (defaults, missing variables, nested sources)

  • #​8493 a75d725 Thanks @​cpruijsen! - Keep argument types of defined directives when pruning so that unused directives such as @key(fields: _FieldSet!) retain their full definitions instead of losing the argument together with its type.

v12.0.4

Compare Source

Patch Changes
  • #​8499 fd95dc9 Thanks @​ardatan! - Skip empty and whitespace-only description values in getDescriptionNode / printSchemaWithDirectives, so loaders that set description: "" no longer emit """""" in printed SDL.
inversify/monorepo (@​inversifyjs/http-core)

v5.9.0

Compare Source

Patch Changes

v5.8.0

Compare Source

Patch Changes

v5.7.0

Compare Source

Minor Changes

Add optional HTTP instrumentation sinks. Event types and the sink live in @inversifyjs/http-instrumentation-core. Adapters emit pipeline events only when at least one sink is configured. The Express 5 adapter also records native middleware, and the Express 5, Fastify, Hono, and uWebSockets adapters record request and response headers and status.

Patch Changes
vitest-dev/vitest (@​vitest/coverage-v8)

v5.0.5

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v5.0.4

Compare Source

   🚀 Features
   🐞 Bug Fixes
   🏎 Performance
    View changes on GitHub
fastify/fastify (fastify)

v5.12.7

Compare Source

Full Changelog: fastify/fastify@v5.12.6...v5.12.7

v5.12.6

Compare Source

⚠️ Security Release
What's Changed

Full Changelog: fastify/fastify@v5.12.5...v5.12.6

enisdenjo/graphql-ws (graphql-ws)

v6.4.1

Compare Source

Patch Changes
  • #​703 707c38c Thanks @​lprnmns! - Use the jsonMessageReplacer when automatically responding to a ping with a pong, on both the client and the server

v6.4.0

Compare Source

Minor Changes
  • #​696 83be052 Thanks @​niukanen1! - Add an isProd option to the ws, uWebSockets.js and @fastify/websocket use-server helpers, matching the existing crossws option. It controls whether internal error messages are masked with Internal server error before reaching the client, defaulting to the NODE_ENV === 'production' check as before. This lets apps running in production keep reporting onConnect error messages to the client by opting out, or mask eagerly in non-production environments.
Patch Changes

  • #​700 d8aeda6 Thanks @​kratam! - Fix the client closing an in-use socket when many subscriptions complete at once and a new one subscribes within the lazyCloseTimeout

    Every completing subscription scheduled its own lazy close timeout, but only the last one got cleared on the next connect. The client now keeps a single lazy close timeout and checks for active subscriptions before closing.

  • #​702 1e05c8c Thanks @​Meemaw! - Avoid an unhandled rejection when a subscription is disposed before the connection is acknowledged and the socket closes before the subscription releases its connection lock (for example, when the client is disposed while connecting and the WebSocket implementation delivers the close event on a microtask).

webpro-nl/knip (knip)

v6.41.0: Release 6.41.0

Compare Source

[!IMPORTANT]
✂ PR body was truncated to here.

Configuration

📅 Schedule: (UTC)

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

🚦 Automerge: Enabled.

♻ 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 has been generated by Mend Renovate CLI.

@inversify-app
inversify-app Bot requested a review from notaphplover as a code owner October 19, 2026 02:19
@changeset-bot

changeset-bot Bot commented Oct 19, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 12829a1

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

@coderabbitai

coderabbitai Bot commented Oct 19, 2026

Copy link
Copy Markdown

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration
  • Configuration used: defaults
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 54294217-384d-420e-8e62-4ce509055124

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@notaphplover
notaphplover merged commit 79996e2 into master Oct 19, 2026
7 checks passed
@notaphplover
notaphplover deleted the renovate/auto-merge-on-patch-or-minor branch October 19, 2026 16:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@notaphplover notaphplover Awaiting requested review from notaphplover notaphplover is a code owner

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@notaphplover