Update deps for v2.4.0 release #4151
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
Lets keep these up to date before doing a new release.
Basically no code changes. Just a release tag.
Jacalz
force-pushed
the
update-deps-v2.4.0
branch
2 times, most recently
from
cfe00ab
to
d982176
Compare
|
Had to revert the change to the new fyne-io/image package. The license check is still complaining. I am honestly considering just moving gobmp into the fyne-io/image project as the upstream developer was a pain working with and had no interest in merging my PR. He commited is own solution without even trying to say what was wrong with my PR like it was some kind of issue and not a PR I had opened. |
|
Do you need to |
Nope. The vendor folder has been removed on |
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.
Description:
We have gotten a lot of PRs from Chinese security researchers trying to update packages for security issues that do not affect us and we have in general been behind on versions due to previously having Go 1.14 as minimum version. Update dependencies to be on top of it before releasing v2.4.0.
I have not updated typesetting, packages related to wasm support or urfave/cli (uses generics and Go 1.18). For the first two, there are probably I don't have enough knowledge to know if everything is ready to be updated.
Checklist:
Where applicable: