Skip to content

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

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

notaphplover merged 1 commit into
masterfrom
renovate/auto-merge-on-patch-or-minor

Conversation

@inversify-app

@inversify-app inversify-app Bot commented Nov 2, 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-tools/merge (source) 10.0.6 → 10.0.7 age confidence dependencies patch 10.0.8
@graphql-tools/schema (source) ^11.0.6 → ^11.0.7 age confidence dependencies patch 11.0.8
@graphql-tools/utils (source) 13.1.3 → 13.2.0 age confidence devDependencies minor 13.2.1
@inversifyjs/http-core (source) ^5.9.0 → ^5.9.1 age confidence peerDependencies patch
@inversifyjs/http-express (source) 5.9.0 → 5.9.1 age confidence devDependencies patch
@inversifyjs/http-fastify (source) 5.9.0 → 5.9.1 age confidence devDependencies patch
knip (source) 6.42.1 → 6.44.0 age confidence devDependencies minor 6.44.1
node (source) 24.22.1 → 24.22.2 age confidence patch
pnpm (source) 12.15.0 → 12.16.1 age confidence tool-constraint minor
pnpm (source) 12.15.0 → 12.16.1 age confidence packageManager minor

Release Notes

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

v10.0.7

Compare Source

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

v11.0.7

Compare Source

Patch Changes
  • #​8601 902d870 Thanks @​ardatan! - mergeSchemas and makeExecutableSchema now accept onFieldTypeConflict, the same callback mergeTypeDefs already had.

    When two schemas define the same field with different types, default merge throws. When only nullability differs, it keeps the earlier type.

    # first schema
    type Post {
      id: ID!
      title: String!
      content: String!
      published: Boolean!
    }
    
    # second schema
    type Post {
      id: ID!
      title: String
      content: Int
      fieldA: Int
      fieldB: String
    }

    content: String! vs content: Int throws. title: String! vs title: String keeps String!.

    mergeSchemas({
      schemas: [firstSchema, secondSchema],
      onFieldTypeConflict: (_existing, incoming) => incoming,
    });

    The merged Post takes title: String and content: Int from the second schema, keeps published from the first, and adds fieldA / fieldB. Types that exist on only one schema, such as User on the first, stay.

    The same callback applies to field arguments. Returning the incoming field uses the second schema's argument types and still keeps arguments that exist on only one side. Returning the existing field with reverseArguments: true keeps the first schema's argument types and still appends new arguments.

  • Updated dependencies [6da2904, 7770067, f956bfe]:

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

v13.2.0

Compare Source

