Skip to content
CAI
Software that uses CAICheck a score

ilyakatz/data-migrate

58.4

Adequate · 6 November 2026

1k

lines of production code

Ruby

primary language

4

measurements over time

CAI band scale
CAI trend line
CAI lens gauges

What this system is

Features

Initial library structure and core module definition

The library now initializes by loading its core components, including the Rails helper, data migrator, schema migration, database tasks, and configuration modules, and exposes a root path accessor for locating the library directory.

lib · high confidence

Initial project scaffolding and configuration

The repository is initialized with the core structure for the \data\_migrate\ gem, including the MIT license, a comprehensive README detailing installation and usage, and a Changelog tracking versions from 11.3.1 back to 6.0.0. Development tooling is established via \.rubocop.yml\ (targeting Ruby 3.1), \.hound.yml\, \.overcommit.yml\, and an \Appraisals\ file that configures testing against Rails 6.1 through 8.1. The gem's supported Rails versions are explicitly documented as 6.1 through 8.0 in the README, with legacy support for Rails 6.0 via version 9.1.x.

(repo-wide) · high confidence

New data migration generator with customizable templates and paths

The library now includes a dedicated \data\_migration\ generator that creates data migration files using a configurable template and output path. Users can specify custom data migration directories via \data\_migrations\_path\ and provide their own migration templates via \data\_template\_path\. The generated data migrations use the modern \ActiveRecord::Migration\[version\]\ class structure and include a default template that raises \IrreversibleMigration\ in the \down\ method, while a separate standard migration template is also provided for schema changes.

lib/generators · high confidence

New rake tasks for combined schema and data migrations

The \tasks/databases.rake\ file introduces a suite of new Rake tasks that allow users to manage both database schema and data migrations together. Key additions include \db:migrate:with\_data\ to run schema and data migrations in sync, \db:migrate:up:with\_data\ and \db:migrate:down:with\_data\ for version-specific operations, and \db:rollback:with\_data\ for rolling back changes. It also adds \db:migrate:status:with\_data\ to view the status of both migration types, \db:abort\_if\_pending\_migrations\ to prevent deployment with pending changes, and \db:prepare:with\_data\ for initial setup. Additionally, \data:migrate\, \data:migrate:up\, \data:migrate:down\, and \data:migrate:redo\ tasks are provided for managing data migrations independently, ensuring that data schema dumps are updated appropriately after operations.

tasks · high confidence

Removals

Removed legacy Rails scaffolding and framework files

The application's default Rails scaffolding has been removed, including the core configuration files (config/application.rb, config/routes.rb, config/database.yml), the base controller and helper classes, the main layout template, and the public directory assets (error pages, JavaScript libraries like Prototype and script.aculo.us, and the welcome page). This cleanup eliminates the boilerplate code from the initial project setup.

(repo-wide) · high confidence

Behavioural changes

Capistrano deployment now supports conditional data migrations

The deployment process now includes a new Capistrano task that runs \rake db:migrate:with\_data\ instead of the standard migration task. This new behavior is conditional: if the \conditionally\_migrate\ configuration option is enabled, the system checks for changes in both \db/migrate\ and \db/data\ directories and skips the migration step if neither has changed. The task defaults to running on the primary database server and can be configured via \migration\_role\.

lib/capistrano · high confidence

Consolidate data migration tasks into a dedicated module

The rake tasks for data migrations (migrate, status, status\_with\_schema, dump, and abort\_if\_pending\_migrations) are now implemented within the new DataMigrate::Tasks::DataMigrateTasks module. This change centralizes the task logic, ensuring that the status command correctly scans subdirectories for migration files and that the database name resolution adapts to the specific Railties version (Rails 6.1 vs 7.0+).

_lib/data\migrate/tasks · high confidence

DataMigrate v11.3.1: Rails 7.2 compatibility and configuration overhaul

