Bump chainlink-ton

[krebernisak]

This PR bumps https://github.com/smartcontractkit/chainlink-ton to latest which brings:

• ExtraData codec fixes when connecting to Solana via LOOP
• Devenv support (Solana <> TON enabled)

Requires

smartcontractkit/chainlink-ccip#1756

Supports

smartcontractkit/chainlink-ton#633

[github-actions]

✅ No conflicts with other open PRs targeting develop

[Copilot]

Pull request overview

Risk Rating: MEDIUM (dependency bumps that can affect runtime relayer/plugin behavior)

This PR bumps github.com/smartcontractkit/chainlink-ton (and the related chainlink-ccip version) to newer pseudo-versions to pick up TON/Solana LOOP codec fixes and enable Solana↔TON devenv support.

Changes:

• Updated the TON LOOP plugin gitRef in the public plugin manifest.
• Bumped chainlink-ton and chainlink-ccip versions in the root Go module (go.mod / go.sum).
• Bumped the same dependencies in the deployment/ Go module (deployment/go.mod / deployment/go.sum), including chainlink-ton/deployment and chainlink-ccip/deployment.

Reviewed changes

Copilot reviewed 3 out of 5 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
plugins/plugins.public.yaml	Updates the TON plugin gitRef used by loopinstall.
go.mod	Bumps chainlink-ton and chainlink-ccip requirements in the root module.
go.sum	Updates checksums corresponding to the bumped module versions.
deployment/go.mod	Bumps chainlink-ton/chainlink-ton/deployment and chainlink-ccip/chainlink-ccip/deployment in the deployment module.
deployment/go.sum	Updates checksums corresponding to the bumped deployment-module versions.

Requires scrupulous human review (behavioral validation):

• Validate TON↔Solana LOOP connectivity paths impacted by the ExtraData codec changes (end-to-end / integration), since this PR is primarily a dependency bump with runtime implications.

[trunk-io]

     

View Full Report ↗︎ ⋅ Docs

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

[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