Skip to content

chore(deps): update dependency @types/node to v26.6.4 - #112

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/node-26.x-lockfile
Open

renovate[bot] wants to merge 1 commit into
mainfrom
renovate/node-26.x-lockfile

Conversation

@renovate

@renovate renovate Bot commented Sep 27, 2026 •

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
@types/node (source) 26.6.3 → 26.6.4 age confidence

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


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.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


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

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

@renovate

renovate Bot commented Sep 27, 2026 •

Copy link
Copy Markdown
Contributor Author

⚠️ Artifact update problem

Renovate failed to update artifacts 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: examples/shop/cart/package-lock.json
npm warn Unknown env config "store". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: openapi-typescript@7.13.0
npm error Found: typescript@7.0.2
npm error node_modules/typescript
npm error   peer typescript@"*" from @typescript/vfs@1.6.5
npm error   node_modules/@typescript/vfs
npm error     @typescript/vfs@"^1.6.2" from @bufbuild/protoplugin@2.16.0
npm error     node_modules/@bufbuild/protoplugin
npm error       @bufbuild/protoplugin@"2.16.0" from @bufbuild/protoc-gen-es@2.16.0
npm error       node_modules/@bufbuild/protoc-gen-es
npm error         dev @bufbuild/protoc-gen-es@"^2.16.0" from the root project
npm error   dev typescript@"^7.0.2" from the root project
npm error
npm error Could not resolve dependency:
npm error peer typescript@"^5.x" from openapi-typescript@7.13.0
npm error node_modules/openapi-typescript
npm error   dev openapi-typescript@"^7.13.0" from the root project
npm error
npm error Conflicting peer dependency: typescript@5.9.3
npm error node_modules/typescript
npm error   peer typescript@"^5.x" from openapi-typescript@7.13.0
npm error   node_modules/openapi-typescript
npm error     dev openapi-typescript@"^7.13.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-10-02T01_45_16_267Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-10-02T01_45_16_267Z-debug-0.log

File name: examples/bff/package-lock.json
npm warn Unknown env config "store". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: openapi-typescript@7.13.0
npm error Found: typescript@7.0.2
npm error node_modules/typescript
npm error   peerOptional typescript@">=4.9.5" from cosmiconfig@8.3.6
npm error   node_modules/@graphql-codegen/cli/node_modules/graphql-config/node_modules/cosmiconfig
npm error     cosmiconfig@"^8.1.0" from graphql-config@5.1.6
npm error     node_modules/@graphql-codegen/cli/node_modules/graphql-config
npm error       graphql-config@"^5.1.6" from @graphql-codegen/cli@7.4.3
npm error       node_modules/@graphql-codegen/cli
npm error         dev @graphql-codegen/cli@"^7.4.3" from the root project
npm error   peer typescript@"*" from @typescript/vfs@1.6.5
npm error   node_modules/@typescript/vfs
npm error     @typescript/vfs@"^1.6.2" from @bufbuild/protoplugin@2.16.0
npm error     node_modules/@bufbuild/protoplugin
npm error       @bufbuild/protoplugin@"2.16.0" from @bufbuild/protoc-gen-es@2.16.0
npm error       node_modules/@bufbuild/protoc-gen-es
npm error         dev @bufbuild/protoc-gen-es@"^2.16.0" from the root project
npm error   2 more (cosmiconfig, the root project)
npm error
npm error Could not resolve dependency:
npm error peer typescript@"^5.x" from openapi-typescript@7.13.0
npm error node_modules/openapi-typescript
npm error   dev openapi-typescript@"^7.13.0" from the root project
npm error
npm error Conflicting peer dependency: typescript@5.9.3
npm error node_modules/typescript
npm error   peer typescript@"^5.x" from openapi-typescript@7.13.0
npm error   node_modules/openapi-typescript
npm error     dev openapi-typescript@"^7.13.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-10-02T01_45_17_827Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-10-02T01_45_17_827Z-debug-0.log

@github-actions

Copy link
Copy Markdown

No architectural change against origin/main.

@renovate
renovate Bot force-pushed the renovate/node-26.x-lockfile branch 3 times, most recently from 102c6c5 to 55bf5f8 Compare October 1, 2026 08:56
@renovate renovate Bot changed the title chore(deps): update dependency @types/node to v26.6.3 chore(deps): update dependency @types/node to v26.6.3 - autoclosed Oct 1, 2026
@renovate renovate Bot closed this Oct 1, 2026
@renovate
renovate Bot deleted the renovate/node-26.x-lockfile branch October 1, 2026 13:32
@renovate renovate Bot changed the title chore(deps): update dependency @types/node to v26.6.3 - autoclosed chore(deps): update dependency @types/node to v26.6.4 Oct 2, 2026
@renovate renovate Bot reopened this Oct 2, 2026
@renovate
renovate Bot force-pushed the renovate/node-26.x-lockfile branch from 55bf5f8 to 7d9dd54 Compare October 2, 2026 01:45

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants