bullet_train 1.10.0 → 1.12.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 476b5c3d4c9b745aa40ae138671c83c98654acd7ebc3070928778413313f9f4f
-  data.tar.gz: 472afd1105a7d81eca8465b01771591c84b10da24c8df90772785303c71a7d88
+  metadata.gz: bd6fdf70fe639d436c4c3a30bdb7334486a06fd164cc1143cfb7c61f594807a1
+  data.tar.gz: 26bfbb1745af219cc5e1a88c63960091e988060b99e6d8c663849a182a2e2d75
 SHA512:
-  metadata.gz: 4749dedcfb1e22982f6288e65f16deb037a3647041cc62027e85af3f6ce152a86298c65f4351c0b1f8ad6730196ab8781433f75402059dabebfdae24fd6d281b
-  data.tar.gz: 25a8e4e1fb083356e8511728c7defe161070561a6d80649ef350806b7578b60833fd14c7867d3b97ab5ccb96bcfd7dfa7c922a79ddf26a4a6edfb0aab4046a6c
+  metadata.gz: 405d7b2680925803f52982019d1311f494b4bfb0d798b45898fc98afe6a2a0e2ce49e83af6ed2dc73fe6ba6f693a699a439e923d9ace5715e35fd68d3c4b2c59
+  data.tar.gz: 1889ac585f748aaf37f4917750e5d4d26e8214a7aa164d8fe45354eab0f24d182ee3dc7bde4b2f45be3c3fe2b08a6d4788539b6bc95b5c14f66c969b79d55397

data/docs/upgrades.md

@@ -14,8 +14,49 @@
 
 ## The Stepwise Upgrade Method
 
-This method will ensure that the version of the Bullet Train gems that your app uses will stay in sync with the application framework provided by the starter repo.
-If you've ever upgraded a Rails app from version to version this process should feel fairly similar.
+This method will ensure that the version of the Bullet Train gems that your app uses will stay in sync
+with the application framework provided by the starter repo. If you've ever upgraded a Rails app from
+version to version this process should feel fairly similar.
+
+We recommend gradually upgrading one version at a time. This makes it relatively easy to pinpoint any
+specific changes that may cause problems with your app. Trying to jump a bunch of versions at once can
+make it hard to figure out exactly where problems are coming from.
+
+The basic idea is that if you're on `1.4.0` you should upgrade next to `1.4.1`, run your tests, deploy
+those changes and make sure things are working well. Then upgrade to `1.4.2` etc... If you update regularly
+then each individual update should be relatively small.
+
+For performing the upgrade you have two options:
+
+* [Use the GitHub Action we provide to create an upgrade Pull Request](./upgrades#github-action)
+* [Performa a manual upgrade via git](./upgrades#manual-upgrade)
+
+## GitHub Action
+
+First go to the "Actions" tab on your project and then click on the "↗️  Create Bullet Train Upgrade PR" link on the left.
+
+![Find the GitHub Action](https://bullettrain.co/upgrade-images/1-find-action.png)
+
+Then on the right side of the page click the "Run workflow" button and enter the target version. `1.4.1` for instance.
+If you don't enter a version number then the action will target the latest version available on GitHub.
+
+![Run the GitHub Action](https://bullettrain.co/upgrade-images/2-run-action.png)
+
+A few seconds after you click the green "Run workflow" button you should see a new action running.
+
+![Running Action](https://bullettrain.co/upgrade-images/3-running-action.png)
+
+Once the action has completed you should have a new Pull Request that will perform the upgrade.
+
+![Upgrade PR](https://bullettrain.co/upgrade-images/4-upgrade-pr.png)
+
+You should review the contents of the pull request, run the tests, and pull down the branch to run it locally.
+
+[Here's a sample of the kind of Pull Request that you'll get. This is from a recent upgrade of the Bullet Train demo site.](https://github.com/bullet-train-co/bullet_train-demo_site/pull/47)
+
+The GitHub action is basically an automated version of the manual upgrade process described below.
+
+## Manual Upgrade
 
 ## Pulling Updates from the Starter Repository
 

data/lib/bullet_train/version.rb

@@ -1,3 +1,3 @@
 module BulletTrain
-  VERSION = "1.10.0"
+  VERSION = "1.12.0"
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: bullet_train
 version: !ruby/object:Gem::Version
-  version: 1.10.0
+  version: 1.12.0
 platform: ruby
 authors:
 - Andrew Culver
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2024-11-21 00:00:00.000000000 Z
+date: 2024-12-10 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: standard
@@ -24,6 +24,20 @@ dependencies:
     - - ">="
       - !ruby/object:Gem::Version
         version: '0'
+- !ruby/object:Gem::Dependency
+  name: simplecov
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '0'
+  type: :development
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '0'
 - !ruby/object:Gem::Dependency
   name: rails
   requirement: !ruby/object:Gem::Requirement
@@ -109,7 +123,7 @@ dependencies:
       - !ruby/object:Gem::Version
         version: '0'
 - !ruby/object:Gem::Dependency
-  name: bullet_train-routes
+  name: bullet_train-fields
   requirement: !ruby/object:Gem::Requirement
     requirements:
     - - ">="
@@ -694,7 +708,6 @@ files:
 - config/locales/en/teams.en.yml
 - config/locales/en/users.en.yml
 - config/locales/localization.en.yml
-- config/models/roles.yml
 - config/routes.rb
 - db/migrate/20161115160419_devise_create_users.rb
 - db/migrate/20161116003852_add_api_key_to_user.rb

data/config/models/roles.yml

@@ -1,37 +0,0 @@
-default:
-  models:
-    Team: read
-    Document: read
-    Membership:
-      - read
-      - search
-
-crud_role:
-  models:
-    Team: crud
-
-editor:
-  models:
-    Scaffolding::AbsolutelyAbstract::CreativeConcept:
-      - read
-      - update
-
-manager:
-  includes:
-    - editor
-
-supervisor:
-  includes:
-    - manager
-
-admin:
-  includes:
-    - editor
-  manageable_roles:
-    - admin
-    - editor
-  models:
-    Team: manage
-    Membership: manage
-    Document: manage
-    Scaffolding::AbsolutelyAbstract::CreativeConcept: manage