Update dependency filenamify to v7.0.2

[amitsingh-007]

This PR contains the following updates:

Package	Change	Age	Confidence
filenamify	7.0.1 → 7.0.2

---

Release Notes

sindresorhus/filenamify (filenamify)

v7.0.2

Compare Source

• Fix handling of Windows reserved names with extensions (#​46) faae880

---

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • Between 12:00 AM and 03:59 AM, on day 1 of the month (* 0-3 1 * *)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ 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 has been generated by Mend Renovate.

Greptile Summary

This PR bumps the filenamify dependency from 7.0.1 to 7.0.2, a patch release that fixes handling of Windows reserved names with extensions. The change is reflected in both the catalog entry in pnpm-workspace.yaml and the generated lockfile.

• The integrity hash in pnpm-lock.yaml is correctly updated for 7.0.2, and the transitive dependency (filename-reserved-regex@4.0.0) and engine constraint (node: >=20) remain unchanged.
• The lockfile diff also surfaces deprecation notices for two pre-existing packages (stream-to-promise@2.2.0 and tsconfck@3.1.6); these are not introduced by this PR — pnpm added the metadata during the resolution refresh.

Confidence Score: 5/5

Safe to merge — this is a minimal patch-version bump with no API changes and a well-scoped bug fix.

The change is limited to updating filenamify from 7.0.1 to 7.0.2 across the workspace catalog and lockfile. The patch release only fixes Windows reserved-name handling, transitive dependencies and engine requirements are unchanged, and the integrity hash in the lockfile is correctly updated.

No files require special attention.

_{Reviews (1): Last reviewed commit: "Update dependency filenamify to v7.0.2" | Re-trigger Greptile}

[qodo-code-review]

PR Summary by Qodo

Bump filenamify dependency to v7.0.2

⚙️ Configuration changes 🕐 Less than 10 minutes

AI Description

• Update filenamify from 7.0.1 to 7.0.2 in the pnpm catalog.
• Regenerate pnpm lockfile entries to reflect the resolved filenamify@7.0.2 package.
• Pull in updated lock metadata (new deprecation markers) from the refreshed resolution.

Diagram

graph TD
  Dev(("Renovate/Dev")) --> WS["pnpm-workspace.yaml"] --> Lock["pnpm-lock.yaml"] --> CI["CI: pnpm install"] --> Reg{{"npm registry"}}
  CI --> Lock

  subgraph Legend
    direction LR
    _actor(("Actor")) ~~~ _file["Config/Lock file"] ~~~ _proc["Process"] ~~~ _ext{{"External"}}
  end

Loading

High-Level Assessment

Current approach (Renovate-driven catalog bump plus lockfile refresh) is the standard and lowest-risk way to apply a patch-level dependency update. Alternatives (manual lock edits, skipping lock regeneration) were implicitly considered and dismissed because they reduce reproducibility and increase the chance of inconsistent installs.

Files changed (2) +9 / -7

Other (2) +9 / -7

pnpm-lock.yamlUpdate filenamify lock entry to 7.0.2 +8/-6

Update filenamify lock entry to 7.0.2

• Updates the resolved filenamify package from 7.0.1 to 7.0.2, including integrity hash changes and snapshot entry rename. Also records new deprecation metadata surfaced during lockfile regeneration.

pnpm-lock.yaml

pnpm-workspace.yamlBump filenamify catalog version to 7.0.2 +1/-1

Bump filenamify catalog version to 7.0.2

• Updates the workspace catalog pin for filenamify from 7.0.1 to 7.0.2 so all importers using the catalog resolve the new patch version.

pnpm-workspace.yaml

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)

Great, no issues found!

Qodo reviewed your code and found no material issues that require review