chore(deps): update dependency knip to v6 (feature/beta-release)

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
knip (source)	^5.88.1 → ^6.0.0

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

webpro-nl/knip (knip)

v6.0.0: Release 6.0.0

Compare Source

Blog post: Announcing Knip v6

See the pre-releases for details:

• https://github.com/webpro-nl/knip/releases/tag/knip%406.0.0-0
• https://github.com/webpro-nl/knip/releases/tag/knip%406.0.0-1
• https://github.com/webpro-nl/knip/releases/tag/knip%406.0.0-2
• https://github.com/webpro-nl/knip/releases/tag/knip%406.0.0-3

Breaking changes:

• Dropped support for Node.js v18 → Knip v6 requires Node.js v20.19.0 or newer
• Dropped issue type classMembers
• Dropped --include-libs → this is now the default and only behavior
• Dropped --isolate-workspaces → this is now the default and only behavior
• Dropped --experimental-tags → use --tags
• In reporter functions, issues.files is consistent with other issue shapes. Removed issues._files.
• In the JSON reporter, issues are consistently arrays for any issue type. Removed root files.

---

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.

[github-advanced-security]

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

• The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
• Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
• You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

[github-actions]

⚠️ Supply Chain Verification Results

⚠️ WARNING

📦 SBOM Summary

• Components: 1483

🔍 Vulnerability Scan

Severity	Count
🔴 Critical	0
🟠 High	2
🟡 Medium	4
🟢 Low	2
Total	8

📎 Artifacts

• SBOM (CycloneDX JSON) and Grype results available in workflow artifacts

---

_{Generated by Supply Chain Verification workflow • View Details}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!