chore(deps): update dependency tmp-promise to v3.0.3

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
tmp-promise	3.0.2 -> 3.0.3

---

Release Notes

benjamingr/tmp-promise (tmp-promise)

v3.0.3

Compare Source

---

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 Mend Renovate. View repository job log here.

[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 ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: vis-dev-utils@4.0.45
npm ERR! Found: tmp-promise@3.0.3
npm ERR! node_modules/tmp-promise
npm ERR!   dev tmp-promise@"3.0.3" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer tmp-promise@"3.0.2" from vis-dev-utils@4.0.45
npm ERR! node_modules/vis-dev-utils
npm ERR!   dev vis-dev-utils@"4.0.45" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: tmp-promise@3.0.2
npm ERR! node_modules/tmp-promise
npm ERR!   peer tmp-promise@"3.0.2" from vis-dev-utils@4.0.45
npm ERR!   node_modules/vis-dev-utils
npm ERR!     dev vis-dev-utils@"4.0.45" 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! 
npm ERR! For a full report see:
npm ERR! /tmp/renovate/cache/others/npm/_logs/2024-04-12T03_49_13_444Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-04-12T03_49_13_444Z-debug-0.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 error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: vis-dev-utils@4.0.45
npm error Found: tmp-promise@3.0.3
npm error node_modules/tmp-promise
npm error   dev tmp-promise@"3.0.3" from the root project
npm error
npm error Could not resolve dependency:
npm error peer tmp-promise@"3.0.2" from vis-dev-utils@4.0.45
npm error node_modules/vis-dev-utils
npm error   dev vis-dev-utils@"4.0.45" from the root project
npm error
npm error Conflicting peer dependency: tmp-promise@3.0.2
npm error node_modules/tmp-promise
npm error   peer tmp-promise@"3.0.2" from vis-dev-utils@4.0.45
npm error   node_modules/vis-dev-utils
npm error     dev vis-dev-utils@"4.0.45" 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 /tmp/renovate/cache/others/npm/_logs/2024-05-22T15_22_17_208Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-05-22T15_22_17_208Z-debug-0.log