Repository navigation
[chore] Use registry.CapabilitiesRegistry instead of deprecated core alias - #596
Conversation
core.CapabilitiesRegistry is a deprecated alias that is being removed from chainlink-common. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
👋 cedric-cordenier, thanks for creating this pull request! To help reviewers, please consider creating future PRs as drafts first. This allows you to self-review and make any final changes before notifying the team. Once you're ready, you can mark it as "Ready for review" to request feedback. Thanks! |
There was a problem hiding this comment.
🟡 Changes recommended
Three production declarations still reference the upstream CapabilitiesRegistry alias and will fail to compile when it is removed.
1 open issue
What changed in this PR
Updates two uses of the deprecated core.CapabilitiesRegistry alias to the canonical registry type, preparing for its removal in smartcontractkit/chainlink-common#2545. These substitutions preserve type identity and runtime behavior.
Changes:
- Uses
registry.CapabilitiesRegistryin the plugin’sNewRelayersignature. - Uses the same type in the relayer options validation test.
| File | Description |
|---|---|
pkg/relay/evm_test.go |
Migrates the test field to the canonical registry type. |
pkg/cmd/chainlink-evm/main.go |
Migrates the plugin’s registry parameter to the canonical type. |
Review effort: Balanced
📊 API Diff Results
|
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Switches the remaining uses of the deprecated
core.CapabilitiesRegistryalias toregistry.CapabilitiesRegistryfromchainlink-common/pkg/capabilities/registry. It's a type alias, so this is a no-op, but it unblocks removing the alias in smartcontractkit/chainlink-common#2545.🤖 Generated with Claude Code