Minor Changes
  • #​8606 6da2904 Thanks @​ardatan! - loadDocuments / loadTypedefs now accept errorHandling so a single invalid file does not have to hide the rest of the load.

    A glob that mixes a valid operation with broken SDL used to throw the first Syntax Error and drop every other file:

    # valid.query.graphql
    query ValidQuery {
      a
    }
    # broken-a.query.graphql
    query {
      a
    await loadDocuments('**/*.query.graphql', {
      loaders: [new GraphQLFileLoader()],
    });
    // throws Syntax Error

    errorHandling chooses what happens next. The default is unchanged (throw the first error).

    aggregate waits until every source is attempted, then throws AggregateError with each parse/load failure:

    await loadDocuments('**/*.query.graphql', {
      loaders: [new GraphQLFileLoader()],
      errorHandling: 'aggregate',
    });

    return does not throw. Failed sources stay in the result as { location, error } without a document, next to the sources that parsed:

    const sources = await loadDocuments('**/*.query.graphql', {
      loaders: [new GraphQLFileLoader(), new CodeFileLoader()],
      errorHandling: 'return',
    });
    
    sources[0].document; // ValidQuery
    sources[1].document; // undefined
    sources[1].error; // GraphQLError: Syntax Error

    Source now has an optional error field. @graphql-tools/graphql-file-loader and @graphql-tools/code-file-loader honor the same option. CodeFileLoader's existing noSilentErrors default is unchanged unless errorHandling is set.

    Custom loader failures and incomplete inline documents (query Foo {) follow the same option. errorHandling: 'throw' raises the first failure, not AggregateError.

Patch Changes
  • #​8588 7770067 Thanks @​ardatan! - rewireTypes (used by mapSchema and addTypes) now recreates only the types that actually reference a replaced type.

    mapSchema already changes just the mapped types. rewireTypes then walked every type and built a new GraphQLObjectType / enum / scalar so field pointers stayed consistent. That is correct, and it is overkill when a pipeline maps one type on a large schema: unrelated types, unused enums, and unused scalars were cloned on every pass.

    The crawl now finds types whose field, argument, interface, or union members point at a different object than the type map (including wrapper types created during mapping), then rebuilds only that set. Specified directives stay as-is. Types that do not reach a replacement keep the same JavaScript object.

    createStub returns the graphql-js specified scalars for String / ID / Int / Float / Boolean instead of building an object or input with that name. Stitch typeFromAST uses createStub for every field type.

    const schema = buildSchema(/* GraphQL */ `
      scalar Unused
      enum Color { RED }
      type Query { foo: Foo }
      type Foo { id: ID }
    `)
    
    const mapped = mapSchema(schema, {
      [MapperKind.OBJECT_TYPE]: type =>
        type.name === 'Foo'
          ? new GraphQLObjectType({ ...type.toConfig(), description: 'mapped' })
          : undefined,
    })
    
    mapped.getType('Unused') === schema.getType('Unused')
    mapped.getType('Color') === schema.getType('Color')
  • #​8608 f956bfe Thanks @​ardatan! - transformInputValue now keeps falsy list items when GraphQL coerces a singleton into a list.

    A [String] / [Int] / [Boolean] field can receive "", 0, or false instead of a one-element array. The previous asArray helper treated those as empty and produced [], so rename and other input transforms dropped a valid value. null is still returned as-is. A real list is still walked item by item.

inversify/monorepo (@​inversifyjs/http-core)

v5.9.1

Compare Source

Patch Changes
webpro-nl/knip (knip)

v6.44.0: Release 6.44.0

Compare Source

  • Clarify that custom entry still adds entry files from package.json (#​2206) (4099dde) - thanks @​MannXo!
  • Resolve expanded package scripts against the directory of their manifest (#​2209) (9d8464d) - thanks @​fixfon!
  • Track exports through namespace member chains of any depth (#​2210) (7569702) - thanks @​fixfon!
  • Do not treat Windows drive letters as package names (#​2217) (d412c5b) - thanks @​Cherry!
  • Generate built-in compilers list from source (#​2216) (d6f594c) - thanks @​abrahamguo!
  • Update to pnpm@^11 + pnpm dedupe (ef5b819)
  • Stop growing and rewriting the analysis cache on warm runs (close #​2213) (54b02dd)
  • Use entry in plugins that do not resolve their config files (0b0e328)
  • Reuse graph reachability for incremental sessions (#​2190) (38d926a) - thanks @​jakeleventhal!
  • fix: reload discovered configuration in watch sessions (#​2211) (cefef30) - thanks @​jakeleventhal!
  • Keep editor sessions and views current (#​2215) (cfe91ab) - thanks @​jakeleventhal!
  • Add Lingui plugin (#​2212) (611e7db) - thanks @​clean99!
  • Update dependency bun to v1.4.4 (#​2219) (3f35bbd) - thanks @​renovate[bot]!
  • Read CSpell configuration from package.json (#​2228) (86ab963) - thanks @​clean99!
  • Ignore file discovery order in session configuration test (51a8d33)
  • Fix strict mode for caught optional peer imports (#​2218) (e535f40) - thanks @​jay23606!
  • Add kysely-codegen plugin (#​2223) (a50e842) - thanks @​clean99!
  • Add PurgeCSS plugin (#​2224) (668aea6) - thanks @​clean99!
  • Document plugin args and path bases, issue key order and real-world fixes (8e48df6)
  • Add Mastra plugin (#​2227) (dd4e1f7) - thanks @​ashokram-si!
  • Count findPackageJSON() bare specifiers as dependencies (#​2235) (d4e387b) - thanks @​abrahamguo!
  • Add universal hooks file to SvelteKit entries (#​2237) (f286584) - thanks @​APX403!
  • Attribute extended tsconfig plugins correctly (#​2230) (8d1d1d1) - thanks @​gioboa!
  • Resolve reporter in the Mocha plugin (#​2232) (c413715) - thanks @​X-Guardian!
  • Read nyc.config.cjs and nyc.config.mjs in the nyc plugin (#​2240) (724c3c9) - thanks @​SwastikTripathi!
  • Read hidden .biome.json and .biome.jsonc in the Biome plugin (#​2239) (dde22a7) - thanks @​SwastikTripathi!
  • fix: narrow Remix plugin enabler to @​remix-run/dev (#​2242) (5e10c52) - thanks @​gioboa!
  • Document alsoReferenceOwner on Input (387e97f)
  • Document path bases and the dir option per input type (98180d3)
  • Emit the Gatsby production entries from resolveConfig (c224f16)
  • Emit the TanStack Router entry files from resolveConfig (c2598a3)
  • Discover Marko tag files when only marko-tag.json files exist (c264697)
  • Remove the static public/sw.js production entry from the vite-plugin-pwa plugin (b3f9a56)
  • Keep absolute build.lib.entry paths in the Vitest plugin (5d974fa)
  • Resolve Vite alias targets from the workspace without prefixing absolute paths (8f93e9d)
  • Keep absolute testDir paths in the Playwright plugin (4e3e6b3)
  • Keep absolute stories paths in the Storybook plugin (321decc)
  • Resolve an absolute basePath in the Karma plugin (64e8b1b)
  • Keep absolute local plugin paths in the Docusaurus plugin (058930d)
  • Keep absolute local plugin paths in the Serverless Framework plugin (0176d78)
  • Resolve Nx run-commands cwd from the workspace root (39c08aa)
  • Resolve package specifiers in Marko tag definitions (168ee52)
  • Keep absolute include paths in the Taskfile plugin (7945ec1)
  • Resolve Lefthook root from the repository root (f28fae6)
  • Pass specifiers with dir instead of absolutizing them in the webpack, Nx and textlint plugins (1ad804d)
  • Drop redundant relative calls on entry patterns in the rstest and Marko plugins (9096f25)
  • Use toAbsolute in the Jasmine, Lunaria and electron-vite plugins (b4266ef)
  • Mark inputs from the start script as production (2fb1024)
  • Mark inputs from scripts in production files as production (af469e9)
  • Apply directory gitignore patterns to static-only globs (efe514f)
  • Glob plugin config files once per workspace (b515677)
  • Resolve Mocha require and file from the working directory (c6850eb)
  • Cover the owning workspace of jsxImportSource in the tsconfig plugins test (0442096)
  • List nyc.config.{js,cjs,mjs} in the nyc plugin example (671e5fb)
  • Fold agent lessons into the tracked guides (e6cbfe3)
  • Ignore development script inputs that the start script repeats in production mode (15cd870)
  • Resolve Taskfile script entry patterns from the workspace directory (2730ffa)
  • Resolve plugin entry patterns from dir (6df9c4e)
  • Add GitHub Actions working-directory fixtures for mocha spec patterns (95efd3a)
  • Pin the scope of negations and workspace exclusions for plugin entry patterns with dir (2070464)
  • Parse GitHub Actions step scripts against their working directory (98d0b98)
  • Parse MCP server commands against their cwd (381e3e3)
  • Let core resolve script entries from dir in the Playwright, Railway and mise plugins (5d10668)
  • Add --output-file option to write reporter output to a file (#​2243) (1a58eb5) - thanks @​X-Guardian!
  • Treat packageExtensions peers as optional (#​2246) (e118ef4) - thanks @​gioboa!
  • Support pnpm workspace config includes (#​2238) (acbbbf5) - thanks @​gioboa!
  • Detect SWC plugins in options set directly on a webpack rule (#​2252) (624da93) - thanks @​fixfon!
  • Escape pipes in symbols in the markdown reporter (#​2254) (153ba1e) - thanks @​NgoQuocViet2001!
  • More than two hundred plugins (e68eaa5)
  • Update dependencies (8b06f9a)

v6.43.0: Release 6.43.0

Compare Source

nodejs/node (node)

v24.22.2: 2026-10-28, Version 24.22.2 'Krypton' (LTS), @​aduh95

Compare Source

Commits
pnpm/pnpm (pnpm)

v12.16.1: pnpm 12.16.1

Compare Source

This release fixes pnpm install hanging on a cold store in workspaces that install Cargo crates, and pnpm pack shipping a file that files excludes by name.

Patch Changes
  • pnpm install no longer hangs on a cold store in a workspace that also installs Cargo crates or a Rust toolchain.

  • pnpm pack and pnpm publish now apply a files entry that names a file after the glob and directory entries, as npm does. A file excluded by name, such as !dist/index.js, stays out even when a later dist/** matches it. A file named by its path, such as lib/secret.js, ships even when a later !lib/*.js matches it.

  • pnpm install no longer leaves a broken symlink in an injected workspace dependency when the package links to a file outside its published files and pnpm imports by hardlink. Installing a git dependency now skips internal directory symlinks when importing its files into the store.

  • pnpm install now relinks a command that a workspace project renames into the projects that depend on it when sharedWorkspaceLockfile is false pnpm/tasks#224.

  • pnpm install and pnpm rebuild now refresh privately hoisted .bin shims in node_modules/.pnpm/node_modules/.bin after a dependency build replaces a script target with a native executable #​17402.

  • pnpm install now reads a package's manifest to decide its peer dependencies when it updates an existing lockfile, as it does when it resolves from scratch.

  • Commands, pnpm --version, pnpm self-update, and invocations with unknown flags now apply the same packageManager and devEngines.packageManager settings when switching to the pinned pnpm version or recording it in pnpm-lock.yaml. --config.<key> flags and lockfileDir now reach the version switch and lockfile sync on every entry point. Unreadable settings in pnpm-workspace.yaml or the global config.yaml that do not affect the pin decision no longer block the version switch pnpm/tasks#222.

  • pnpm now accepts the --cache-dir <dir> flag, as in pnpm install --cache-dir /tmp/pnpm-cache #​17422.

  • When the version or range given to pnpm unpublish matches every published version, the error now says so and shows the same command with --force. Before, the error suggested running pnpm unpublish <pkg>@<version>, the command that had just failed.

Platinum Sponsors
Bit OpenAI Notion
CodeRabbit
Gold Sponsors
Sanity Discord Vite
SerpApi Stackblitz Workleap
Nx Latitude

v12.16.0: pnpm 12.16

Compare Source

This release adds a global --env-file flag, updates to a symlinked pnpm-lock.yaml, and pnpm setup --no-modify-path. It also fixes two security issues, in zstd decompression and in signing.

Minor Changes
  • Added a repeatable global --env-file <path> flag to load environment variables from dotenv-style files before running a command. Later files override earlier files, variables already in the environment are preserved, and loaded variables are visible to user-level .npmrc interpolation and lifecycle scripts #​7111.

  • pnpm can now update a pnpm-lock.yaml that is a symlink. List the directories the lockfile may link into in the symlinkedLockfileTargetDirs setting, in the global config or with PNPM_CONFIG_SYMLINKED_LOCKFILE_TARGET_DIRS. pnpm writes the update to the file the symlink points to if that file is inside one of these directories. The symlink stays in place. pnpm ignores this setting in pnpm-workspace.yaml #​17222.

  • Added a --no-modify-path option to pnpm setup. It installs pnpm without adding it to PATH, leaving the shell config file, the Windows registry, and the GitHub Actions environment files unchanged. pnpm setup then prints the lines to add yourself get.pnpm.io#37.

Patch Changes
Security
  • Fixed memory exposure and allocation handling vulnerabilities when processing zstd-compressed data #​17388.

  • Signing in pnpm and pnpr no longer uses arithmetic that may leak the private key through timing. This covers shared artifacts, OCI registry tokens, and OIDC login state advisory.

Installing packages
  • A dependency symlink that pnpm cannot point at the wanted target now fails the install with an error that names the link. This happens when the filesystem still serves the old link after pnpm removed it, as a node_modules served by a virtual filesystem does. pnpm used to remove the link again without end and crashed with a segmentation fault once the thread ran out of stack.

  • Concurrent workspace installs no longer lose store-index rows when initializing the shared SQLite index #​17388.

  • Agent skill links now keep the same target across installs when a package version is installed with several sets of peer dependencies. An install no longer fails with ERR_PNPM_AGENT_SKILL_PATH_OCCUPIED on a skill link that pnpm created for another of those copies #​17319.

  • pnpm now fails at once, without retrying, when a downloaded package archive contains a rejected entry path #​17205.

  • pnpm now builds a git-hosted dependency in every new location it links the dependency into, such as a new global virtual store slot or a fresh node_modules. When the side-effects cache holds the build output, pnpm restores it from there. Before, only the install that fetched the dependency built it. This also fixes dependencies that are already in the store #​17224.

  • Changes a preResolution hook makes to the lockfiles now take effect. The hook now also runs when pnpm installs from an up-to-date lockfile. An error thrown by the hook now fails the install.

  • A custom fetcher in the pnpmfile can now call fetchers.directory to fetch a package from a local directory. The call rejects with ERR_PNPM_TARBALL_INTEGRITY if the lockfile pins an archive integrity for the package. Previously, calling fetchers.directory failed with a TypeError.

  • packageImportMethod: copy now also applies to packages that have lifecycle scripts or patches. On a filesystem that supports block cloning, such as ReFS or a Dev Drive on Windows, these packages were cloned #​17195.

  • With nodeLinker: hoisted and autoInstallPeers: false, a package that workspace projects use with different peer versions is now installed once per peer variant, so each project's copy resolves that project's peer #​17395.

  • Under nodeLinker: hoisted, pnpm install now leaves a patched package that is already in place alone. The same holds for a package whose peers include a patched package, such as every package peering on a patched react-native #​17188.

  • With nodeLinker: hoisted, an install that stops partway no longer leaves the next install trusting the packages it was replacing. Before, reverting the change that started the stopped install, such as a patch edit, kept the half-replaced package in node_modules.

Repeat installs and changed settings
  • A repeat pnpm install now acts on a change to these settings. Before, it reported "Already up to date".

    • storeDir or virtualStoreDir: it recreates node_modules.
    • globalVirtualStoreDir: it links the packages from the new directory.
    • virtualStoreDirMaxLength: it renames the virtual store directories.
    • dangerouslyAllowAllBuilds turned on: it runs the builds it skipped.
    • trustLockfile turned off: it verifies the lockfile.
  • pnpm add, pnpm remove, and pnpm update now fail if node_modules does not match the current settings. Run pnpm install to recreate it. Previously, these commands removed and reinstalled node_modules without asking. They report:

    • ERR_PNPM_UNEXPECTED_STORE if node_modules was linked from a different store.
    • ERR_PNPM_UNEXPECTED_VIRTUAL_STORE if it was linked from a different virtual store directory.
    • ERR_PNPM_MODULES_BREAKING_CHANGE if it was installed by an incompatible pnpm version, or if node_modules/.modules.yaml cannot be read.
    • ERR_PNPM_NODE_LINKER_DIFF if it was installed with a different nodeLinker.

    pnpm update now also fails with ERR_PNPM_HOIST_PATTERN_DIFF and the other errors pnpm add reports for a changed hoist pattern or virtualStoreDirMaxLength.

  • An install filtered to some workspace projects now fails if node_modules was installed with a different nodeLinker, hoistPattern, publicHoistPattern, store, or virtual store. Before, it recreated node_modules and left the projects it skipped without their dependencies. A pnpm install of the whole workspace still recreates node_modules pnpm/tasks#217.

  • pnpm install and the verifyDepsBeforeRun check now notice an edited patch file when sharedWorkspaceLockfile is false.

  • pnpm install now takes its fast path in a workspace with patchedDependencies when the previous install ran with another major version of pnpm.

  • pnpm install now relinks the bins of a workspace package when its bin field changes, including with --frozen-lockfile and an unchanged lockfile. A filtered install relinks them in the selected projects, and the next install that covers the remaining projects relinks them there #​17324.

  • pnpm install now removes command shims from node_modules/.bin when a workspace dependency renames or removes an entry from its bin field pnpm/tasks#211.

Resolving dependencies and the lockfile
  • A package that a plain range and a <prefix>: specifier both resolve from one registry is now recorded once in pnpm-lock.yaml and installed once. The lockfile key names the registry a package resolved from. When that registry declares a prefix, through prefix in `regist

[!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 November 2, 2026 03:16
@changeset-bot

changeset-bot Bot commented Nov 2, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: b46f791

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 Nov 2, 2026

Copy link
Copy Markdown

Important

Review skipped

Bot user detected.

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

Run configuration
  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: defaults
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: fda3e275-133b-46e2-8feb-a02130a4ce4f

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

@notaphplover
notaphplover merged commit 47bb476 into master Nov 3, 2026
8 checks passed
@notaphplover
notaphplover deleted the renovate/auto-merge-on-patch-or-minor branch November 3, 2026 11:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant