feat: update dependencies due to vulnerabilities #9
Conversation
This file contains hidden or 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
1 participant
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.
Hey man,
Awesome tool. Tried it out locally and noticed some vulnerabilities and unpinned libraries. For security purposes, I pinned some of them and updated the docker image.
If you plan to keep that thing up to date (which would be awesome) I would recommend to add dependabot or something like it.
There are a f**** ton of lines updated due to
cargo fmt. The main changes are the Cargo.toml files, the Dockerfile and the two imports ofimage::FileTypemoved toimage::imageops::FileTypeandimage::ConvertBuffermoved toimage::buffer::ConvertBufferDo you plan to publish the docker image yourself?