mirror of
https://github.com/lipis/flag-icons.git
synced 2026-04-26 09:25:50 +03:00
[PR #366] [MERGED] Update grunt-contrib-cssmin to the latest version 🚀 #768
Labels
No labels
3rd-party
3rd-party
bug
code
documentation
enhancement
fixed-in-master
flag-request
help needed
missing-flag
missing-flag
pull-request
wrong-flag
wrong-flag
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/flag-icons#768
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/lipis/flag-icons/pull/366
Author: @greenkeeper[bot]
Created: 5/10/2017
Status: ✅ Merged
Merged: 5/13/2017
Merged by: @lipis
Base:
master← Head:greenkeeper/grunt-contrib-cssmin-2.2.0📝 Commits (1)
a6bc70cchore(package): update grunt-contrib-cssmin to version 2.2.0📊 Changes
1 file changed (+1 additions, -1 deletions)
View changed files
📝
package.json(+1 -1)📄 Description
Version 2.2.0 of grunt-contrib-cssmin just got published.
The version 2.2.0 is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of grunt-contrib-cssmin.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Commits
The new version differs by 3 commits0.
5404a77Update clean-css to v4.1.1.f3e3987Set required Node.js version to >=4 since clean-css 4.x requires that.22471feUpdate URL to clean-css repo.false
See the full diff
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.