support Solana v1 tx

[huangzhen1997]

Jira

[github-actions]

CORA - Pending Reviewers

Codeowners Entry	Overall	Num Files	Owners
*	⏳	1	@smartcontractkit/foundations, @smartcontractkit/core
/integration-tests/**/*ccip*	⏳	2	@smartcontractkit/ccip-offchain, @smartcontractkit/core, @smartcontractkit/ccip
/deployment/	⏳	1	@smartcontractkit/ccip-tooling, @smartcontractkit/ccip-offchain, @smartcontractkit/keystone, @smartcontractkit/operations-platform, @smartcontractkit/core
/deployment/ccip/	⏳	6	@smartcontractkit/ccip-tooling, @smartcontractkit/ccip-offchain, @smartcontractkit/operations-platform, @smartcontractkit/core
go.mod	⏳	6	@smartcontractkit/core, @smartcontractkit/foundations
go.sum	⏳	6	@smartcontractkit/core, @smartcontractkit/foundations
integration-tests/go.mod	⏳	1	@smartcontractkit/core, @smartcontractkit/devex-tooling, @smartcontractkit/foundations
integration-tests/go.sum	⏳	1	@smartcontractkit/core, @smartcontractkit/devex-tooling, @smartcontractkit/foundations

Legend: ✅ Approved | ❌ Changes Requested | 💬 Commented | 🚫 Dismissed | ⏳ Pending | ❓ Unknown

For more details, see the full review summary.

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

   

Failed Test	Failure Summary	Logs
Test_CRE_V2_ConfidentialWorkflows_Relay/Confidential_Workflows_Relay_-_mixed-env	The test failed during the setup of confidential workflows enclaves, likely due to an error or timeout in starting or responding from the enclave a...	Logs ↗︎
Test_CRE_V2_ConfidentialWorkflows_Relay/Confidential_Workflows_Relay_-_workflow-gateway-capabilities-confidential-workflows	The test failed during the setup of confidential workflows enclaves, likely due to an error or timeout in enclave initialization or communication.	Logs ↗︎
Test_CRE_V2_Suite_Bucket_C	The test named Test_CRE_V2_Suite_Bucket_C failed to run successfully.	Logs ↗︎
Test_CRE_V2_Suite_Bucket_C/Cron_Beholder_-_workflow-gateway-capabilities	The test failed because the Chip Ingress stack failed to start, preventing the creation of the stack instance.	Logs ↗︎

... and 1 more

View Full Report ↗︎ ⋅ Docs

[cl-sonarqube-production]

Quality Gate failed

Failed conditions
25.0% Duplication on New Code (required ≤ 10%)
C Maintainability Rating on New Code (required ≥ A)
16.51% Technical Debt Ratio on New Code (required ≤ 4%)

See analysis details on SonarQube

Catch issues before they fail your Quality Gate with our IDE extension SonarQube for IDE