Skip to content

Comments

chore(deps): update dependency nock to v14.0.11#227

Open
pactflow-renovate-bot[bot] wants to merge 1 commit intomasterfrom
renovate/nock-14.x
Open

chore(deps): update dependency nock to v14.0.11#227
pactflow-renovate-bot[bot] wants to merge 1 commit intomasterfrom
renovate/nock-14.x

Conversation

@pactflow-renovate-bot
Copy link
Contributor

This PR contains the following updates:

Package Change Age Confidence
nock 14.0.1014.0.11 age confidence

Release Notes

nock/nock (nock)

v14.0.11

Compare Source

Bug Fixes

v14.0.10

Compare Source

Bug Fixes
  • Use Error objects instead of plain objects with replyWithError() (#​2900) (f2a3389)

v14.0.9

Compare Source

Bug Fixes

v14.0.8

Compare Source

Bug Fixes
  • ClientRequest: support http.Agent instances as agents for https requests (#​2896) (e4390b8)

v14.0.7

Compare Source

Bug Fixes

v14.0.6

Compare Source

Bug Fixes

v14.0.5

Compare Source

Bug Fixes
  • use of a fetch() recording that uses gzip compression is missing the headers, Possible EventEmitter memory leak when used together with MongoDBContainer (#​2869) (90b2a04)

v14.0.4

Compare Source

Bug Fixes

v14.0.3

Compare Source

Bug Fixes

v14.0.2

Compare Source

Bug Fixes

Configuration

📅 Schedule: 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.

🔕 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 has been generated by Renovate Bot.

@pactflow-renovate-bot
Copy link
Contributor Author

pactflow-renovate-bot bot commented Feb 12, 2026

⚠️ 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: package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: consumer@0.1.0
npm ERR! Found: eslint@6.8.0
npm ERR! node_modules/eslint
npm ERR!   dev eslint@"6.8.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer eslint@"^8.57.0 || ^9.0.0" from @typescript-eslint/parser@8.54.0
npm ERR! node_modules/@typescript-eslint/parser
npm ERR!   dev @typescript-eslint/parser@"8.54.0" from the root project
npm ERR!   peer @typescript-eslint/parser@"^8.54.0" from @typescript-eslint/eslint-plugin@8.54.0
npm ERR!   node_modules/@typescript-eslint/eslint-plugin
npm ERR!     dev @typescript-eslint/eslint-plugin@"8.54.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /var/cache/renovate/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /var/cache/renovate/others/npm/_logs/2026-02-15T22_57_14_275Z-debug-0.log

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