Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: golang 1.24 #5053

Draft
wants to merge 3 commits into
base: master
Choose a base branch
from
Draft

chore: golang 1.24 #5053

wants to merge 3 commits into from

Conversation

gacevicljubisa
Copy link
Contributor

Checklist

  • I have read the coding guide.
  • My change requires a documentation update, and I have done it.
  • I have added tests to cover my changes.
  • I have filled out the description and linked the related issues.

Description

Open API Spec Version Changes (if applicable)

Motivation and Context (Optional)

Related Issue (Optional)

Screenshots (if appropriate):

github.com/libp2p/go-libp2p v0.33.2
github.com/multiformats/go-multiaddr v0.12.3
github.com/multiformats/go-multiaddr-dns v0.3.1
github.com/libp2p/go-libp2p v0.41.0
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updating the libp2p library could be quite sensitive, I would suggest to do the update in a separate PR and test that all things work well.

@martinconic
Copy link
Contributor

My recommendation would be that we should update most of the libraries separate one from each other and separate from upgrading to the new Go version. Doing this we can avoid struggling to find possible issues/incompatibilities that might come with the new updates. the libp2p library should be in this category and any update could be sensitive and testes well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants