Bump tmp from 0.2.4 to 0.2.6

[dependabot]

Bumps tmp from 0.2.4 to 0.2.6.

Commits

• 41f7159 Bump up the version
• efa4a06 Merge commit from fork
• 7ef2728 Check for relative values
• 3d2fe38 Bump up the version
• e162828 Merge pull request #309 from fflorent/fix-tmp-dir-with-dir
• b847d2f Fix use of tmp.dir() with dir option
• 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 this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[n-lark]

tmp 0.2.4 → 0.2.6 — packages/flowfuse

TL;DR: transitive of cypress only (dev/test scope, never ships to prod). This bump closes GHSA-ph9p-34f9-6g65 — HIGH-sev path traversal via unsanitized prefix/postfix. Current 0.2.4 is vulnerable. Safe to merge.

Standard gates

• Scope: transitive via cypress@15.14.2 → tmp only; not in any package.json dependencies/devDependencies and not imported by our forge/, frontend/, or ee/ code
• Cypress allows it: cypress declares tmp: "~0.2.4" which covers 0.2.6
• Diff: lockfile only (and 2 unrelated workflow lines from main being ahead)
• Published >12h ago (2026-05-26, ~42h); latest tag is 0.2.7 (see note below)
• Real CVE fix: GHSA-ph9p-34f9-6g65, HIGH, path traversal, <0.2.6 vulnerable, fixed in 0.2.6
• No new GHSA against 0.2.6 itself
• Local install + smoke: tmp@0.2.6 loads, exports match
• CI green on PR
• No conflicting Dependabot PR on same lockfile

Note: 0.2.7 is now latest

• 0.2.7 shipped 2026-05-27 (~22h ago) with hardening commits (Reject non-string prefix, postfix, template + Merge commit from fork) — looks like defense-in-depth on the same area as 0.2.6's CVE.
• No GHSA against 0.2.6 yet, so 0.2.7 isn't a published security fix.
• Dependabot hasn't opened a 0.2.7 PR yet; it will on its next scan cycle.
• Recommendation: merge 0.2.6 now to close the HIGH CVE. Comment @dependabot recreate (or just close + reopen) when the 0.2.7 PR appears, then merge it as a routine patch.