el-gem-updates into main Trying to keep on top of some of the more important gem updates. See each commit for slightly more details. These were all tested using rspec and also deploying to our staging server and clicking around.
This encompases two rails releases: - [8.0.5](https://github.com/rails/rails/releases/tag/v8.0.5) - [8.1.3](https://github.com/rails/rails/releases/tag/v8.1.3) The full list of updated gems is: - erb 6.0.2 (was 6.0.1) - bigdecimal 4.1.1 (was 4.0.1) - rack 3.2.6 (was 3.2.5) - zeitwerk 2.7.5 (was 2.7.4) - timeout 0.6.1 (was 0.5.0) - json 2.19.3 (was 2.12.2) - minitest 6.0.3 (was 6.0.1) - net-imap 0.6.3 (was 0.5.12) - rack-session 2.1.2 (was 2.1.1) - nokogiri 1.19.2 (arm64-darwin) (was 1.19.1) - loofah 2.25.1 (was 2.25.0) - rails-html-sanitizer 1.7.0 (was 1.6.2) - activesupport 8.1.3 (was 8.1.2.1) - activemodel 8.1.3 (was 8.1.2.1) - actionview 8.1.3 (was 8.1.2.1) - activejob 8.1.3 (was 8.1.2.1) - activerecord 8.1.3 (was 8.1.2.1) - actionpack 8.1.3 (was 8.1.2.1) - railties 8.1.3 (was 8.1.2.1) - actioncable 8.1.3 (was 8.1.2.1) - actionmailer 8.1.3 (was 8.1.2.1) - activestorage 8.1.3 (was 8.1.2.1) - actionmailbox 8.1.3 (was 8.1.2.1) - action_text-trix 2.1.18 (was 2.1.17) - actiontext 8.1.3 (was 8.1.2.1) - rails 8.1.3 (was 8.1.2.1)
For being a major version change, the changes were quite minor
08f63d4959/History.md
The only breaking change was the exact interface puma listens on, which falls
back to the old interface anyway.
https://github.com/ged/ruby-pg/blob/master/CHANGELOG.md Tested by deploying to our acceptance branch
Mostly just refreshing the underlying javascript and a few bug fixes https://github.com/hotwired/turbo-rails/releases
No due date set.
No dependencies set.
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?