Skip to content

fix(deps): update examples (major) - #819

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/major-examples
Open

fix(deps): update examples (major)#819
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/major-examples

Conversation

@renovate

@renovate renovate Bot commented Jul 20, 2025 •
edited
Loading

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
@graphql-tools/schema (source) 10.0.23 → 11.0.8 age confidence
@nestjs/apollo 13.2.4 → 14.2.0 age confidence
@nestjs/cli 11.0.7 → 12.0.11 age confidence
@nestjs/common (source) 11.1.3 → 12.3.3 age confidence
@nestjs/graphql 13.2.4 → 14.2.0 age confidence
@nestjs/platform-express (source) 11.1.3 → 12.3.3 age confidence
@nestjs/testing (source) 11.1.3 → 12.3.3 age confidence
@types/node (source) 24.0.3 → 26.6.6 age confidence
eslint (source) 9.29.0 → 10.14.0 age confidence
graphql 16.11.0 → 17.0.2 age confidence
graphql-yoga (source) 5.13.5 → 6.0.1 age confidence
ts-morph 26.0.0 → 28.0.0 age confidence
typescript (source) 5.8.3 → 7.0.2 age confidence

Release Notes

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

v11.0.8

Compare Source

Patch Changes

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]:

v11.0.6

Compare Source

Patch Changes

  • #​8564 fe44242 Thanks @​ardatan! - requireResolversForArgs (and the other resolver-presence checks) now look for subscribe on the schema's subscription type.

    On subscriptions, subscribe is required and resolve is optional. The validator used to look only at field.resolve, so a subscription with arguments was reported as missing even when subscribe was present. Query and mutation fields still require resolve.

  • Updated dependencies [7fbc6e7, 5ceed9d]:

v11.0.5

Compare Source

Patch Changes

v11.0.4

Compare Source

Patch Changes

v11.0.3

Compare Source

Patch Changes

v11.0.2

Compare Source

Patch Changes

v11.0.1

Compare Source

Patch Changes

v11.0.0

Compare Source

Major Changes

  • #​8515 1d70c62 Thanks @​ardatan! - Drop GraphQL v14/v15 support and require Node.js >= 22.18.

    • graphql peer range is now ^16.0.0 || ^17.0.0.
    • engines.node is now >=22.18.0 (Node fs.glob + Babel 8).
    • Dev tooling and @graphql-tools/graphql-tag-pluck move to Babel 8 (@babel/core / parser / traverse / types).
    • The standalone cross-inspect package is discontinued. Use inspect from @graphql-tools/utils instead (Node util.inspect via process.getBuiltinModule, with a small JSON.stringify / String fallback).
Removed @graphql-tools/utils exports
Removed Use instead
getArgumentValues import { getArgumentValues } from 'graphql'
coerceInputs / graphqlJSCompat graphql@​16+ APIs (getArgumentValues, etc.)
createDeferred / createDeferredPromise const { promise, resolve, reject } = Promise.withResolvers()
createGraphQLError new GraphQLError(message, options) from graphql
mapMaybePromise handleMaybePromise from @whatwg-node/promise-helpers
isPromise / fakePromise / mapAsyncIterator / MaybePromise @whatwg-node/promise-helpers
registerAbortSignalListener / getAbortPromise AbortSignal APIs (throwIfAborted, addEventListener('abort', …, { once: true }), AbortSignal.any, …)
withCancel / getAsyncIterableWithCancel / getAsyncIteratorWithCancel Handle cancellation on the async iterator’s return() (or your transport abort path)
debugTimerStart / debugTimerEnd Your own timing / console.time if needed
PromiseWithResolvers (type) Built-in PromiseWithResolvers<T> / return type of Promise.withResolvers()

inspect and the WeakMap memoize1…memoize2of5 helpers remain on @graphql-tools/utils (inspect is no longer re-exported from cross-inspect).

File matching (globby → fs.glob)

Loaders and @graphql-tools/load-files now use Node’s fs.glob through:

import { matchFiles, matchFilesSync } from '@graphql-tools/load-files';

