Autoprefixer version 9.6.0 introduces several updates compared to its predecessor, 9.5.1, offering developers enhanced functionality for automatically adding vendor prefixes to CSS rules. While both versions share the core purpose of leveraging Can I Use data to ensure cross-browser compatibility, version 9.6.0 includes updated dependencies that translate into improved browser support and bug fixes.
A notable difference lies in the dependencies section. Version 9.6.0 upgrades to browserslist version 4.6.1, from 4.5.4 in the previous version which dictates target browsers. Most importantly, caniuse-lite jumps to version 1.0.30000971 from 1.0.30000957, ensuring that Autoprefixer has access to the latest browser compatibility data, enabling more accurate and comprehensive prefixing. The addition of chalk as a new dependency in version 9.6.0 suggests potential improvements in the command-line interface, possibly related to color-coded output or enhanced logging for developers.
Developers upgrading to 9.6.0 can expect more accurate vendor prefixing, reflecting the most up-to-date browser support landscape. The change to chalk does not influence the main usage of the library and it's more for developers contributing or running the package in verbose mode, while the upgrade to the Caniuse-lite data will probably change the CSS output. Other than this no code changes are expected, so no major issues should be expected from the upgrade.
All the vulnerabilities related to the version 9.6.0 of the package
PostCSS line return parsing error
An issue was discovered in PostCSS before 8.4.31. It affects linters using PostCSS to parse external Cascading Style Sheets (CSS). There may be \r discrepancies, as demonstrated by @font-face{ font:(\r/*);} in a rule.
This vulnerability affects linters using PostCSS to parse external untrusted CSS. An attacker can prepare CSS in such a way that it will contains parts parsed by PostCSS as a CSS comment. After processing by PostCSS, it will be included in the PostCSS output in CSS nodes (rules, properties) despite being originally included in a comment.
