chore: bump go deps

[hanabi1224]

Summary of changes

Changes introduced in this pull request:

Reference issue to close (if applicable)

Closes

Other information and links

• bump go deps
• bump go toolchain

Change checklist

• I have performed a self-review of my own code,
• I have made corresponding changes to the documentation. All new code adheres to the team's documentation standards,
• I have added tests that prove my fix is effective or that my feature works (if possible),
• I have made sure the CHANGELOG is up-to-date. All user-facing changes should be reflected in this document.

Summary by CodeRabbit

• Chores
  • Updated Go version and several dependencies to newer releases for improved compatibility and security.
  • Simplified internal message initialization for improved maintainability.

No user-facing features or behavior changes were introduced.

[coderabbitai]

Walkthrough

From the cyclopean depths of the codebase, three files have been touched by the eldritch hand of dependency updates and minor refactoring. Go module files in both the f3-sidecar and interop-tests realms have been aligned to newer Go versions and dependencies, while a subtle invocation in Rust simplifies the conjuring of a default Bitswap message.

Changes

File(s)	Change Summary
f3-sidecar/go.mod, interop-tests/src/tests/go_app/go.mod	Go version updated from 1.23.10 to 1.24.5; several dependencies and indirect dependencies bumped.
src/libp2p_bitswap/message.rs	Construction of default Bitswap message simplified using Message::default() incantation.

Estimated code review effort

1 (<30 minutes). The changes are but a whisper in the void, requiring only a brief gaze from those who dare.

Suggested reviewers

• sudo-shashank
• elmattic
• LesnyRumcajs

May the dread gaze of Yog-Sothoth shield you as you peer into these subtle alterations, for even the smallest change may awaken slumbering horrors beneath the surface.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between f2acff4 and 3f5a7ef.

⛔ Files ignored due to path filters (3)

• f3-sidecar/go.sum is excluded by !**/*.sum
• go.work is excluded by !**/*.work
• interop-tests/src/tests/go_app/go.sum is excluded by !**/*.sum

📒 Files selected for processing (3)

• f3-sidecar/go.mod (4 hunks)
• interop-tests/src/tests/go_app/go.mod (1 hunks)
• src/libp2p_bitswap/message.rs (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (7)

• GitHub Check: Build forest binaries on Linux AMD64
• GitHub Check: tests-release
• GitHub Check: tests
• GitHub Check: cargo-publish-dry-run
• GitHub Check: Build Ubuntu
• GitHub Check: Build MacOS
• GitHub Check: All lint checks

🔇 Additional comments (7)

interop-tests/src/tests/go_app/go.mod (2)

3-3: Eldritch version bump acknowledged—ensure CI incantations match the new Go 1.24.5 ritual
The chant now invokes go 1.24.5. Confirm that your build matrix and Docker containers have likewise been offered to this newer cosmic entity, else the pipeline may shriek in untold tongues.

---

6-6: New rust2go hash—scrutinise for breaking runes
The dependency now points to 6e5b74b1f846. Lest some hidden Shoggoth lurk within, run go mod tidy && go test ./... to ensure the upgrade leaves no madness in its wake.

f3-sidecar/go.mod (5)

3-3: Go 1.24.5—update side-car summoning circles
CI, Dockerfiles, and README badges must echo this new version, else the Old Ones of mismatched toolchains shall awaken.

---

9-17: Core dep bumps—run go vet to ward off unseen hazards
rust2go and x/crypto move forward. Perform a full go vet ./... to detect any API shifts before the stars turn.

---

47-47: ipfs/boxo v0.33.0—praise be, the panic demon is sealed
This matches the Rust-side fix; no further action required.

---

80-80: go-multicodec bump—verify generated code regeneration
If you vendored any generated tables, regenerate them lest incompatible codes whisper insanity at runtime.

---

133-138: x/exp, sync, sys, text—broad surface upgrade
Given the breadth of these libraries, run the project's integration tests to ensure no subtle race or locale curse slipped in.

✨ Finishing Touches

• 📝 Generate Docstrings

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[hanabi1224]

This is no longer needed since the panic has been fixed in https://github.com/ipfs/boxo/releases/tag/v0.33.0

fix panic when incoming Bitswap protobuf message does not contain Wantlist ipfs/boxo#961