1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
|
# Changelog
# 6.7.0
Add configuration for which database name is to be used for database migrations [lewhit](https://github.com/lewhit)
Add tests for Rails 6.1 [lewhit](https://github.com/lewhit)
Migrations files should end only in .rb [kroehre](https://github.com/kroehre)
## 6.6.1
configs_for deprecation notice [borama](https://github.com/borama)
## 6.6.0
Allow data dump connection to be configured [lewhit](https://github.com/lewhit)
## 6.4.0
Add primary key to data_migrations table [aandis](https://github.com/aandis)
## 6.3.0
Add `abort_if_pending_migrations` rake tasks [tomgia](https://github.com/tomgia)
## 6.2.0
Add `rake data:schema:load` [timkrins](https://github.com/timkrins)
## 6.1.0
Fixing `rake db:schema:load:with_data` for Rails 6
Note:
Rails 5.0 is no longer maintained. The gem will still work but it is not being
actively tested.
## 6.0.5
Fixing `needs_migration?` method for Rails 5.2 and up [EnomaDebby](https://github.com/EnomaDebby)
## 6.0.4.beta
Fix rolling back schema migrations failing for Rails 5.2 and above
## 6.0.3.beta
Compatiblity with Rails 6 RC2 [y-yagi](https://github.com/y-yagi)
## 6.0.1.beta
Fix migrations being generated in wrong folder
## 6.0.0
Support for Rails 6
No longer supporting Rails 4.2
## 5.3.3
Ruby 2.2 and 2.3 are no longer actively validated with tests since they are both EOL
## 5.3.2
Fix capistrano migration tasks to only skip migrations if there are no changes in the db/data and db/migrate folders
## 5.3.1
Change database task to use data_migrations_path_configuration
## 5.3.0
Add support to configure data migration path
## 5.1.0
Fixes to `db:schema:load:with_data` + `db:structure:load:with_data` definition, thanks to [craineum](https://github.com/craineum)
## 5.0.0
Remove support for legacy migrations (from v2).
**IMPORTANT**: If you used this gem from before version 2, make sure to run migration script
```
DataMigrate::LegacyMigrator.new.migrate
```
**Failure to do so may cause re-running old migrations**
## 4.0.0
Support for Rails 5.2
Deprecated support for Rails 4.1
Internal changes to make data-migrate behavior more similar to Rails migrations
## 3.5.0
Deprecated support for rails 4.0
Improvements to timestamped migrations, thanks to [Pierre-Michard](https://github.com/Pierre-Michard)
## 3.4.0
`rake data:migrate:status` to return result in chronological order
## 3.3.1
Regression fix, thanks to [subakva](https://github.com/subakva)
## 3.3.0
The concept of schema:dump to data migrations, thanks to
[tobyndockerill](https://github.com/tobyndockerill)
## 3.2.1
data_migrate table into rails schema dump, thanks to
[jturkel](https://github.com/jturkel)
## 3.2.0
- Add support for Rails 5.1
- No longer testing EOL rubies
## 3.1.0
Rails 5.0 support thanks to
[jturkel](https://github.com/jturkel) and [abreckner](https://github.com/abreckner)
## 3.0.1
([gacha](https://github.com/gacha)) Capistrano fixes
## 3.0.0
`--skip-schema-migration` removed deprecated. This gem will no longer generate schema
migrations. It still supports running schema/data migrations with one command.
## 2.2.0
([bilby91](https://github.com/bilby91)) Capistrano support
## 2.1.0
User `Rails.application.config.paths["db/migrate"]` instead of hard coded
path to db migrations
|
