chore(deps): update dependency clean-publish to v7

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
clean-publish	^5.0.0 → ^7.0.0

---

Release Notes

shashkovdanil/clean-publish (clean-publish)

v7.1.0

Compare Source

• Added --stage support (by @​43081j).

v7.0.1

Compare Source

• Fixed npm package size regression.

v7.0.0

Compare Source

• Added pnpm-workspace.yaml to ignore files.
• Removed Node.js 20 support.

v6.0.5

Compare Source

• Ignore oxfmt and oxlint configs.

v6.0.4

Compare Source

• Ignore .prettierignore file.

v6.0.3

Compare Source

• Added pnpm to ignore package.json fields.

v6.0.2

Compare Source

• Ignore .claude folder.

v6.0.1

Compare Source

• Fixed CLI calls (by @​hyperz111).

v6.0.0

Compare Source

• Removed Node.js 18 support.
• Reduced dependencies (by @​hyperz111).

---

Configuration

📅 Schedule: (UTC)

• 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.

[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: pnpm-lock.yaml

Scope: all 9 workspace projects
? Verifying lockfile against supply-chain policies (743 entries)...
✗ Lockfile failed supply-chain policy check (743 entries in 5.9s)
[ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 29 lockfile entries failed verification:
  @oxlint/binding-android-arm-eabi@1.68.0 was published at 2026-06-01T17:06:31.000Z, within the minimumReleaseAge cutoff (2026-05-31T22:31:43.155Z)
  @oxlint/binding-android-arm64@1.68.0 was published at 2026-06-01T17:06:00.000Z, within the minimumReleaseAge cutoff (2026-05-31T22:31:43.155Z)
  @oxlint/binding-darwin-arm64@1.68.0 was published at 2026-06-01T17:05:55.000Z, within the minimumReleaseAge cutoff (2026-05-31T22:31:43.155Z)
  @oxlint/binding-darwin-x64@1.68.0 was published at 2026-06-01T17:07:19.000Z, within the minimumReleaseAge cutoff (2026-05-31T22:31:43.155Z)
  @oxlint/binding-freebsd-x64@1.68.0 was published at 2026-06-01T17:07:30.000Z, within the minimumReleaseAge cutoff (2026-05-31T22:31:43.155Z)
  @oxlint/binding-linux-arm-gnueabihf@1.68.0 was published at 2026-06-01T17:06:37.000Z, within the minimumReleaseAge cutoff (2026-05-31T22:31:43.155Z)
  @oxlint/binding-linux-arm-musleabihf@1.68.0 was published at 2026-06-01T17:06:43.000Z, within the minimumReleaseAge cutoff (2026-05-31T22:31:43.155Z)
  @oxlint/binding-linux-arm64-gnu@1.68.0 was published at 2026-06-01T17:06:13.000Z, within the minimumReleaseAge cutoff (2026-05-31T22:31:43.155Z)
  @oxlint/binding-linux-arm64-musl@1.68.0 was published at 2026-06-01T17:06:19.000Z, within the minimumReleaseAge cutoff (2026-05-31T22:31:43.155Z)
  @oxlint/binding-linux-ppc64-gnu@1.68.0 was published at 2026-06-01T17:06:55.000Z, within the minimumReleaseAge cutoff (2026-05-31T22:31:43.155Z)
  @oxlint/binding-linux-riscv64-gnu@1.68.0 was published at 2026-06-01T17:07:01.000Z, within the minimumReleaseAge cutoff (2026-05-31T22:31:43.155Z)
  @oxlint/binding-linux-riscv64-musl@1.68.0 was published at 2026-06-01T17:07:06.000Z, within the minimumReleaseAge cutoff (2026-05-31T22:31:43.155Z)
  @oxlint/binding-linux-s390x-gnu@1.68.0 was published at 2026-06-01T17:07:13.000Z, within the minimumReleaseAge cutoff (2026-05-31T22:31:43.155Z)
  @oxlint/binding-linux-x64-gnu@1.68.0 was published at 2026-06-01T17:07:38.000Z, within the minimumReleaseAge cutoff (2026-05-31T22:31:43.155Z)
  @oxlint/binding-linux-x64-musl@1.68.0 was published at 2026-06-01T17:07:45.000Z, within the minimumReleaseAge cutoff (2026-05-31T22:31:43.155Z)
  @oxlint/binding-openharmony-arm64@1.68.0 was published at 2026-06-01T17:06:25.000Z, within the minimumReleaseAge cutoff (2026-05-31T22:31:43.155Z)
  @oxlint/binding-win32-arm64-msvc@1.68.0 was published at 2026-06-01T17:06:06.000Z, within the minimumReleaseAge cutoff (2026-05-31T22:31:43.155Z)
  @oxlint/binding-win32-ia32-msvc@1.68.0 was published at 2026-06-01T17:06:48.000Z, within the minimumReleaseAge cutoff (2026-05-31T22:31:43.155Z)
  @oxlint/binding-win32-x64-msvc@1.68.0 was published at 2026-06-01T17:07:25.000Z, within the minimumReleaseAge cutoff (2026-05-31T22:31:43.155Z)
  @vitest/expect@4.1.8 was published at 2026-06-01T08:14:36.000Z, within the minimumReleaseAge cutoff (2026-05-31T22:31:43.155Z)
  …and 9 more

The lockfile contains entries that the active policies reject. This can mean the lockfile is stale, or that someone committed a lockfile that bypassed the policy locally — inspect recent changes to pnpm-lock.yaml before trusting it. If the changes look expected, run "pnpm clean --lockfile" and then "pnpm install" to rebuild from a fresh resolution. Alternatively, relax the policy that flagged them.