-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update postcss to the latest version 🚀 #6
base: master
Are you sure you want to change the base?
Conversation
Version 7.0.1 just got published.Update to this version instead 🚀 Release Notes7.0.1
|
Version 7.0.2 just got published.Update to this version instead 🚀 Release Notes7.0.2
|
Update to this version instead 🚀 Release Notes for 7.0.3
|
Update to this version instead 🚀 Release Notes for 7.0.4
|
Update to this version instead 🚀 Release Notes for 7.0.5
|
Update to this version instead 🚀 Release Notes for 7.0.6
|
Update to this version instead 🚀 Release Notes for 7.0.7
|
Update to this version instead 🚀 Release Notes for 7.0.8
|
Update to this version instead 🚀 Release Notes for 7.0.9
|
|
Update to this version instead 🚀 Release Notes for 7.0.11
|
Update to this version instead 🚀 Release Notes for 7.0.12
|
Update to this version instead 🚀 Release Notes for 7.0.13
|
|
|
|
|
|
|
|
|
|
|
|
|
🚨 Reminder! Less than one month left to migrate your repositories over to Snyk before Greenkeeper says goodbye on June 3rd! 💜 🚚💨 💚 Find out how to migrate to Snyk at greenkeeper.io
|
🚨 Reminder! Less than one month left to migrate your repositories over to Snyk before Greenkeeper says goodbye on June 3rd! 💜 🚚💨 💚 Find out how to migrate to Snyk at greenkeeper.io
|
🚨 Reminder! Less than one month left to migrate your repositories over to Snyk before Greenkeeper says goodbye on June 3rd! 💜 🚚💨 💚 Find out how to migrate to Snyk at greenkeeper.io
|
Version 7.0.0 of postcss was just published.
The version 7.0.0 is not covered by your current version range.
If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of postcss.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Release Notes
7.0 “President Amy”PostCSS 7.0 dropped Node.js 4 support and bring a few small features.
Breaking Changes
We removed Node.js 4 and Node.js 9 support since it doesn’t have security updates anymore.
We removed IE and “dead” browsers (without security updates) from Babel’s Browserslist:
New Features
@nikhilgaba added cute thing for plugin developers. If error was happened in
Container#walk()
circle, PostCSS will show in stack trace CSS node, which cause this error:@igorkamyshev added
finally
method toLazyResult
to make it compatible with latest Promise API.Other Changes
FAQ and help
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper bot 🌴