Upgrade pngcrush to version 2.0.0 #51
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![depfu[bot]](https://avatars.githubusercontent.com/in/715?s=60&v=4){kind=small}
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 upgraded a dependency and all tests pass. \o/
You should probably take a good look at this before merging this pull request, of course.
What changed?
✳️ pngcrush ( → 2.0.0) · Repo
Commits
See the full diff on Github. The new version differs by 9 commits:
2.0.0Travis: Ditch old before_install, only run on node 4, 6, 8, and 9Update author's emailUpdate gettemporaryfilepath, memoizeasync, pngcrush-bin, and which.Use ^ version ranges for dev deps.Travis: Build with node.js 4, 6, and 7.update dev deps.1.1.1Stand at pngcrush-png 3.0.0 as 3.1.0 seems to be causing problems with optipng: https://travis-ci.org/assetgraph/assetgraph-builder/jobs/174813961#L1769-L1772Depfu 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.