Skip to content

chore(deps): update dependency nock to v13.5.6#1427

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/nock-13.x
Open

chore(deps): update dependency nock to v13.5.6#1427
renovate[bot] wants to merge 1 commit intomainfrom
renovate/nock-13.x

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Nov 11, 2024

This PR contains the following updates:

Package Change Age Confidence
nock 13.5.513.5.6 age confidence

Release Notes

nock/nock (nock)

v13.5.6

Compare Source

Bug Fixes

Configuration

📅 Schedule: 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 is behind base branch, 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 requested a review from a team as a code owner November 11, 2024 12:08
@renovate renovate bot force-pushed the renovate/nock-13.x branch 2 times, most recently from 543a065 to 5564d58 Compare November 15, 2024 15:30
@renovate renovate bot force-pushed the renovate/nock-13.x branch 3 times, most recently from fefd639 to ad56121 Compare November 25, 2024 16:10
@renovate renovate bot force-pushed the renovate/nock-13.x branch from ad56121 to ad90fc2 Compare December 10, 2024 13:53
@renovate renovate bot force-pushed the renovate/nock-13.x branch 4 times, most recently from 64f9c59 to 762724a Compare December 23, 2024 12:34
@renovate renovate bot force-pushed the renovate/nock-13.x branch 2 times, most recently from a3910c8 to ee9d65a Compare January 6, 2025 13:23
@renovate renovate bot force-pushed the renovate/nock-13.x branch 8 times, most recently from f6ad1d2 to 2ff6b85 Compare January 22, 2025 09:36
@renovate renovate bot force-pushed the renovate/nock-13.x branch 4 times, most recently from da111aa to 8b229b9 Compare February 4, 2025 08:40
@renovate renovate bot force-pushed the renovate/nock-13.x branch 5 times, most recently from ddd4fb5 to 8c4ea31 Compare February 20, 2025 14:06
@renovate renovate bot changed the title chore(deps): update dependency nock to v13.5.6 Update dependency nock to v13.5.6 May 12, 2025
@renovate renovate bot force-pushed the renovate/nock-13.x branch 10 times, most recently from 92a9902 to 00aaa39 Compare May 14, 2025 17:22
@renovate renovate bot changed the title Update dependency nock to v13.5.6 chore(deps): update dependency nock to v13.5.6 May 14, 2025
@renovate renovate bot force-pushed the renovate/nock-13.x branch from 00aaa39 to c9bf123 Compare May 26, 2025 11:51
@renovate renovate bot changed the title chore(deps): update dependency nock to v13.5.6 Update dependency nock to v13.5.6 May 26, 2025
@renovate renovate bot force-pushed the renovate/nock-13.x branch 2 times, most recently from c01ab25 to 9b16778 Compare June 2, 2025 15:45
@renovate renovate bot force-pushed the renovate/nock-13.x branch 4 times, most recently from 48704eb to 39d97e6 Compare June 10, 2025 12:32
@renovate renovate bot force-pushed the renovate/nock-13.x branch 6 times, most recently from d441b7a to f1b98b8 Compare June 18, 2025 08:34
@renovate renovate bot force-pushed the renovate/nock-13.x branch from f1b98b8 to a1a10af Compare June 24, 2025 11:37
@sonarqubecloud
Copy link

@renovate
Copy link
Contributor Author

renovate bot commented Dec 19, 2025

⚠️ 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 warn Unknown env config "store". This will stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: ts-auto-mock@3.7.4
npm error Found: typescript@4.9.5
npm error node_modules/typescript
npm error   dev typescript@"4.9.5" from the root project
npm error   peer typescript@">=3.8 <5.0" from ts-jest@27.1.5
npm error   node_modules/ts-jest
npm error     dev ts-jest@"^27.0.4" from the root project
npm error   3 more (ts-loader, tsutils, ttypescript)
npm error
npm error Could not resolve dependency:
npm error peer typescript@"^5.0.4" from ts-auto-mock@3.7.4
npm error node_modules/ts-auto-mock
npm error   dev ts-auto-mock@"^3.3.5" from the root project
npm error   peer ts-auto-mock@"^3.5.0" from jest-ts-auto-mock@2.1.0
npm error   node_modules/jest-ts-auto-mock
npm error     dev jest-ts-auto-mock@"^2.0.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.0.4" from ts-auto-mock@3.7.4
npm error   node_modules/ts-auto-mock
npm error     dev ts-auto-mock@"^3.3.5" from the root project
npm error     peer ts-auto-mock@"^3.5.0" from jest-ts-auto-mock@2.1.0
npm error     node_modules/jest-ts-auto-mock
npm error       dev jest-ts-auto-mock@"^2.0.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error 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-03-06T08_20_26_788Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-03-06T08_20_26_788Z-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