Routine dependency updates #232
Merged
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
Dependency updates
eldang
commented
Apr 24, 2025
| ) | ||
|
|
||
| replace golang.org/x/crypto => golang.org/x/crypto v0.32.0 | ||
| replace golang.org/x/crypto => golang.org/x/crypto v0.37.0 |
Contributor
Author
There was a problem hiding this comment.
https://nvd.nist.gov/vuln/detail/CVE-2025-22869 was the immediate impetus for this, and apparently 0.35.0 is the minimum fix version for crypto, but I figured it made sense to take everything to latest unless it caused problems. I had to hold antlr back because the latest version (and I think all v1.x) doesn't have a ATNDeserializer.DeserializeFromUInt16() method, which is called in cql_parser.go and cql_lexer.go. All the updates that are in this PR pass automated tests and work well in my environment.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Another round of "I had to update dependencies to satisfy a client's security requirements, so I might as well make a PR for the base repo".