This release updates the gem to version 11.3.1 and introduces significant architectural changes to support Rails 7.2. The library now uses a centralized \DataMigrate.config\ object for settings (such as \data\_migrations\_path\ and \db\_configuration\) instead of global constants, and introduces a \data\_template\_path\ configuration option that validates the existence of custom migration templates. To ensure compatibility with Rails 7.1 and 7.2 internals, the codebase now delegates schema migration access to \ActiveRecord::Base.connection\_pool\ and \connection\ methods, and resets the Active Record model schema cache before running data migrations to prevent stale state issues.

_lib/data\migrate · high confidence

Test coverage

Added comprehensive test suite for data migration configuration and execution; Added test fixtures for data and schema migrations; Added tests for data migration rake tasks; Added tests for the data migration generator; Initial RSpec test suite for data migration paths; Removed obsolete Rails performance and test helper files.

Dependencies

Expanded Rails version support via Appraisal gemfiles

The gemfiles directory now includes Appraisal configurations for Rails 6.1, 7.0, 7.1, 7.2, 8.0, and 8.1, enabling the library to be tested and used across these specific framework versions.

gemfiles · high confidence

Update gem dependencies and simplify Gemfile

The data\_migrate gem now requires Rails 6.1 or higher (activerecord and railties), dropping support for older versions. The Gemfile has been simplified to use the gemspec, removing explicit version constraints for Rails and SQLite3 that were previously defined there.

(dependencies) · high confidence

Written by cca.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.

How this codebase got here

Score

  • CAI 58 → 58 (+0.5)
  • Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.

Lenses

  • Code Health 63 → 63 (+0.0)
  • Architecture 69 → 69 (+0.0)
  • Maturity 49 → 51 (+1.8)
  • Readiness 66 → 66 (+0.0)
  • Security 83 → 75 (-8.3)

Resolved (6)

  • Duplication of intent between DatabaseTasks and SchemaMigration. SchemaMigration has a method 'pending_schema_migrations()' which duplicates the functionality of DatabaseTasks.pending_schema_migrations(). Similarly, DatabaseTasks has 'pending_data_migrations()' which likely duplicates logic that could be centralized. Having two entry points for the same query creates maintenance overhead and potential for divergence.
  • Inconsistent 'run' operation signatures across different context types. DataMigrator and SchemaMigration accept (direction, paths, version), while MigrationContext accepts (direction, target_version) and DatabaseTasks accepts (migration, direction). This forces consumers to memorize different argument orders and sets of parameters depending on which class they are using, despite the core intent (executing migrations) being identical.
  • Inconsistent method signatures for dump operations. Both SchemaDumper and StatusService have two 'dump' methods: one taking (connection, stream) and one taking just (stream). This suggests an overloaded method pattern that is inconsistently applied or documented. It is unclear if the single-argument version infers the connection or if it's a legacy signature.
  • Off-boarding risk: anonymized user #1
  • Orphaned file (lib/data_migrate/data_migrator.rb)
  • Redundant and inconsistent status reporting methods. Both DataMigrator and MigrationContext expose 'migrations_status()', while the Tasks layer exposes 'status()' and 'status_with_schema()'. It is unclear if these return the same data structure or if 'status_with_schema' is a distinct operation. The naming convention shifts between 'migrations_status' and 'status' without clear domain separation.

New (1)

  • Off-boarding risk: anonymized user #1

Changes since last survey

  • 2 commits — 2 feature/other, 0 fixes

By area

  • (root) — 1 commit
  • lib/data_migrate — 1 commit

Notable commits

  • change: Feature: Check for pending data migrations on page load (#374)
  • change: Release version 11.4.0

Written by cca.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.

Survey your own repository

ilyakatz/data-migrate was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point a surveyor at a repository you know and see whether you agree with it.

About this page

  • The score is its most recent published measurement, taken on 6 November 2026 at a pinned commit. It is not a live figure and does not change until the project is measured again.
  • Measured at commit c66da4f4780d5a0df516949bc9f303bf506ee432 — the exact code this score is about.
  • Scored under rubric-2026.11.2 — the same rubric and the same method as every other entry in this index.
  • Measured by Canine Code Analyzer (cca.canine.dev) using cca measure-2026.11.2+preprod-5c4e66d9318b.