bump ccip dep

[RensR]

No description provided.

[github-actions]

I see you updated files related to core. Please run make gocs in the root directory to add a changeset as well as in the text include at least one of the following tags:

• #added For any new functionality added.
• #breaking_change For any functionality that requires manual action for the node to boot.
• #bugfix For bug fixes.
• #changed For any change to the existing functionality.
• #db_update For any feature that introduces updates to database schema.
• #deprecation_notice For any upcoming deprecation functionality.
• #internal For changesets that need to be excluded from the final changelog.
• #nops For any feature that is NOP facing and needs to be in the official Release Notes for the release.
• #removed For any functionality/config that is removed.
• #updated For any functionality that is updated.
• #wip For any change that is not ready yet and external communication about it should be held off till it is feature complete.

[github-actions]

✅ No conflicts with other open PRs targeting develop

[trunk-io]

     

View Full Report ↗︎ ⋅ Docs

[Copilot]

Pull request overview

Risk Rating: MEDIUM

This PR bumps the pinned github.com/smartcontractkit/chainlink-ccip dependency versions across the main module and several nested test/deployment modules, updating their go.mod/go.sum files and reflecting a related dependency-graph change in go.md.

Changes:

• Update chainlink-ccip and selected chainlink-ccip/* module pseudo-versions (notably chains/evm and deployment) across multiple Go modules in this repo.
• Regenerate/update go.sum entries to match the new module versions/hashes.
• Adjust the go.md Mermaid module-dependency graph for the CCIP module relationships.

Reviewed changes

Copilot reviewed 8 out of 15 changed files in this pull request and generated 7 comments.

Show a summary per file

File	Description
go.mod	Bumps chainlink-ccip and chainlink-ccip/chains/evm versions in the main module.
go.sum	Updates checksums corresponding to the bumped CCIP modules in the main module.
go.md	Updates the documented module dependency graph edges related to CCIP.
deployment/go.mod	Bumps CCIP module versions used by the deployment module.
deployment/go.sum	Updates checksums for the deployment module after the CCIP bump.
core/scripts/go.mod	Bumps CCIP module versions used by the core/scripts module.
core/scripts/go.sum	Updates checksums for the core/scripts module after the CCIP bump.
integration-tests/go.mod	Bumps CCIP module versions used by the integration-tests module.
integration-tests/go.sum	Updates checksums for the integration-tests module after the CCIP bump.
integration-tests/load/go.mod	Bumps CCIP module versions used by the integration-tests/load module.
integration-tests/load/go.sum	Updates checksums for the integration-tests/load module after the CCIP bump.
system-tests/lib/go.mod	Bumps CCIP module versions used by the system-tests/lib module.
system-tests/lib/go.sum	Updates checksums for the system-tests/lib module after the CCIP bump.
system-tests/tests/go.mod	Bumps CCIP module versions used by the system-tests/tests module.
system-tests/tests/go.sum	Updates checksums for the system-tests/tests module after the CCIP bump.

Areas requiring scrupulous human review:

• The decision to bump only some chainlink-ccip/* submodules (evm/deployment) while leaving others (solana/gobindings) on an older commit in each affected go.mod.
• Running go test ./... (or the repo’s standard CI targets) for each affected module (./, deployment/, core/scripts/, integration-tests/, integration-tests/load/, system-tests/lib/, system-tests/tests/) to ensure the new CCIP commit doesn’t introduce integration breakages.

[cl-sonarqube-production]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarQube