Here's release 1.5.0 with:
- A new GraphQL API that will allow write operations
- Easier customization of valid zipcodes
- Improvements in notifications and newsletters
- New options to simplify code customization
- Debian Buster and Debian Bullseye support in the installer
- Many bug fixes and small improvements
Check the Changelog to see all the changes. Please take your time reading all referenced pull requests to understand new features and changes.
Updating your fork
Check how to keep your fork updated; if you're updating from release 1.4.1 you can just:
git checkout master
git pull
git checkout -b release
git fetch upstream tag 1.5.0
git merge 1.5.0
git checkout master
git merge release
git branch -d release
git push
⚙️ After deploying the new version, execute the release tasks:
bin/rake consul:execute_release_tasks RAILS_ENV=production
⚠️ We've finished replacing Paperclip with Active Storage to manage attachments. If you're upgrading from version 1.4.x, make sure you execute the release tasks immediately after upgrading, since you'll get 500 errors in many places if you don't.
Even if we've removed Paperclip, there might be references to paperclip attachments in any existing content (for example, custom pages) and so old attachment files generated by Paperclip should be removed with care or even kept indefinitely.
⚠️ We've removed the newrelic and rollbar gem dependencies from our Gemfile. If you're using the services provided by newrelic, make sure you edit the Gemfile_custom in order to uncomment it and restore the config/newrelic.yml file (which we deleted in pull request #4645). In a similar way, if you're using the services provided by rollbar, make sure you edit the Gemfile_custom in order to uncomment it and restore the config/initializers/rollbar.rb file (which we deleted in the mentioned pull request #4645)
⚠️ We've changed the way to define valid postal codes for the users verification. In the past, you had to change the code in app/models/custom/verification/residence.rb. Now CONSUL administrators can define postal codes in the settings section of the administration.
If you had already defined custom postal codes in app/models/custom/verification/residence.rb, when you get a conflict when merging these changes, keep your changes; they'll most probably still work but, depending on your implementation, the postal codes defined by administrators might be ignored. In this case, you might want to double-check your custom changes still work as expected and consider removing this custom code and use the setting instead. In order to ease the transition, the setting allows regular expressions. When using regular expressions, omit the ^ and $ characters (or the Ruby equivalents, \A and \Z); we're already adding them in the code. For example, if your code was postal_code =~ /^280[0-9]{2}$/, use 280[0-9]{2} in the setting.
⚠️ We've updated the GraphQL API so it no longer uses a deprecated DSL (pull request #4766). If you've added custom fields or models to your GraphQL API, you'll need to update those changes to the new DSL.
⚠️ JavaScript files in the app/assets/javascripts/custom/ folder are now automatically required. If you've added files to that folder that aren't present in CONSUL, like homepage_enhancements.js, and are requiring them with //= require homepage_enhancements, you need to delete the line saying //= require homepage_enhancements. You don't have to delete this line if the files already exists in CONSUL (for example, you wouldn't have to delete //= require globalize if you had a file in app/assets/javascripts/custom/globalize.js because the file app/assets/javascripts/globalize.js already exists in CONSUL).