Update font-awesome-sass: 4.7.0 → 5.4.1 (major) #136
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We've updated a dependency and here is what you need to know:
Additionally, the update changed a few other dependencies as well:
You should probably take a good look at the info here and the test results before merging this pull request, of course.
What changed?
✳️ font-awesome-sass (4.7.0 → 5.4.1) · Repo
Commits
See the full diff on Github. The new version differs by 18 commits:
Merge pull request #165 from FortAwesome/5.4.1-wip
Release 5.4.1
Merge pull request #162 from FortAwesome/5.3.1-wip
Release 5.3.1
Merge pull request #161 from FortAwesome/5.2.0-wip
Upgrading to Font Awesome 5 Free 5.2.0
Merge pull request #156 from FortAwesome/5.0.13-wip
Updating to sassc since sass gem deprecated
Update to Font Awesome Free 5.0.13
Version 5.0.9
Merge pull request #145 from FortAwesome/5.0.6.2-wip
Proper pathing setup for SASS and loading of Solid style
Merge pull request #135 from paulmwatson/patch-1
Merge pull request #143 from FortAwesome/5.0.6.1-wip
Fixing pathing issues and Rails font loading
Merge pull request #139 from FortAwesome/5.0.6-wip
Upgrade to Font Awesome 5.x
Update README.md
Sorry, we couldn't find anything useful about this release.
Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase
.All Depfu comment commands