Directory symlinks are followed for recursive (**) patterns:

  • On Node.js ≥26.1 (and ≥24.16 where backported), fs.glob followSymlinks is used.
  • On older engines, symlink directories are discovered only under each pattern’s literal prefix (not the whole cwd) and patterns are re-rooted.
  • Non-recursive / literal patterns skip the symlink walk entirely.

@graphql-tools/executor hot-path caches (collectSubfields, argument coercion, @stream detection) use memoize2 / memoize3 from utils. collectSubFields in utils stays unmemoized so the executor can own a single memoize3 layer.

Errors and other cleanup
  • Prefer new GraphQLError(message, options) from graphql. Experimental schema coordinate support remains on locatedError / relocatedError / getSchemaCoordinate.
  • Removed GraphQL versions older than 16 compatibility branches (error construction, validation rule name suffixes, URL.canParse fallback).
  • Promise helpers should be imported from @whatwg-node/promise-helpers (handleMaybePromise, isPromise, fakePromise, mapAsyncIterator, MaybePromise) rather than re-exported from utils.
Patch Changes

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

v10.1.3

Compare Source

Patch Changes

v10.1.2

Compare Source

Patch Changes

v10.1.1

Compare Source

Patch Changes

v10.1.0

Compare Source

Minor Changes

  • #​8346
    2273c21
    Thanks @​ardatan! - This release adds GraphQL v17 support and aligns
    the existing executor implementation with the latest GraphQL v17 API changes. The following
    changes are included:

    • getAsyncHelpers is now available on GraphQLResolveInfo. Its track method is used whenever
      waitUntil is available, as in Yoga's
      Explicit Resource Management
    • getAbortSignal is now available on GraphQLResolveInfo, matching behavior that was already
      available in this executor implementation, as in Yoga's
      Execution Cancellation
    • GraphQLResolveInfo automatically aligns variableValues according to the GraphQL version for
      better compatibility. In GraphQL v17 and above, variableValues follows the wrapped shape
      ({ coerced, sources }) expected by GraphQL APIs. In GraphQL v16 and below, variableValues
      remains a flat map as in previous versions.
    • If your custom scalar resolvers define __serialize and __parseValue, they are automatically
      mapped to coerceOutputValue and coerceInputValue in GraphQL v17.
    • BREAKING: @graphql-tools/executor's getVariableValues now returns { variableValues }
      on success, where variableValues is a VariableValues object ({ coerced, sources }). On
      failure, it returns { errors }.
    • BREAKING: collectFields, shouldIncludeNode, getDeferValues, and collectSubFields now
      need a VariableValues object instead of Record<string, any> for the variableValues
      argument.
    • visitResult now internally normalizes ExecutionRequest.variables into a
      VariableValues-compatible shape ({ coerced, sources }) before traversing selections.
Patch Changes

v10.0.38

Compare Source

Patch Changes

v10.0.37

Compare Source

Patch Changes

v10.0.36

Compare Source

Patch Changes

v10.0.35

Compare Source

Patch Changes

v10.0.34

Compare Source

Patch Changes

v10.0.33

Compare Source

Patch Changes

v10.0.32

Compare Source

Patch Changes

v10.0.31

Compare Source

Patch Changes

v10.0.30

Compare Source

Patch Changes

v10.0.29

Compare Source

Patch Changes

v10.0.28

Compare Source

Patch Changes

v10.0.27

Compare Source

Patch Changes

v10.0.26

Compare Source

Patch Changes

v10.0.25

Compare Source

Patch Changes

v10.0.24

Compare Source

Patch Changes
nestjs/graphql (@​nestjs/apollo)

v14.2.0

Compare Source

This release fixes several security issues and a range of correctness bugs in schema generation, resolver binding and the drivers. Upgrading is recommended for all users of @nestjs/graphql, @nestjs/apollo and @nestjs/mercurius.

Security

