TXMv2 broadcast transactions

[eduard-cl]

No description provided.

[github-actions]

AER Report: CI Core

aer_workflow , commit , Clean Go Tidy & Generate , Detect Changes , Scheduled Run Frequency , Core Tests (go_core_tests) , Core Tests (go_core_tests_integration) , Core Tests (go_core_ccip_deployment_tests) , GolangCI Lint (.) , Core Tests (go_core_fuzz) , Core Tests (go_core_race_tests) , test-scripts , lint , SonarQube Scan

1. Test failure in core/capabilities/remote/executable:

[Run tests] [2025-01-20T13:19:04.2611937Z] FAIL

Source of Error:

Run tests	2025-01-20T13:19:04.2611937Z FAIL
Run tests	2025-01-20T13:19:04.2612463Z FAIL	github.com/smartcontractkit/chainlink/v2/core/capabilities/remote/executable	633.154s

Why: The test suite for core/capabilities/remote/executable failed. The logs do not provide specific details about the failure, but the test did not pass within the allotted time, indicating a potential timeout or unhandled exception.

Suggested fix: Investigate the specific test cases within core/capabilities/remote/executable to identify the root cause. Look for potential infinite loops, unhandled exceptions, or resource constraints that could lead to a timeout. Add more detailed logging to capture the exact point of failure.

AER Report: Operator UI CI

aer_workflow , commit , Breaking Changes GQL Check

1. Workflow triggered but failed to complete successfully: breaking-changes-gql-check

Source of Error:

Run convictional/trigger-workflow-and-wait@f69fa9eedd3c62a599220f4d5745230e237904be	2025-01-20T13:06:31.9935013Z Checking conclusion [failure]
Run convictional/trigger-workflow-and-wait@f69fa9eedd3c62a599220f4d5745230e237904be	2025-01-20T13:06:31.9935538Z Checking status [completed]
Run convictional/trigger-workflow-and-wait@f69fa9eedd3c62a599220f4d5745230e237904be	2025-01-20T13:06:31.9935994Z Conclusion is not success, it's [failure].
Run convictional/trigger-workflow-and-wait@f69fa9eedd3c62a599220f4d5745230e237904be	2025-01-20T13:06:31.9936715Z Propagating failure to upstream job

Why: The triggered workflow did not complete successfully. The status check returned a conclusion of "failure," indicating that the downstream job encountered an issue.

Suggested fix: Investigate the logs of the downstream job at https://github.com/smartcontractkit/operator-ui/actions/runs/12868676511 to identify the specific cause of the failure and address it accordingly.

[github-actions]

I see you added a changeset file but it does not contain a tag. Please edit 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.

🎖️ No JIRA issue number found in: PR title, commit message, or branch name. Please include the issue ID in one of these.

[cl-sonarqube-production]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube