Kasugaijin's open-source Ruby on Rails production app that enables dog rescue organisation staff in Mexico to post dogs and receive applications for adoption from users in USA and Canada..
27
stars
9
forks
source link
Upgrade to latest Rails patch version (7.0.6) #177
Reason: 7.0.5.1 included a security patch for redirect_to that @kasugaijin wanted to include, and we might as well upgrade to the latest patch for 7.0
Summary of changes:
Changed rails gem version to minimum of 7.0.6
Updated rails and associated dependencies
Steps skipped:
Did not update Ruby at all
I did not run bundle update because it would indiscriminately update all the gems
This can potentially break a lot of things, especially if you don't specify the range of versions for certain gems
I did only update the rails gem, which updated various gems directly related to it (see the changes for Gemfile.lock)
Running the update task generated a file for 7.0 defaults, which is already enabled in your app
So no change at all was made, since 7.0 defaults are already enable in your app, and you also have custom configs
There is no need to override your custom configurations as it will break your app
The update task also generated 3 migrations, but these migrations already exist since your app was already on version 7.0.x (when you added the active storage tables)
I decided to remove these as they were simply unnecessary migrations that do not add anything
Additional information
This was reverted by cf4d076970612bb2196689437e0d17cb01a04249, see #175 for a bit more details on the revert.
This restores commit 2b0711a755b681bf1e964063578e0e27e9f65203.
Closes Issue
167
Feel free to let me know if you need more information, or if you require that I take a different approach. I would be glad to do either one!
Reason:
7.0.5.1included a security patch forredirect_tothat @kasugaijin wanted to include, and we might as well upgrade to the latest patch for7.0Summary of changes:
railsgem version to minimum of7.0.6railsand associated dependenciesSteps skipped:
bundle updatebecause it would indiscriminately update all the gemsrailsgem, which updated various gems directly related to it (see the changes forGemfile.lock)7.0defaults, which is already enabled in your app7.0defaults are already enable in your app, and you also have custom configs7.0.x(when you added the active storage tables)Additional information This was reverted by cf4d076970612bb2196689437e0d17cb01a04249, see #175 for a bit more details on the revert.
This restores commit 2b0711a755b681bf1e964063578e0e27e9f65203.
Closes Issue
167
Feel free to let me know if you need more information, or if you require that I take a different approach. I would be glad to do either one!