Bump tmp from 0.2.5 to 0.2.7 in the npm_and_yarn group across 1 directory

[dependabot]

Bumps the npm_and_yarn group with 1 update in the / directory: tmp.

Updates tmp from 0.2.5 to 0.2.7

Commits

• 8ea1f37 Bump up the version
• 8f24f78 Merge commit from fork
• ce787f3 Reject non-string prefix, postfix, template
• 41f7159 Bump up the version
• efa4a06 Merge commit from fork
• 7ef2728 Check for relative values
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[mergify]

Merge Queue Status

• ✅ Entered queue — 2026-05-28 02:54 UTC · Rule: branchProtection
• ✅ Checks started · on draft merge queue: embarking main (08e88f1) and #2428 together #2429
• ❌ Checks failed
• 🚫 Left the queue — 2026-05-28 08:57 UTC · at 55c97e97d94ea3939ec64bc3d6fbfdc81b6501d4

This pull request spent 6 hours 2 minutes 5 seconds in the queue, including 6 hours 1 minute 41 seconds running CI.

Waiting for any of

• check-neutral = Lint & Test
• check-skipped = Lint & Test
• check-success = Lint & Test

All conditions

• any of [🛡 GitHub branch protection]:
  • check-neutral = Lint & Test
  • check-skipped = Lint & Test
  • check-success = Lint & Test
• #review-threads-unresolved = 0 [🛡 GitHub branch protection]
  • Bump tmp from 0.2.5 to 0.2.7 in the npm_and_yarn group across 1 directory #2428
• -merged
  • Bump tmp from 0.2.5 to 0.2.7 in the npm_and_yarn group across 1 directory #2428

Reason

The merge conditions cannot be satisfied due to failing checks

Failing checks:

• 🛑 Lint & Test (job log)
• 🛑 Lint & Test (job log)

Hint

You may have to fix your CI before adding the pull request to the queue again.
If you update this pull request, to fix the CI, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio queue comment.