Rails 5.0: Action Cable, API mode, and so much more After six months of polish, four betas, and two release candidates, Rails 5.0 is finally done! It’s taken hundreds of contributors and thousands of commits to get here, but what a destination: Rails 5.0 is without a doubt the best, most complete version of Rails yet. It’s incredible that this community is still going so strong after so long. Than
We’re happy to announce Rails 5 RC2 has been released. We continue to work torwards the final Rails 5 release. Between RC1 and RC2 Rails got 91 commits! That’s a whole lot of bug fixes and polishing! To view the changes for each gem, please read the changelogs on GitHub: Action Mailer CHANGELOG Action Pack CHANGELOG Action View CHANGELOG Active Model CHANGELOG Active Record CHANGELOG Active Suppor
Ruby on Rails’ phenomenal rise to prominence owed much of its lift-off to novel technology and timing. But technological advantages erode over time, and good timing doesn’t sustain movements alone over the long term. So a broader explanation of how Rails has continued to not only stay relevant but to grow its impact and community is needed. I propose that the enduring enabler has been and remains
Rails 5.0.0.beta1: Action Cable, API mode, Rails command Rails 5.0! Can you believe it? We only just celebrated the tenth anniversary of Rails 1.0 a few days ago. Time flies when you’re having fun with good friends, and we’ve never had more fun or better friends in the Rails community, so no wonder it’s going swoosh! Now this is just the first beta release, but Rails 5.0.0.beta1 is already running
We’re getting really close to signing off on Rails 4.1.0, but we need your help to push it the last mile. Today we’re putting out the first (and, with luck, only) release candidate of Rails 4.1.0. It would be swell if you would try it out and tell us where it breaks. It’s already in really good shape (we’ve been running beta1 and forward in production for Basecamp for months), but still, let’s mak
Rails 3.2.17, 4.0.3 and 4.1.0.beta2 have been released! Hi everyone! Rails 3.2.17, 4.0.3 and 4.1.0.beta2 have been released! These three releases contain important security fixes, so please upgrade as soon as possible! In order to make upgrading as smooth as possible, we’ve only included commits directly related to each security issue. The security fixes in 3.2.17 are: CVE-2014-0081 CVE-2014-0082
Hi everyone! Rails 3.2.16 and 4.0.2 have been released! These two releases contain important security fixes, so please upgrade as soon as possible! In order to make upgrading as smooth as possible, we’ve only included commits directly related to each security issue. The security fixes in 3.2.16 are: CVE-2013-6417 CVE-2013-4491 CVE-2013-6415 CVE-2013-6414 The security fixes in 4.0.2 are: CVE-2013-6
Good news everyone! Rails version 3.2.6 has been released. This release of Rails contains two important security fixes: CVE-2012-2694 Ruby on Rails Unsafe Query Generation Risk in Ruby on Rails CVE-2012-2695 Ruby on Rails SQL Injection Please note that the last round of security fixes DO NOT cover the situations that these patches fix. Therefore it is suggested that all users upgrade immediately.
Rails 4.0 is finally ready after a thorough process of betas and release candidates. It’s an amazing new version packed with new goodies and farewells to old features past their expiration date. A big focus has been on making it dead simple to build modern web applications that are screaming fast without needing to go the client-side JS/JSON server route. Much of this work was pioneered for Rails
We’re almost at the end of the road for Rails 4.0.0. This is intended to be the last release candidate before the final version is released. We have just under a hundred commits in since RC1. All just fixing regressions since the last release. As last time, please give this release candidate an honest try. This is the version we’re going to ship on June 25th unless people find and report blocking
Hi everyone, Rails 3.2.9 has been released without new changes since 3.2.9.rc3. IMPORTANT! A DoS attack was recently found in Ruby that uses specially-crafted input to dramatically reduce the performance of hashes, thus using up lots of CPU time. Rails applications may be vulnerable to an attacker sending a specially-crafted HTTP request to exploit this. A good way to limit the effectiveness of su
Rails 3.2 RC1: Faster dev mode & routing, explain queries, tagged logger, store Once you’ve boarded the Rails train, you just know that every stop along the way is going to be a good time. This release candidate is no different and we’ve packed it with loving goodies without making upgrading a hassle. Faster dev mode & routing The most noticeable new feature is that development mode got a ton and
The forthcoming 3.2.x release series will be the last branch of Rails that supports Ruby 1.8.7. There’s a new 3-2-stable branch in git to track the changes we need until 3.2.0 final is release and for managing point releases after that. So for now you should stop floating on rails/master if your application is not compatible with Ruby 1.9.3. We have updated the version numbers to indicate this bac
Hi everyone, Rails 3.1.1 has been released. This release requires at least sass-rails 3.1.4 CHANGES Action Mailer No changes Action Pack stylesheet_link_tag(‘/stylesheets/application’) and similar helpers doesn’t throw Sprockets::FileOutsidePaths exception anymore [Santiago Pastorino] Ensure default_asset_host_protocol is respected, closes #2980. [José Valim] Changing rake db:schema:dump to run :e
Hi everybody! It’s been 3 Months since RailsConf, so I think it’s time we released Rails 3.1.0. So, here it is! I’ve released Rails 3.1.0! CHANGES For a much more attractive and easy to read list of changes, please check out the awesome Rails 3.1.0 Release Notes on the Rails Guides site. For a less attractive list of changes, please continue to read! Here are some highlights of the major changes i
As I promised at RailsConf, we’re finally good to go on the Rails 3.1: Release Candidate. This is a fantastically exciting release. We have three new star features and an even greater number of just awesome improvements. First the stars: The Asset Pipeline The star feature of 3.1 is the asset pipeline powered by Sprockets 2.0. It makes CSS and JavaScript first-class code citizens and enables prope
Rails 3.0 has been underway for a good two years, so it’s with immense pleasure that we can declare it’s finally here. We’ve brought the work of more than 1,600 contributors together to make everything better, faster, cleaner, and more beautiful. This third generation of Rails has seen thousands of commits, so picking what to highlight was always going to be tough and incomplete. But here’s a choi
High off Baltimore Pandemic and Yellow Tops, I believe we promised a release candidate shortly after RailsConf. As things usually go in open source, we gorged ourselves on fixes and improvements instead. But all to your benefit. We’ve had 842 commits by 125 authors since the release of the last beta! Now it’s time to just say good is good enough, otherwise we could keep on with this forever. So pl
The 2.3.7 release slipped out the door too hastily. Fixing compatibility with the rails_xss plugin inadvertently forced everyone to use it. Facepalm. I apologize for wasting a chunk of your day on installing what ought to have been a patch-level update only to find it breaks your app. That’s well out of line with our stable release process and it’s my fault for stepping out of it. I got caught up
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く