PostCSS 8.4.29 and 8.4.28 are recent versions of a powerful tool for transforming styles with JavaScript plugins, highly valuable for developers seeking to enhance and automate their CSS workflows. Both versions share the same core dependencies: nanoid for generating unique IDs, picocolors for colorful terminal output, and source-map-js for robust source map handling, ensuring consistent performance. They are distributed under the MIT license and actively supported through funding platforms like Open Collective, Tidelift, and GitHub Sponsors.
The key difference between the two versions lies in their release date and potentially subsequent bug fixes or minor enhancements. Version 8.4.29 was released on August 29, 2023, while 8.4.28 was released on August 15, 2023. Moreover, looking at the unpacked size of both packages, 8.4.29 (196422) is a bit bigger than 8.4.28 (196218). While the file count remains the same at 55, suggesting no major structural changes, this subtle difference in size suggests minor code or asset updates.
For developers, upgrading from 8.4.28 to 8.4.29 is likely a low-risk endeavor, potentially bringing improved stability and addressing any identified issues. Always refer to the official changelog for a comprehensive list of changes, which would provide granular details about bug fixes, performance optimizations, or new features in version 8.4.29. These minor version updates are crucial for maintaining a healthy and up-to-date development environment.
All the vulnerabilities related to the version 8.4.29 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.
