Project

General

Profile

Refactor #18726

Test failures due to deprecation warning

Added by Sean O'Keeffe over 4 years ago. Updated about 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
DB migrations
Target version:
Difficulty:
Triaged:
Bugzilla link:
Fixed in Releases:
Found in Releases:

Description

Currently i'm getting:

`#timestamps` was called without specifying an option for `null`. In Rails 5, this behavior will change to `null: false`. You should manually specify `null: true` to prevent the behavior of your existing migrations from changing."

Associated revisions

Revision cb271bde (diff)
Added by Sean O'Keeffe over 4 years ago

Fixes #18726 - Set null to true on migrations for Rails 5

History

#1 Updated by The Foreman Bot over 4 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/foreman/pull/4348 added

#2 Updated by Sean O'Keeffe over 4 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100

#3 Updated by Dominic Cleal over 4 years ago

  • Category changed from Rails to DB migrations
  • Legacy Backlogs Release (now unused) set to 209

Also available in: Atom PDF