update cldf in chainlink/deployment

[FelixFan1992]

Requires

Supports

[github-actions]

✅ No conflicts with other open PRs targeting develop

[trunk-io]

     

Failed Test	Failure Summary	Logs
Test_CCIPTokenTransfer_Sui2EVM_BurnMintTokenPool_WithAllowlist	The test failed due to an unspecified error during execution, with no clear indication of the specific cause in the logs.	Logs ↗︎
Test_CCIPTokenTransfer_Sui2EVM_BurnMintTokenPool_WithAllowlist/Sender_not_in_allowlist_-_should_fail	The test failed because a transaction was rejected by validators due to an invalid state, not because of a MoveAbort error.	Logs ↗︎
Test_CCIPMessaging_TON2EVM	The test failed due to an error or issue that caused it to not complete successfully.	Logs ↗︎
Test_CCIP_EVM2Sui_ZeroReceiver/Message_to_Sui_with_zero_receiver		Logs ↗︎

... and 11 more

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