chore(deps-dev): bump postcss from 8.5.15 to 8.5.23

[dependabot]

Bumps postcss from 8.5.15 to 8.5.23.

Release notes

Sourced from postcss's releases.

8.5.23

• Do not load source map without opts.from for security reasons.

8.5.22

• Fixed custom property losing semicolon before a comment (by @​sarathfrancis90).

8.5.21

• Fixed childless at-rule losing semicolon before comment (by @​sarathfrancis90).
• Fixed docs (by @​isker).

8.5.20

• Fixed missing space if AtRule#params is set after (by @​sarathfrancis90).
• Fixed mixing AST error on warnings (by @​MahinAnowar).

8.5.19

• Fixed cleaning before for new nodes inserted to Root (by @​MahinAnowar).

8.5.18

• Restricted loading previous source maps file to the opts.from folder for security reasons (use unsafeMap: true to disable the check).

8.5.17

• Fixed Maximum call stack size exceeded error.
• Fixed Prototype hijacking for postcss.fromJSON().
• Fixed Input#origin() for unmapped end position (by @​chatman-media).

8.5.16

• Fixed Input#origin() position (by @​mizdra).
• Fixed raws after rehydrating a JSON AST (by @​sarathfrancis90).
• Fixed putting parent-less node in nodes of new node (by @​MahinAnowar).
• Fixed computing offset in positionBy() (by @​greymoth-jp).
• Fixed rangeBy() on index: 0 (by @​sarathfrancis90).

Changelog

Sourced from postcss's changelog.

8.5.23

• Do not load source map without opts.from for security reasons.

8.5.22

• Fixed custom property losing semicolon before a comment (by @​sarathfrancis90).

8.5.21

• Fixed childless at-rule losing semicolon before comment (by @​sarathfrancis90).
• Fixed docs (by @​isker).

8.5.20

• Fixed missing space if AtRule#params is set after (by @​sarathfrancis90).
• Fixed mixing AST error on warnings (by @​MahinAnowar).

8.5.19

• Fixed cleaning before for new nodes inserted to Root (by @​MahinAnowar).

8.5.18

• Restricted loading previous source maps file to the opts.from folder for security reasons (use unsafeMap: true to disable the check).

8.5.17

• Fixed Maximum call stack size exceeded error.
• Fixed Prototype hijacking for postcss.fromJSON().
• Fixed Input#origin() for unmapped end position (by @​chatman-media).

8.5.16

• Fixed Input#origin() position (by @​mizdra).
• Fixed raws after rehydrating a JSON AST (by @​sarathfrancis90).
• Fixed putting parent-less node in nodes of new node (by @​MahinAnowar).
• Fixed computing offset in positionBy() (by @​greymoth-jp).
• Fixed rangeBy() on index: 0 (by @​sarathfrancis90).

Commits

• eb9e1fe Release 8.5.23 version
• 9d19c78 Update dependencies
• 7beca13 Does no load source map file without opts.from
• decea51 Typo
• c18e30d Update EM banner
• 98a39ad Update EM banner
• a3e48c4 Release 8.5.22 version
• f49d691 Fix custom property losing its semicolon before a comment (#2117)
• 28e0daf Release 8.5.21 version
• 3d2b4e4 Update dependencies
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for postcss since your current version.

[greptile-apps]

Greptile Summary

This PR raises the backoffice application's PostCSS dependency floor and refreshes its pnpm resolution.

• Changes postcss from ^8.5.10 to ^8.5.23.
• Resolves the dependency to PostCSS 8.5.26 in the committed lockfile.

Confidence Score: 5/5

The PR appears safe to merge with no blocking failure identified.

No blocking failure remains; the previously reported lockfile-scope concern is still present but does not establish a concrete build or runtime defect.

Important Files Changed

Filename	Overview
apps/backoffice-app/package.json	Raises the PostCSS development-dependency range to ^8.5.23, consistent with the repository's existing caret-range convention.
pnpm-lock.yaml	Resolves PostCSS to 8.5.26 and updates the resulting workspace dependency graph.

_{Reviews (4): Last reviewed commit: "chore(deps-dev): bump postcss from 8.5.1..." | Re-trigger Greptile}

[greptile-apps]

Unrelated workspace lockfile churn

This focused PostCSS update also changes Jest peer variants, Node types, and transitive Babel, Browserslist, js-yaml, and ws releases across unrelated workspaces. Frozen CI and Docker installs consume the entire regenerated graph, unnecessarily broadening the regression and verification surface.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!