common bump

[ettec]

No description provided.

[github-actions]

👋 ettec, thanks for creating this pull request!

To help reviewers, please consider creating future PRs as drafts first. This allows you to self-review and make any final changes before notifying the team.

Once you're ready, you can mark it as "Ready for review" to request feedback. Thanks!

[github-actions]

✅ No conflicts with other open PRs targeting develop

[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.

[Copilot]

Pull request overview

Risk Rating: LOW

This PR bumps the github.com/smartcontractkit/chainlink-common dependency to a newer pseudo-version across the repo’s main module and several nested test/deployment/script modules, updating corresponding go.sum entries accordingly.

Changes:

• Update github.com/smartcontractkit/chainlink-common from v0.11.2-0.20260506120607-7f10be016c89 to v0.11.2-0.20260511105412-c0c74c7c893e in multiple go.mod files.
• Refresh related go.sum checksums to match the new chainlink-common version.
• Remove a duplicated cld-changesets v0.2.0/go.mod checksum line in a couple of go.sum files.

Scrupulous human review recommended (targeted):

• Confirm the chainlink-common commit c0c74c7c893e is the intended bump and is compatible with the consuming modules (root, deployment tooling, scripts, and test modules), since any subtle API/behavior changes could surface primarily in integration/system tests and scripts.

Reviewed changes

Copilot reviewed 7 out of 14 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
system-tests/tests/go.sum	Updates chainlink-common sums; removes a duplicated cld-changesets go.mod sum entry.
system-tests/tests/go.mod	Bumps chainlink-common requirement to the new pseudo-version.
system-tests/lib/go.sum	Updates chainlink-common sums to the new pseudo-version.
system-tests/lib/go.mod	Bumps chainlink-common requirement to the new pseudo-version.
integration-tests/load/go.sum	Updates chainlink-common sums to the new pseudo-version.
integration-tests/load/go.mod	Bumps chainlink-common requirement to the new pseudo-version.
integration-tests/go.sum	Updates chainlink-common sums to the new pseudo-version.
integration-tests/go.mod	Bumps chainlink-common requirement to the new pseudo-version.
go.sum	Updates top-level chainlink-common sums to the new pseudo-version.
go.mod	Bumps top-level chainlink-common requirement to the new pseudo-version.
deployment/go.sum	Updates chainlink-common sums to the new pseudo-version.
deployment/go.mod	Bumps chainlink-common requirement to the new pseudo-version.
core/scripts/go.sum	Updates chainlink-common sums; removes a duplicated cld-changesets go.mod sum entry.
core/scripts/go.mod	Bumps chainlink-common requirement to the new pseudo-version.

[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

[trunk-io]

     

Failed Test	Failure Summary	Logs
Test_CCIP_TokenTransfer_LnR_Aptos2EVM	The test failed because the expected condition or process did not complete successfully, likely due to a timeout or an issue with the environment s...	Logs ↗︎
Test_CCIP_TokenTransfer_BnM_EVM2Aptos	The test failed because the Aptos node API could not be accessed on port 8080, likely due to the container not exposing the required port properly.	Logs ↗︎
Test_CCIP_TokenTransfer_LnR_without_TransferRef_EVM2Aptos	The test failed because the Aptos node API was not accessible on port 8080, preventing the container from being properly tested.	Logs ↗︎

View Full Report ↗︎ ⋅ Docs