Advisory Severity Package Summary
GHSA-8www-f354-mh8p High @nestjs/graphql Unauthenticated requests can crash applications that enable GraphQL subscriptions
GHSA-f2pj-v3fc-65xp High @nestjs/graphql Guards, interceptors and pipes are silently skipped on resolvers registered with useFactory or useValue
GHSA-c658-2mxh-7pqx High @nestjs/graphql Guards of a subclass resolver can be bypassed when its base resolver is also registered
GHSA-m88h-g79w-v5mc Medium @nestjs/graphql DateTime and Timestamp scalars accept invalid input, so null and invalid dates reach non-null arguments
GHSA-qcfh-v6vh-p698 Medium @nestjs/mercurius MercuriusFederationDriver ignores subscription filters and delivers events to all subscribers
GHSA-fvxv-c29c-43xc Medium @nestjs/apollo Credentials of failed outgoing HTTP requests can be exposed in GraphQL error responses
GHSA-68rj-86jm-2jwh Medium @nestjs/graphql Guarded field resolvers can be dropped when the resolvers option defines the same type
GHSA-5mvw-93v2-cm4m Medium @nestjs/apollo, @nestjs/mercurius Context objects returned by a context function can be shared across requests
GHSA-9c65-35pp-rvj7 Medium @nestjs/graphql Subscription filters receive schema-named arguments, which can deliver other users' events
GHSA-5xqp-272w-2j3q Medium @nestjs/graphql Subscription resolve callbacks run without guards when the operation is sent over HTTP

Behaviour changes

Most applications need no changes. The fixes below either make silent misconfigurations fail loudly, or align runtime behaviour with what the schema and the documentation promise. Please review them before upgrading.

Startup errors for configurations that used to skip checks silently
  • Factory or value resolvers with class-referenced enhancers. A resolver registered with useFactory/useValue that uses guards, interceptors or pipes referenced by class now fails at startup; before, these enhancers never ran. Register the resolver as a class or with useClass, or pass enhancer instances.
  • Unattachable scoped enhancers and plugins. Request- or transient-scoped global enhancers that can't be attached to a resolver fail at startup, and so do request-scoped or transient @Plugin() classes.
  • Ambiguous handlers. Two unrelated classes (or two methods) resolving the same type and field fail at startup. A subclass overriding its parent is fine: the most-derived class wins.
  • Argument conflicts. These fail at schema build:
    • a renamed @ArgsType() property that collides with a named @Args();
    • the same argument declared in two @Args() with different types or defaults.
  • defaultValue: null on a non-null argument or field fails at schema build. Add nullable: true, or drop the default.
  • Extra required arguments. A @ResolveField() that adds a required argument the implemented interface field doesn't declare is a schema validation error.
  • isOneOf. Derived input types inherit isOneOf, and the @oneOf directive now sets it.
  • Ambiguous type names. Referencing a type by name (@Field(() => 'Name')) when two types share that name fails. Reference the class, or scope the types with registerIn.
  • MercuriusGatewayDriver with transformSchema fails at startup; the option used to be ignored.
  • Schema-first with both schema and typeDefs. resolverValidationOptions now apply to the merged schema.
Requests that are now rejected
  • Malformed dates. Malformed DateTime/Timestamp input is a validation error (HTTP 400). Valid date strings, Date instances and epoch-millisecond numbers keep working.
  • Custom scalars. A null result from a custom scalar's parseValue()/parseLiteral() is now treated as invalid input. Throw a GraphQLError for input your scalar can't parse.
  • Subscriptions over HTTP are refused by ApolloDriver, ApolloFederationDriver and MercuriusDriver. Use WebSocket.
  • Exact endpoint path on Express. The GraphQL endpoint matches its exact path: /graphql/<anything> returns 404, and path: '/' no longer catches every URL. A trailing slash still works.
  • 'graphql-ws': false now disables the WebSocket endpoint. A subscriptions object that enables no protocol no longer accepts upgrades.
  • IntersectionType(). A field shared by both classes is non-null unless both allow null.
  • graphql-ws operations now go through Apollo's validationRules and formatError.
  • Request start hooks. An async request start hook (ResolverDecoratorHost.setOnRequestStartHook()) is awaited, and if it rejects, the operation fails.
