Autoprefixer, a widely used PostCSS plugin for automatically adding vendor prefixes to CSS rules, saw a minor version bump from 9.3.0 to 9.3.1 in October 2018. Both versions share the same core functionality: parsing CSS and applying vendor prefixes based on data from the "Can I Use" website, ensuring cross-browser compatibility. They also depend on the same core packages such as postcss, caniuse-lite, num2fraction, normalize-range, and postcss-value-parser, guaranteeing no fundamental changes to how Autoprefixer handles CSS parsing or value manipulation.
The key difference lies within the browserslist dependency, which updates from version 4.3.2 in 9.3.0 to 4.3.3 in 9.3.1. browserslist dictates the target browsers for vendor prefixing. While seemingly small, this update likely incorporates the latest browser usage data and potentially includes fixes or improvements in browser selection logic. For developers, this means a slightly more accurate and up-to-date vendor prefixing strategy in version 9.3.1, potentially reducing unnecessary prefixes and optimizing CSS output. Additionally, the unpackedSize has gone from 303718 to 304142, so maybe some new additional functionality has been added. Finally, the newer releases was published one day after the older release so this is probably a patch. Although the changes are minimal, upgrading from 9.3.0 to 9.3.1 is advisable for developers who want to ensure their CSS is optimized for the most current browser landscape, resulting in better performance and compatibility.
All the vulnerabilities related to the version 9.3.1 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.
