actual_db_schema 0.7.0 → 0.7.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 957b11aa8112a41c4cc875a2c34510e651c9f41b94ab76c86b765f3f89501a27
-  data.tar.gz: b1d2c2a81647bb18b6a1b3bce71691ff3cac4cd809585a4830bc332a3b135df5
+  metadata.gz: eac7885f8774402bb8f0532caf66d4304df61be50ef0c22f1fd8f6ef325b8330
+  data.tar.gz: 8c90d4101e41941a4c247f6af2695e050f450a46435b659c99e1d5fe8fd71929
 SHA512:
-  metadata.gz: 9fc19c47a665af2efc5bc1e5e1d37cf8335f11d5f7c3e248e67cfb5d044d69fd626890b31e539f8f0e0fc3f63bdd36ecd3ce624383c42a1320bed9632a037242
-  data.tar.gz: d1af7d177e1dfbd9f7e69e502e5e55d7b73906c0d63b6a3c125ff4af311994feb3b1c5a97ba9eca321a7a8e2aa791016ee3e8de7baffda598f6eb5dcabb10ade
+  metadata.gz: 794038e111d31a3e99b1a48c3c3a0603498e6492e8b2a8f050d4e9e481debe047d908ff5cae5940789c96c3d76da13a10a841c55834275392e0d08076b4b6b52
+  data.tar.gz: 342ba459e1705c42a64d0f476c50054724a48b212bbba79a82f85a1a4118ac342bac7d0ebab3158bcab58f5d6068c1e4f344f813a6464091e20545815ff09dc3

data/CHANGELOG.md

@@ -1,3 +1,7 @@
+## [0.7.1] - 2024-03-19
+
+- add csv as a dependency since Ruby 3.3 has removed it from the standard library
+
 ## [0.7.0] - 2024-01-18
 
 - db:phantom_migrations displays the branch in which the phantion migration was run

data/Gemfile.lock

@@ -1,9 +1,10 @@
 PATH
   remote: .
   specs:
-    actual_db_schema (0.7.0)
+    actual_db_schema (0.7.1)
       activerecord (>= 6.0.0)
       activesupport (>= 6.0.0)
+      csv
 
 GEM
   remote: https://rubygems.org/
@@ -92,6 +93,7 @@ GEM
     concurrent-ruby (1.2.2)
     connection_pool (2.4.1)
     crass (1.0.6)
+    csv (3.2.8)
     date (3.3.3)
     debug (1.8.0)
       irb (>= 1.5.0)

data/README.md

@@ -4,7 +4,7 @@
 
 Does switching between branches in your Rails app mess up the DB schema?
 
-Keep the DB schema actual across branches in your Rails project. Just install `actual_db_schema` gem and run `db:migrate` in branches as usual. It automatically rolls back the *phantom migrations* (non-relevant to the current branch). No additional steps are needed.
+Keep the DB schema actual across branches in your Rails project. Just install `actual_db_schema` gem and run `db:migrate` in branches as usual. It automatically rolls back the *phantom migrations* (non-relevant to the current branch). No additional steps are needed. It works with both `schema.rb` and `structure.sql`.
 
 ## Why ActualDbSchema
 
@@ -28,9 +28,9 @@ With `actual_db_schema` gem you don't need to care about that anymore. It saves
 
 ### How it solves the issue
 
-This gem stores all run migrations with their code in the `tmp/migrations` folder. Whenever you perform a schema dump, it rolls back the *phantom migrations*.
+This gem stores all run migrations with their code in the `tmp/migrated` folder. Whenever you perform a schema dump, it rolls back the *phantom migrations*.
 
-The *phantom migrations* list is the difference between the migrations you've executed (in the `tmp/migrations` folder) and the current ones (in the `db/migrate` folder).
+The *phantom migrations* list is the difference between the migrations you've executed (in the `tmp/migrated` folder) and the current ones (in the `db/migrate` folder).
 
 Therefore, all you do is run rails `db:migrate` in your current branch. `actual_db_schema` will ensure the DB schema is up-to-date. You'll never have an inaccurate `schema.rb` file again.
 
@@ -63,7 +63,15 @@ The gem offers the following rake tasks that can be manually run according to yo
 
 After checking out the repo, run `bin/setup` to install dependencies. Then, run `rake test` to run the tests. You can also run `bin/console` for an interactive prompt that will allow you to experiment.
 
-To install this gem onto your local machine, run `bundle exec rake install`. To release a new version, update the version number in `version.rb`, update the CHANGELOG, make the commit, push, and then run `bundle exec rake release`, which will create a git tag for the version, push git commits and the created tag, and push the `.gem` file to [rubygems.org](https://rubygems.org).
+To install this gem onto your local machine, run `bundle exec rake install`.
+
+To release a new version do the following in the order:
+
+- update the version number in `version.rb`;
+- update the CHANGELOG;
+- `bundle install` to update `Gemfile.lock`;
+- make the commit and push;
+- run `bundle exec rake release`. This will create a git tag for the version, push git commits and the created tag, and push the `.gem` file to [rubygems.org](https://rubygems.org).
 
 ## Contributing
 

data/actual_db_schema.gemspec

@@ -38,6 +38,7 @@ Gem::Specification.new do |spec|
   # Uncomment to register a new dependency of your gem
   spec.add_runtime_dependency "activerecord", ">= 6.0.0"
   spec.add_runtime_dependency "activesupport", ">= 6.0.0"
+  spec.add_runtime_dependency "csv"
 
   spec.add_development_dependency "appraisal"
   spec.add_development_dependency "debug"

data/lib/actual_db_schema/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module ActualDbSchema
-  VERSION = "0.7.0"
+  VERSION = "0.7.1"
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: actual_db_schema
 version: !ruby/object:Gem::Version
-  version: 0.7.0
+  version: 0.7.1
 platform: ruby
 authors:
 - Andrei Kaleshka
 autorequire:
 bindir: exe
 cert_chain: []
-date: 2024-01-18 00:00:00.000000000 Z
+date: 2024-03-19 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: activerecord
@@ -38,6 +38,20 @@ dependencies:
     - - ">="
       - !ruby/object:Gem::Version
         version: 6.0.0
+- !ruby/object:Gem::Dependency
+  name: csv
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '0'
+  type: :runtime
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '0'
 - !ruby/object:Gem::Dependency
   name: appraisal
   requirement: !ruby/object:Gem::Requirement