Welcome to the spookiest issue of This week in Rails, your weekly inside scoop of interesting commits, pull requests and more from Rails.
Before diving into this week's changes, I just wanted to mention that we are assembling a team of editors for this newsletter – if you are interesting in helping to deliver the latest Rails news to over 1200 readers every week, please shoot me an email!
In addition to the security releases, a new beta for 4.2.0 was also released, containing all the issues that was reported and fixed since beta2. If all goes well, we should see a Release Candidate for 4.2 very soon!
We previously reported about a new --skip-gems option in the Rails generator. It was ultimately decided that it was easy enough to remove a single entry from the Gemfile, and it wasn't worthwhile to introduce a new option (and the associated complexity) for that purpose.
On the bright side, the more intuitive and convenient --skip-turbolinks option is back!
It was reported that the filiesize of the gems in the 4.2.0.beta4 release was unexpectedly large. This was caused by the guides output getting included in the gems by accident. The problem should now be corrected for all future releases.
You have probably bumped into the "Circular dependency detected" message at some point . With this commit, the error message in some of these cases should be more accurate (thus more helpful). See @fxn's comment for more background.
Currently, Active Record maintains a whitelist of "truthy" values, so that when you assigned anything outside of that list to a boolean attribute, it will be type casted to false. In the future, this behavior will be flipped to better match how Ruby handles truthiness.
And that's it for this issue of This week in Rails. As always, there are a lot more changes on Rails than what I can cover in this newsletter, so I encourage you to check them out yourself!
If you have any feedback for me, please feel free to email me or let me know on twitter! Thank you for reading, and Happy Halloween!