chore(deps): update dependency nock to v14.0.10

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
nock	14.0.4 -> 14.0.10

---

Release Notes

nock/nock (nock)

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

• address timeout issue with mocked timers (Revert #​2880) (#​2902) (bc48f92)

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

• address timeout issue with mocked timers (#​2880) (fb112f3)

v14.0.6

Compare Source

Bug Fixes

• upgrade interceptors (2bcaf0f)

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)

---

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

⚠️ 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: [email protected]
npm error Found: [email protected]
npm error node_modules/express
npm error   express@"^5.0.0" from the root project
npm error   express@"^5.0.0" from [email protected]
npm error   node_modules/probot
npm error     probot@"^13.3.9" from the root project
npm error
npm error Could not resolve dependency:
npm error peer express@"4.x" from [email protected]
npm error node_modules/express-prometheus-middleware
npm error   express-prometheus-middleware@"^1.2.0" from the root project
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/express
npm error   peer express@"4.x" from [email protected]
npm error   node_modules/express-prometheus-middleware
npm error     express-prometheus-middleware@"^1.2.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/2025-09-25T16_13_19_244Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-09-25T16_13_19_244Z-debug-0.log

[semanticdiff-com]

Review changes with  

Changed Files

File	Status
package.json	0% smaller

[restack-app]

No applications have been configured for previews targeting branch: master. To do so go to restack console and configure your applications for previews.

[instapr]

Feedback

The PR looks good. The nock dependency has been successfully updated from 14.0.4 to 14.0.5. The package.json file has been updated accordingly.

Great job! 🚀

[coderabbitai]

Important

Review skipped

Bot user detected.

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

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Join our Discord community for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[pr-code-reviewer]

👋 Hi there!

Everything looks good!

_{^{Automatically generated with the help of gpt-3.5-turbo.
Feedback? Please don't hesitate to drop me an email at [email protected].}}

[pr-code-reviewer]

👋 Hi there!

1. Ensure the version of "nock" is updated from "14.0.4" to "14.0.6".
2. Consider updating Jest from "^29.0.0" to a newer stable version for potential enhancements or bug fixes.
3. Review other dependencies for possible updates that could improve performance, security, or features.

_{^{Automatically generated with the help of gpt-3.5-turbo.
Feedback? Please don't hesitate to drop me an email at [email protected].}}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[mergeable]

⚠️

Please add Jira ticket id i.e. "JIRA-ID"

Check Fail Adhere to the branch naming convention described here