Schema changes
  • Renamed properties. A subclass that redeclares a property under another schema name no longer keeps the parent's field.
  • Mapped types. PickType(), OmitType(), PartialType() and IntersectionType() no longer include fields inherited from a parent of another kind (e.g. an @ObjectType() parent of an @InputType()).
  • @ResolveField() placement.
    • Field resolvers of a base resolver typed with a base or interface type appear only on the types actually served.
    • Handler-only fields no longer leak between include-scoped GraphQL modules.
  • include and @Global() modules. include no longer pulls in resolvers of @Global() modules; list them in include explicitly.
  • Undecorated overrides. An override of a handler that isn't decorated no longer produces a field.
  • Ordering.
    • Field order in the SDL can change for types that implement several interfaces.
    • Argument order for @ArgsType() chains three or more levels deep is now root-first.
  • Enums. Keys created by Infinity/NaN reverse mappings and namespace-merged members are no longer enum values.
  • CLI plugin.
    • It skips protected and #private members.
    • @HideField() also works when applied through a composed decorator.
  • Federation. Custom buildFederatedSchema callbacks receive only the __resolveReference resolvers; the other resolvers are attached separately.
Different resolvers or middleware for the same query
  • Object subtypes run the nearest ancestor's @ResolveField() handler, with its guards and middleware, instead of reading the property. To keep the old behaviour, declare a handler on the subtype.
  • Interfaces. When interfaces provide competing field resolvers, the most specific one wins, not the last one listed.
  • Model field middleware.
    • @Field({ middleware }) and @UseFieldMiddleware() on a model field also run when the field has a @ResolveField() handler, in the order global → model → handler, each once.
    • Global field middleware also runs on fields inherited from @InterfaceType() classes.
  • Unbound handler-only fields. A field declared only by a @ResolveField(), that ends up on a type with no bound handler, returns an error and is listed in a startup warning. Before, it read the parent's property unguarded.
  • __typename of subclasses. The default resolveType returns the most-derived class, so __typename names the subclass.
  • Bare @Resolver() subclasses inherit the parent's type.
  • Subscription/Mutation object types. @ResolveField() handlers on object types named Subscription or Mutation are treated as field resolvers.
  • Error conversion. Only real HttpException instances are converted to GraphQL errors.
  • Context objects. A context object returned by a context function is copied per request, so class contexts lose #private fields.
  • Defaults.
    • Omitted object argument defaults are completed with the input type's field defaults.
    • Array and object defaults are fresh copies on every request.
  • Class-level @Extensions() are inherited by subclasses.
  • directiveResolvers is deprecated and logs a warning. It has

