Upgrade minimagick 5 #132
Open
Upgrade minimagick 5 #132
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
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.
Using just the specs as a guide, this seems like a fairly minimal set of changes that would permit support for minimagick 5, addressing all deprecation warnings.
It also introduces distinct gemfiles for minimagick v4 and v5 which could both be run in CI. I have not yet modified the Github actions yaml to do that, but should be pretty easy to do.
A couple specs are still failing, related to the
stripcommand, but I figured it would be worth posting this to see if it seems like the right direction before spending more time on it.