rm keepers v1

[RensR]

No description provided.

[github-actions]

CORA - Pending Reviewers

Codeowners Entry	Overall	Num Files	Owners
*	⏳	33	@smartcontractkit/foundations, @smartcontractkit/core
/core/services/job/	⏳	4	@smartcontractkit/foundations, @smartcontractkit/core
/core/services/pipeline/	⏳	4	@smartcontractkit/foundations, @smartcontractkit/bix-framework, @smartcontractkit/core
/core/services/keeper/	⏳	26	@smartcontractkit/dev-services
/core/web/resolver/	⏳	7	@smartcontractkit/foundations, @smartcontractkit/core
/core/web/schema/	⏳	1	@smartcontractkit/foundations, @smartcontractkit/core
/devenv/	⏳	16	@smartcontractkit/devex-tooling
/deployment/	⏳	4	@smartcontractkit/ccip-tooling, @smartcontractkit/ccip-offchain, @smartcontractkit/keystone, @smartcontractkit/operations-platform, @smartcontractkit/core
/.github/**	⏳	1	@smartcontractkit/devex-cicd, @smartcontractkit/devex-tooling, @smartcontractkit/core
/.github/CODEOWNERS	⏳	1	@smartcontractkit/core, @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
TestScripts/node/validate/disk-based-logging-disabled	The test failed without a specific error message, indicating an unspecified failure during script execution.	Logs ↗︎
TestScripts/node/validate/disk-based-logging-disabled	The test failed during validation of node disk-based logging configuration, likely due to an issue with the logging setup.	Logs ↗︎
TestScripts/node/validate/defaults-override	The test failed during validation of default configuration overrides, but the specific cause of failure is not detailed in the log.	Logs ↗︎
TestScripts/node/validate/defaults-override	The test failed during configuration validation, indicating an issue with the environment or setup that prevented successful validation.	Logs ↗︎

... and 24 more

View Full Report ↗︎ ⋅ Docs

[cl-sonarqube-production]

Quality Gate passed

Issues
6 New issues
5 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