Using numeric(20,0) for chain_selector and blocks in ccv_chain_statuses

[mateusz-sekara]

Context smartcontractkit/chainlink-ccv#783

[github-actions]

👋 mateusz-sekara, 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!

[github-actions]

✅ No conflicts with other open PRs targeting develop

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

[Copilot]

Pull request overview

This PR updates the database schema for the ccv_chain_statuses table to use NUMERIC(20,0) instead of TEXT for the chain_selector and finalized_block_height columns. This change aligns with the pattern established in other tables throughout the codebase where uint64 values (like chain selectors) are stored using NUMERIC(20,0).

Changes:

• Converts chain_selector column from TEXT to NUMERIC(20,0) in ccv_chain_statuses table
• Converts finalized_block_height column from TEXT to NUMERIC(20,0) in ccv_chain_statuses table
• Provides proper up and down migration paths with primary key handling

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[cl-sonarqube-production]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarQube

[trunk-io]

     

View Full Report ↗︎ ⋅ Docs