Releases: jasonfb/nonschema_migrations
Rail 7.1 support
v6.5.1
Unbound Dependency on Rails Upper Level Version (Rails 7 now supported)
Now ready for Rails 7.
Welcome to Nonschema Migrations.
1. run set up data migrations start with
rails generate data_migrations:install
2. to create a data migration use
rails generate data_migration SetupExampleData
You can think of data migrations like seed data for production, staging, and dev environments.
For support please see https://heliosdev.shop/
For Rails 7.0.0.alpha2 special release Latest
This version (6.0.alpha2) includes this contribution from @badlamer fixing the ability to run the migrations down (personally I don't run my migrations down but I appreciate that @badlamer does) . Thank you @badlamer !
Because of the funky way that bundler gem dependency specification does not allow me to specify that it's OK to allow the prerelease version of Rails, I am just releasing this as nonschema_migations gem version 6.0.alpha2 (for use with Rails 7.0.0.alpha2-- note it is locked specifically in the gem dependency).
Once Rails 7 is no longer prerelease I will re-release fixing the gemspec file.
• Rails 7 doesn't like having data_migrations have an id column; if you are upgrading, you might want to drop the ID column from the data_migrations table
• Otherwise, new projects on Rails 7.0.0.alpha2 should be OK on this version (6.0.alpha1).
The last version of the gem is locked to Rails < 7 so it bundler will not automatically update for you.
use bundle update nonschema_migrations to force it to upgrade
What's Changed
New Contributors
Full Changelog: v5.1.2...v6.0.alpha2
For Rails 7.0.0.alpha2 special release
Because of the funky way that bundler gem dependency specification does not allow me to specify that it's OK to allow the prerelease version of Rails, I am just releasing this as nonschema_migations gem version 6.0.alpha1 (for use with Rails 7.0.0.alpha2-- note it is locked specifically in the gem dependency).
Once Rails 7 is no longer prerelease I will re-release fixing the gemspec file.
• Rails 7 doesn't like having data_migrations have an id column; if you are upgrading, you might want to drop the ID column from the data_migrations table
• Otherwise, new projects on Rails 7.0.0.alpha2 should be OK on this version (6.0.alpha1).
The last version of the gem is locked to Rails < 7 so it bundler will not automatically update for you.
use bundle update nonschema_migrations
to force it to upgrade
Rails 7
• Rails 7 doesn't like having data_migrations have an id column; if you are upgrading, you might want to drop the ID column from the data_migrations
table
• Otherwise, new projects on Rails 7 should be OK on this version (5.5). The last version is locked to Rails < 7 so it bundler will not automatically update for you. use bundle update nonschema_migrations
to force it to upgrade
For Rails 6 including no_op for down migrations
Fixes to Rubygems settings
v5.1.2 v5.1.2