Update dependencies #265
Closed
Update dependencies #265
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
|
Hi @joohoi, is the project still maintained? Thanks :) |
|
Hi, It is. I have just been really busy lately! Thanks for the PR, I'll look into it within a few days. |
|
Hi, @joohoi do you have any update for me? 😀 |
|
Hello? :) |
|
Hi @joohoi could you please check the PR? I think it makes sense to update the Golang version (if possible). @fritterhoff I think in the meantime, it could make sense to update to version 1.17 directly, what do you think? |
|
Sure - it makes more sense to use an up-to-date version, but without any feedback/reaction it is a pity to waste any time 😞 |
|
@ZPascal I've updated the dependencies and the base image to 1.17 a few days ago. |
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.
Hi,
several dependencies are a bit outdated so I've updated them (including the changes for #220 ). According to my tests nothing should be broken afterwards 😉