[!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: 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

changeset-bot Bot commented Jul 20, 2025 •
edited
Loading

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 7cc49f2

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

@renovate
renovate Bot force-pushed the renovate/major-examples branch from 75151d7 to 3a364f2 Compare August 19, 2025 17:45
@codecov-commenter

codecov-commenter commented Aug 19, 2025 •
edited
Loading

Copy link
Copy Markdown

⚠️ Please install the 'codecov app svg image' 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 (0a8fdd6) to head (5f78420).
❗ Your organization needs to install the Codecov GitHub app to enable full functionality.

Additional details and impacted files 
@@           Coverage Diff           @@
##             main     #819   +/-   ##
=======================================
  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
renovate Bot force-pushed the renovate/major-examples branch from 77228e5 to cbd9ba1 Compare August 22, 2025 15:04
@renovate
renovate Bot force-pushed the renovate/major-examples branch from cbd9ba1 to 11f2045 Compare September 10, 2025 21:04
@renovate renovate Bot changed the title fix(deps): update dependency @apollo/server to v5 fix(deps): update examples (major) Sep 10, 2025
@renovate
renovate Bot force-pushed the renovate/major-examples branch from 11f2045 to 687fe14 Compare September 25, 2025 20:48
@renovate
renovate Bot force-pushed the renovate/major-examples branch from 687fe14 to 32318ce Compare October 15, 2025 15:45
@renovate
renovate Bot force-pushed the renovate/major-examples branch from 32318ce to 64b8606 Compare October 31, 2025 20:08
@renovate
renovate Bot force-pushed the renovate/major-examples branch from 64b8606 to 57b4500 Compare November 11, 2025 01:12
@renovate
renovate Bot force-pushed the renovate/major-examples branch 2 times, most recently from 37ec295 to 836348b Compare November 25, 2025 00:42
@renovate
renovate Bot force-pushed the renovate/major-examples branch from 836348b to 5a054c2 Compare December 3, 2025 14:47
@renovate
renovate Bot force-pushed the renovate/major-examples branch from 5a054c2 to 9f603be Compare December 27, 2025 18:02
@renovate renovate Bot changed the title fix(deps): update examples (major) fix(deps): update dependency ts-morph to v27 Dec 27, 2025
@renovate
renovate Bot force-pushed the renovate/major-examples branch from 9f603be to d903fe3 Compare December 31, 2025 17:04
@renovate
renovate Bot force-pushed the renovate/major-examples branch from d903fe3 to 2b58b75 Compare February 10, 2026 00:31
@renovate renovate Bot changed the title fix(deps): update dependency ts-morph to v27 fix(deps): update examples (major) Feb 10, 2026
@renovate
renovate Bot force-pushed the renovate/major-examples branch 2 times, most recently from 5be7caa to ec8cea7 Compare February 23, 2026 20:01
@renovate
renovate Bot force-pushed the renovate/major-examples branch 2 times, most recently from 65141a3 to 09c91d2 Compare March 5, 2026 17:22
@renovate
renovate Bot force-pushed the renovate/major-examples branch from 09c91d2 to 06862d9 Compare March 10, 2026 01:41
@renovate
renovate Bot force-pushed the renovate/major-examples branch 2 times, most recently from 4c8009b to 9ba7b19 Compare March 26, 2026 17:29
@renovate
renovate Bot force-pushed the renovate/major-examples branch 3 times, most recently from 59963a3 to e560bad Compare April 8, 2026 17:22
@renovate
renovate Bot force-pushed the renovate/major-examples branch 2 times, most recently from 62eae9e to 3dd04aa Compare April 20, 2026 01:59
@renovate

renovate Bot commented Jul 11, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor Author

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: yarn.lock
! Corepack is about to download https://repo.yarnpkg.com/4.9.2/packages/yarnpkg-cli/bin/yarn.js

@renovate
renovate Bot force-pushed the renovate/major-examples branch from 67df056 to ffddb8c Compare July 13, 2026 23:28
@renovate
renovate Bot force-pushed the renovate/major-examples branch from ffddb8c to 711f7b9 Compare July 27, 2026 22:14
@renovate
renovate Bot force-pushed the renovate/major-examples branch from 711f7b9 to 6642bdc Compare August 10, 2026 21:01
@renovate
renovate Bot force-pushed the renovate/major-examples branch 4 times, most recently from d79f61c to 7ee49ed Compare August 30, 2026 14:08
@renovate
renovate Bot force-pushed the renovate/major-examples branch from 7ee49ed to 0343a80 Compare September 8, 2026 00:38
@renovate
renovate Bot force-pushed the renovate/major-examples branch 6 times, most recently from c3ee414 to 689b839 Compare September 21, 2026 21:15
@renovate
renovate Bot force-pushed the renovate/major-examples branch 7 times, most recently from 91cfe5e to 2955ffd Compare October 1, 2026 17:53
@renovate
renovate Bot force-pushed the renovate/major-examples branch 2 times, most recently from 152ba74 to 4785896 Compare October 5, 2026 21:15
@renovate
renovate Bot force-pushed the renovate/major-examples branch 3 times, most recently from 52ad30f to af874b7 Compare October 22, 2026 15:53
@renovate
renovate Bot force-pushed the renovate/major-examples branch 2 times, most recently from 21f8f8d to a1e527b Compare October 23, 2026 18:52

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

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

@codecov-commenter