Since our last 0.11.1 bug fix release, many users and core developers have been continuing to find and fix bugs as well as improve our documentation. Today we release 0.11.2 which is the second bug fix release since our huge 0.11.0 release. We’d like to release another wave of bug fixes again next month since we know we still have a lot of issues to address. The following is a detailed list of fixes in the details.
- FIX #1232 Padrino::Server – call expand_path on PID file option (@sshaw)
- FIX #1234 Create table migration should be also timestamped if configured (@udzura)
- FIX #1228 Allow for block arg to StandardFormBuilder.label (@sshaw)
- FIX #1235 error of routing when using provides :any and Accept contains / (@tyabe)
- FIX #1196 Remove Ohm monkey patch and include Padrino::Ohm::Validator (@lastcanal)
- FIX #1236 Pass our logger to rack-protection for csrf (@dariocravero)
- FIX #1246 missing translation for Russian (@silentvick)
- NEW #1062 add configurable #app method for rack-test closes (@achiu)
- FIX #1252 translations for japanese (@tyabe, @namusyaka)
- FIX Specify full class name for migrations to fix failing migrations (@Ortuna)
- FIX #1279 Datamapper rake task to pass arguments (@Ortuna)
- FIX #1281 Documentation fixes to various areas (@matthias-guenther)
- FIX #1269 issue with tilt version (@ujifgc)
- FIX #1283 issue with html_safe and form builder (@ujifgc)
- NEW #1285 Add :file option for delivering mail docs (@matthias-guenther)
- FIX #1287 Lock minitest version from going to 5 (@Ortuna)
- FIX #1288 Http router fix unicode (@Ortuna)
- FIX #698 Sqlite adding an extra “/” to the connection string for windows (@dariocravero)
Want to give a special thanks to the key contributors for this release, working tirelessly to make Padrino better: @ujifgc, @dariocravero, @Ortuna, @matthias-guenther, @tyabe and @sshaw. Thanks so much!
Please do report any issues you have. We are working very actively on Padrino and want to make the framework as stable and reliable as possible. That concludes the changelog for this release. As always if you want to keep up with Padrino updates, be sure to follow us on twitter: @padrinorb, join us on IRC at “#padrino” on freenode or open an issue on GitHub.