Update dependency autoprefixer to v10.5.2

[amitsingh-007]

This PR contains the following updates:

Package	Change	Age	Confidence
autoprefixer	10.5.0 → 10.5.2

---

Release Notes

postcss/autoprefixer (autoprefixer)

v10.5.2

Compare Source

• Moved -webkit-fill-available before -moz-available, so Firefox
  will use -webkit- version which is closer to stretch.

v10.5.1

Compare Source

• Fixed grid-area span reset for overriding areas (by @​puneetdixit200).

---

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 is an automated Renovate PR bumping autoprefixer from 10.5.0 to 10.5.2 in the shared pnpm catalog. The lock file is updated to reflect the new version along with its transitive dependencies (browserslist, caniuse-lite, electron-to-chromium, node-releases, baseline-browser-mapping).

• The autoprefixer 10.5.1 release fixed a grid-area span reset bug for overriding areas, and 10.5.2 corrects the ordering of -webkit-fill-available vs -moz-available prefixes so Firefox falls back to the closer-to-spec -webkit- variant.
• All lock file changes are internally consistent — every transitive dependency hash, resolution, and snapshot is correctly updated to match the new version.

Confidence Score: 5/5

Routine patch bump of a CSS tooling dependency with no functional changes to application code; safe to merge.

Only pnpm-workspace.yaml and pnpm-lock.yaml are touched. The upgrade is a two-patch-version jump in a CSS post-processing tool with well-scoped bug fixes. Transitive dependency hashes are all consistent. No application logic, configuration, or API surface is affected.

No files require special attention.

_{Reviews (1): Last reviewed commit: "Update dependency autoprefixer to v10.5...." | Re-trigger Greptile}

[qodo-code-review]

PR Summary by Qodo

Bump autoprefixer to 10.5.2 (pnpm catalog + lockfile)

⚙️ Configuration changes 🕐 Less than 10 minutes

AI Description

• Bump autoprefixer from 10.5.0 to 10.5.2 in the pnpm catalog.
• Regenerate pnpm lockfile to capture autoprefixer and related transitive updates.
• Record updated dependency metadata (including new deprecation markers) in the lockfile.

Diagram

graph TD
  workspace["pnpm-workspace.yaml"] --> lock["pnpm-lock.yaml"] --> autop["autoprefixer 10.5.2"] --> bl["browserslist 4.28.5"] --> cl["caniuse-lite 1.0.30001803"]
  bl --> nr["node-releases 2.0.50"]
  bl --> etc["electron-to-chromium 1.5.388"]
  bl --> bbm["baseline-browser-mapping 2.10.42"]

Loading

High-Level Assessment

The straightforward catalog bump + lockfile regeneration is the appropriate approach for a patch-level autoprefixer update; alternatives (e.g., pinning transitive versions or deferring lock updates) add maintenance overhead without clear benefit for this change.

Files changed (2) +53 / -9

Other (2) +53 / -9

pnpm-lock.yamlLock autoprefixer 10.5.2 and refresh Browserslist transitive set +52/-8

Lock autoprefixer 10.5.2 and refresh Browserslist transitive set

• Updates the resolved autoprefixer version from 10.5.0 to 10.5.2 and refreshes the corresponding snapshot entry. Pulls in updated transitive packages (e.g., browserslist, caniuse-lite, electron-to-chromium, node-releases, baseline-browser-mapping) and records new deprecation markers for some packages during lockfile regeneration.

pnpm-lock.yaml

pnpm-workspace.yamlBump autoprefixer version in pnpm catalog +1/-1

Bump autoprefixer version in pnpm catalog

• Updates the workspace catalog entry for autoprefixer from 10.5.0 to 10.5.2 so all workspaces resolve the new patch release.

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