PostCSS 8.5.26

PostCSS 8.5.26 landed on August 6, 2026, and let's not get carried away: this is a patch release that fixes two things. Two. No new features, no performance renaissance, no reason to rearrange your build pipeline.

What Actually Changed

• Fixed a list.split() regression — the 8.5.17 visitor rework broke splitting in some configurations; this restores correct behavior (reported and fixed by @lazerg).
• Symlink tracking in source map loading — path protection during source map resolution now follows symlinks properly (by @drengir1), which matters when your project resolves through symlinked node_modules or monorepo workspaces.

Why It Matters More Than It Looks

Two fixes in a patch release reads as boring. But the list.split() regression is exactly the kind of thing that silently breaks @value parsing, custom at-rules, or any plugin leaning on PostCSS's list utilities — you'd get weird output, not loud errors. The symlink fix matters for pnpm-style isolated installs, where source maps pointing at the wrong physical path have been a recurring annoyance.

The Caveats

If you never hit either bug, this release changes nothing for you. And note the pattern: 8.5.25 shipped just a week earlier with its own regression fix — the 8.5.17 visitor rewrite is still shaking out. If your build was fine before, there's no rush. If you're on a pnpm monorepo with source maps, this one is worth taking.

Update when your test suite gives you the green light. Not before.