From 0fc9f9d3e741629987afd2370069485bca640396 Mon Sep 17 00:00:00 2001 From: Jan Provaznik Date: Tue, 13 Nov 2018 08:27:31 +0100 Subject: Add version 4.2 to all existing migrations DB schema generated by a migration may look different in rails 4 and 5 (because rails 5 may use different default values). For this reason it's important to explicitly set for which rails version a migration was written for. See https://stackoverflow.com/questions/35929869/activerecordmigration-deprecation-warning-asks-for-rails-version-but-im-no/35930912#35930912 --- db/migrate/20170720111708_add_lock_version_to_ci_stages.rb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'db/migrate/20170720111708_add_lock_version_to_ci_stages.rb') diff --git a/db/migrate/20170720111708_add_lock_version_to_ci_stages.rb b/db/migrate/20170720111708_add_lock_version_to_ci_stages.rb index e1c4f033286..a5caca7e80c 100644 --- a/db/migrate/20170720111708_add_lock_version_to_ci_stages.rb +++ b/db/migrate/20170720111708_add_lock_version_to_ci_stages.rb @@ -1,4 +1,4 @@ -class AddLockVersionToCiStages < ActiveRecord::Migration +class AddLockVersionToCiStages < ActiveRecord::Migration[4.2] include Gitlab::Database::MigrationHelpers DOWNTIME = false -- cgit v1.2.1