cre 2.31.0 draft

[krehermann]

Requires

Supports

[github-actions[bot]]

CORA - Pending Reviewers

Codeowners Entry	Overall	Num Files	Owners
*	⏳	13	@smartcontractkit/foundations, @smartcontractkit/core
/core/services/ocr*	⏳	1	@smartcontractkit/foundations, @smartcontractkit/core
/core/services/workflows	⏳	6	@smartcontractkit/keystone
/core/web/resolver	⏳	2	@smartcontractkit/foundations, @smartcontractkit/core
/deployment/cre	⏳	4	@smartcontractkit/keystone, @smartcontractkit/operations-platform
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[bot]]

I see you updated files related to core. Please run pnpm changeset 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[bot]]

Quality Gate passed

Issues
2 New issues
0 Fixed 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

[trunk-io[bot]]

     

Failed Test	Failure Summary	Logs
TestDeployMCMSWithTimelockV2	The test failed during the deployment process, likely due to issues with initializing or configuring the access controller or related contracts.	Logs ↗︎
TestSetConfigMCMSV2Solana	The transaction failed due to invalid account data during instruction processing.	Logs ↗︎

View Full Report ↗︎ ⋅ Docs