horizon: update go dependencies #5084
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
tsachiherman
force-pushed
the
tsachi/update_go_dependencies
branch
from
0419b5c
to
09881b3
Compare
tamirms
approved these changes
Oct 18, 2023
2opremio
added a commit
to 2opremio/go-2
that referenced
this pull request
Oct 23, 2023
stellar#5084 broke go.mod becaue: 1. go mod tidy wasn't invoked before merging (we should probably enforce this is CI and make sure there are no diffs) 2. It ugraded github.com/creachadair/jrpc2 to 1.1.1 which requires Go 1.21 (breaking the two-Go-release compatibility guarantee we make)
Merged
2opremio
added a commit
that referenced
this pull request
Oct 23, 2023
#5084 broke go.mod becaue: 1. go mod tidy wasn't invoked before merging (we should probably enforce this is CI and make sure there are no diffs) 2. It ugraded github.com/creachadair/jrpc2 to 1.1.1 which requires Go 1.21 (breaking the two-Go-release compatibility guarantee we make)
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.
PR Checklist
PR Structure
otherwise).
services/friendbot, orallordocif the changes are broad or impact manypackages.
Thoroughness
.mdfiles, etc... affected by this change). Take a look in the
docsfolder for a given service,like this one.
Release planning
needed with deprecations, added features, breaking changes, and DB schema changes.
semver, or if it's mainly a patch change. The PR is targeted at the next
release branch if it's not a patch change.
What
This PR updates the dependencies of the go monorepo, updating some of the packages that are known to have vulnerabilities.
Why
Use latest packages to avoid known vulnerabilities, and in particular
Known limitations
n/a