bullet_train 1.10.0 → 1.11.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: 476b5c3d4c9b745aa40ae138671c83c98654acd7ebc3070928778413313f9f4f
4
- data.tar.gz: 472afd1105a7d81eca8465b01771591c84b10da24c8df90772785303c71a7d88
3
+ metadata.gz: 892c29ff71cfaa92f465dcdda297c34c767123aebc2a9b9950b04136dd327eef
4
+ data.tar.gz: be30f624783ec02d7924d7312c0697097e1f968cc28e34ca878d86add2d2cc40
5
5
  SHA512:
6
- metadata.gz: 4749dedcfb1e22982f6288e65f16deb037a3647041cc62027e85af3f6ce152a86298c65f4351c0b1f8ad6730196ab8781433f75402059dabebfdae24fd6d281b
7
- data.tar.gz: 25a8e4e1fb083356e8511728c7defe161070561a6d80649ef350806b7578b60833fd14c7867d3b97ab5ccb96bcfd7dfa7c922a79ddf26a4a6edfb0aab4046a6c
6
+ metadata.gz: a2f4d79b3f5dcbcc89d7058836bbb7ff22c41b47917a82caadb051f11fd4cfc03e34f7bedb1ea94ed538525d60c0be9f0c09373c920f3a8fded04659944142f3
7
+ data.tar.gz: 0eb2e4f26cb7eb9f84523b01717698e5f672d74fa2c5e3b319b7258b0c0318c76d33828ce520e768c137c1c6bc9351b7db5a72c833b5e90ffcb692fafe5ae7cb
data/docs/upgrades.md CHANGED
@@ -14,8 +14,49 @@
14
14
 
15
15
  ## The Stepwise Upgrade Method
16
16
 
17
- 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.
18
- If you've ever upgraded a Rails app from version to version this process should feel fairly similar.
17
+ This method will ensure that the version of the Bullet Train gems that your app uses will stay in sync
18
+ with the application framework provided by the starter repo. If you've ever upgraded a Rails app from
19
+ version to version this process should feel fairly similar.
20
+
21
+ We recommend gradually upgrading one version at a time. This makes it relatively easy to pinpoint any
22
+ specific changes that may cause problems with your app. Trying to jump a bunch of versions at once can
23
+ make it hard to figure out exactly where problems are coming from.
24
+
25
+ The basic idea is that if you're on `1.4.0` you should upgrade next to `1.4.1`, run your tests, deploy
26
+ those changes and make sure things are working well. Then upgrade to `1.4.2` etc... If you update regularly
27
+ then each individual update should be relatively small.
28
+
29
+ For performing the upgrade you have two options:
30
+
31
+ * [Use the GitHub Action we provide to create an upgrade Pull Request](./upgrades#github-action)
32
+ * [Performa a manual upgrade via git](./upgrades#manual-upgrade)
33
+
34
+ ## GitHub Action
35
+
36
+ First go to the "Actions" tab on your project and then click on the "↗️ Create Bullet Train Upgrade PR" link on the left.
37
+
38
+ ![Find the GitHub Action](https://bullettrain.co/upgrade-images/1-find-action.png)
39
+
40
+ Then on the right side of the page click the "Run workflow" button and enter the target version. `1.4.1` for instance.
41
+ If you don't enter a version number then the action will target the latest version available on GitHub.
42
+
43
+ ![Run the GitHub Action](https://bullettrain.co/upgrade-images/2-run-action.png)
44
+
45
+ A few seconds after you click the green "Run workflow" button you should see a new action running.
46
+
47
+ ![Running Action](https://bullettrain.co/upgrade-images/3-running-action.png)
48
+
49
+ Once the action has completed you should have a new Pull Request that will perform the upgrade.
50
+
51
+ ![Upgrade PR](https://bullettrain.co/upgrade-images/4-upgrade-pr.png)
52
+
53
+ You should review the contents of the pull request, run the tests, and pull down the branch to run it locally.
54
+
55
+ [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)
56
+
57
+ The GitHub action is basically an automated version of the manual upgrade process described below.
58
+
59
+ ## Manual Upgrade
19
60
 
20
61
  ## Pulling Updates from the Starter Repository
21
62
 
@@ -1,3 +1,3 @@
1
1
  module BulletTrain
2
- VERSION = "1.10.0"
2
+ VERSION = "1.11.0"
3
3
  end
metadata CHANGED
@@ -1,14 +1,14 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: bullet_train
3
3
  version: !ruby/object:Gem::Version
4
- version: 1.10.0
4
+ version: 1.11.0
5
5
  platform: ruby
6
6
  authors:
7
7
  - Andrew Culver
8
8
  autorequire:
9
9
  bindir: bin
10
10
  cert_chain: []
11
- date: 2024-11-21 00:00:00.000000000 Z
11
+ date: 2024-11-25 00:00:00.000000000 Z
12
12
  dependencies:
13
13
  - !ruby/object:Gem::Dependency
14
14
  name: standard
@@ -109,7 +109,7 @@ dependencies:
109
109
  - !ruby/object:Gem::Version
110
110
  version: '0'
111
111
  - !ruby/object:Gem::Dependency
112
- name: bullet_train-routes
112
+ name: bullet_train-fields
113
113
  requirement: !ruby/object:Gem::Requirement
114
114
  requirements:
115
115
  - - ">="
@@ -694,7 +694,6 @@ files:
694
694
  - config/locales/en/teams.en.yml
695
695
  - config/locales/en/users.en.yml
696
696
  - config/locales/localization.en.yml
697
- - config/models/roles.yml
698
697
  - config/routes.rb
699
698
  - db/migrate/20161115160419_devise_create_users.rb
700
699
  - db/migrate/20161116003852_add_api_key_to_user.rb
@@ -1,37 +0,0 @@
1
- default:
2
- models:
3
- Team: read
4
- Document: read
5
- Membership:
6
- - read
7
- - search
8
-
9
- crud_role:
10
- models:
11
- Team: crud
12
-
13
- editor:
14
- models:
15
- Scaffolding::AbsolutelyAbstract::CreativeConcept:
16
- - read
17
- - update
18
-
19
- manager:
20
- includes:
21
- - editor
22
-
23
- supervisor:
24
- includes:
25
- - manager
26
-
27
- admin:
28
- includes:
29
- - editor
30
- manageable_roles:
31
- - admin
32
- - editor
33
- models:
34
- Team: manage
35
- Membership: manage
36
- Document: manage
37
- Scaffolding::AbsolutelyAbstract::CreativeConcept: manage