build(build): upgrade toolchain to go 1.25.7

[gzliudan]

Proposed changes

upgrade toolchain to go 1.25.7

Types of changes

What types of changes does your code introduce to XDC network?
Put an ✅ in the boxes that apply

• build: Changes that affect the build system or external dependencies
• ci: Changes to CI configuration files and scripts
• chore: Changes that don't change source code or tests
• docs: Documentation only changes
• feat: A new feature
• fix: A bug fix
• perf: A code change that improves performance
• refactor: A code change that neither fixes a bug nor adds a feature
• revert: Revert something
• style: Changes that do not affect the meaning of the code
• test: Adding missing tests or correcting existing tests

Impacted Components

Which parts of the codebase does this PR touch?
Put an ✅ in the boxes that apply

• Consensus
• Account
• Network
• Geth
• Smart Contract
• External components
• Not sure (Please specify below)

Checklist

Put an ✅ in the boxes once you have confirmed below actions (or provide reasons on not doing so) that

• This PR has sufficient test coverage (unit/integration test) OR I have provided reason in the PR description for not having test coverage
• Tested on a private network from the genesis block and monitored the chain operating correctly for multiple epochs.
• Provide an end-to-end test plan in the PR description on how to manually test it on the devnet/testnet.
• Tested the backwards compatibility.
• Tested with XDC nodes running this version co-exist with those running the previous version.
• Relevant documentation has been updated as part of this PR
• N/A

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[Copilot]

Pull request overview

This PR upgrades the Go toolchain from version 1.25.5 to 1.25.7. The change affects the build system configuration, updating the toolchain directive in go.mod and modifying the GO version variable in the Makefile.

Changes:

• Updated toolchain directive in go.mod from go1.25.5 to go1.25.7
• Changed GO variable in Makefile from version 1.25.1 to "latest"

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
go.mod	Updated toolchain directive to go1.25.7 to specify the required Go toolchain version
Makefile	Changed GO variable from specific version 1.25.1 to "latest"

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The GO variable is being changed from a specific version to "latest", but this variable doesn't appear to be used anywhere in the Makefile. If this variable is intended for future use or external consumption, consider whether "latest" is appropriate, as it introduces unpredictability. If the variable is unused, consider removing it entirely to reduce confusion.

Suggested change

GO ?= latest

[Copilot]

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Changing the GO variable from a specific version (1.25.1) to "latest" creates version inconsistency with the toolchain specification in go.mod (go1.25.7). This can lead to different build environments using different Go versions. Consider either:

1. Setting this to match the toolchain version (e.g., GO ?= 1.25.7), or
2. Removing this variable if the toolchain directive in go.mod is sufficient for version control.

Additionally, note that the toolchain version go1.25.7 specified in go.mod does not exist yet.

Suggested change

GO ?= latest