<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <title type="text" xml:lang="en">Riding Rails</title>
  <link type="application/atom+xml" href="http://weblog.rubyonrails.org/feed/" rel="self" />
  <link type="text" href="http://weblog.rubyonrails.org/" rel="alternate" />
  <updated>2013-05-01T14:41:54-07:00</updated>
  <id>http://weblog.rubyonrails.org/</id>
  
  <entry>
    <title>Rails 4.0: Release Candidate 1 released!</title>
    <author>
      <name>dhh</name>
    </author>
    <link href="http://weblog.rubyonrails.org/2013/5/1/Rails-4-0-release-candidate-1/"/>
    <updated>2013-05-01T15:30:00-07:00</updated>
    <id>http://weblog.rubyonrails.org/2013/5/1/Rails-4-0-release-candidate-1/</id>
    <content type="html"><![CDATA[<p>Just in time for the opening of RailsConf, we managed to push out the first release candidate of Rails 4.0. This incorporates no less than 1,368 commits since beta 1. You can see <a href="https://github.com/rails/rails/compare/v4.0.0.beta1...v4.0.0.rc1">the full list of changes on Github</a>. If you're interested in a high-level review of what's in Rails 4.0, please see <a href="http://weblog.rubyonrails.org/2013/2/25/Rails-4-0-beta1/">the announcement we made for beta 1</a>.</p>

<p>As last time, please give this release candidate an honest try. This is pretty much the version we're going to ship unless people find and report blocking issues. Depending on how much stuff is unearthed, we expect that the final version could drop in as little as 3-4 weeks. Please report all the issues you find on the <a href="https://github.com/rails/rails/issues?state=open">Rails issue tracker</a>.</p>

<p>We're still working on the <a href="http://edgeguides.rubyonrails.org/upgrading_ruby_on_rails.html#upgrading-from-rails-3-2-to-rails-4-0">upgrade guide from 3.2 to 4.0</a>, but that's a good place to start for help on how to do it. We're also so lucky to have many authors and screencasters ready with material for 4.0. In the books department, you'll find Rails 4.0-ready versions of <a href="http://pragprog.com/book/rails4/agile-web-development-with-rails">Agile Web Development with Rails</a> and <a href="http://pragprog.com/book/jvrails2/crafting-rails-applications">Crafting Rails Applications</a>. For screencasts, checkout the new <a href="http://rails4.codeschool.com/videos">Rails 4: Zombie Outlaws</a> and <a href="http://pragmaticstudio.com/rails">Mike Clark's Rails 4 class</a>. There's new material and books coming out all the time from a variety of other authors and broadcasters, so we're really in good shape with training material timed for the release this time!</p>

<p>As always, install the release with <code>gem install rails --version 4.0.0.rc1 --no-ri --no-rdoc</code> or depend on the <a href="https://github.com/rails/rails/tree/v4.0.0.rc1">v4.0.0.rc1 tag</a>. We also have a new <a href="https://github.com/rails/rails/tree/4-0-stable">4-0-stable branch</a>. Master is now safe to move on to developing features for 4.1.</p>

<p>Go West, friends!</p>
]]></content>
  </entry>
  
  <entry>
    <title>Google Summer of Code 2013</title>
    <author>
      <name>Andrew White</name>
    </author>
    <link href="http://weblog.rubyonrails.org/2013/4/10/google-summer-of-code-2013/"/>
    <updated>2013-04-10T09:00:00-07:00</updated>
    <id>http://weblog.rubyonrails.org/2013/4/10/google-summer-of-code-2013/</id>
    <content type="html"><![CDATA[<p>We're pleased to announce, Ruby on Rails has been accepted into Google Summer of Code 2013 as a <a href="http://www.google-melange.com/gsoc/accepted_orgs/google/gsoc2013">mentoring organization</a>. What does this mean to you? Potentially, if you're the right person, you can get <strong>paid</strong> to work on Rails this summer! The "right person" in this case is one who is at least 18 years old (sorry, Google's rule, not ours!) on or before May 27, 2013; a full or part-time college student; and passionate about improving Rails.</p>

<p>We're building a potential list of <a href="https://github.com/rails/gsoc2013/wiki/Ideas">project ideas</a> on a GitHub wiki, but we welcome other interesting proposals. If your proposal gets accepted, Google will pay you $5000 over the course of three months to work on the code. If you're interested, head over to the <a href="http://www.google-melange.com/gsoc/homepage/google/gsoc2013">GSoC site</a> and start reading about the process. Student applications can be submitted starting April 22 and the deadline is May 3.</p>

<p>If you're wondering what's involved in becoming a GSoC student then the <a href="http://en.flossmanuals.net/GSoCStudentGuide/">Google Student Guide</a> has all the details on what's expected and what you will gain from taking part. Any further questions can be directed either to the <a href="https://groups.google.com/d/forum/rubyonrails-gsoc">mailing list</a> or to <a href="mailto:andyw@pixeltrix.co.uk">me</a> directly.</p>

<p>What if you're not a student? You can still help out by discussing ideas on the special <a href="https://groups.google.com/d/forum/rubyonrails-gsoc">mailing list</a> we've setup for this year's program. Or if you've got previous experience of contributing to Rails and are ready to make a strong commitment to help out the next generation of developers, you can <a href="http://www.google-melange.com/gsoc/accepted_orgs/google/gsoc2013">apply to be a mentor</a>.</p>

<p>We're looking forward to working with this year's students, and expecting some outstanding contributions to Rails as a result!</p>
]]></content>
  </entry>
  
  <entry>
    <title>[SEC] [ANN] Rails 3.2.13, 3.1.12, and 2.3.18 have been released!</title>
    <author>
      <name>tenderlove</name>
    </author>
    <link href="http://weblog.rubyonrails.org/2013/3/18/SEC-ANN-Rails-3-2-13-3-1-12-and-2-3-18-have-been-released/"/>
    <updated>2013-03-18T00:00:00-07:00</updated>
    <id>http://weblog.rubyonrails.org/2013/3/18/SEC-ANN-Rails-3-2-13-3-1-12-and-2-3-18-have-been-released/</id>
    <content type="html"><![CDATA[<p>Hi everyone!</p>

<p>Rails versions 3.2.13, 3.1.12, and 2.3.18 have been released.  These releases contain important security fixes.  It is recommended users upgrade as soon as possible.</p>

<p>Please check out these links for the security fixes:</p>

<ul>
<li><a href="https://groups.google.com/forum/#!topic/ruby-security-ann/o0Dsdk2WrQ0">CVE-2013-1854 Symbol DoS vulnerability in Active Record</a></li>
<li><a href="https://groups.google.com/forum/?fromgroups=#!topic/rubyonrails-security/4_QHo4BqnN8">CVE-2013-1855 XSS vulnerability in sanitize_css in Action Pack</a></li>
<li><a href="https://groups.google.com/forum/?fromgroups=#!topic/rubyonrails-security/KZwsQbYsOiI">CVE-2013-1856 XML Parsing Vulnerability affecting JRuby users</a></li>
<li><a href="https://groups.google.com/forum/?fromgroups=#!topic/rubyonrails-security/zAAU7vGTPvI">CVE-2013-1857 XSS Vulnerability in the <code>sanitize</code> helper of Ruby on Rails</a></li>
</ul>


<p>All versions of Rails are impacted by one or more of these security issues, but per our <a href="https://groups.google.com/forum/?fromgroups=#!topic/rubyonrails-security/G4TTUDDYbNA">maintenance policy</a>, only versions 3.2.13, 3.1.12, and 2.3.18 have been released.  You can find patches for older versions on each stable branch on GitHub:</p>

<ul>
<li><a href="https://github.com/rails/rails/tree/3-0-stable">Rails 3-0-stable</a></li>
</ul>


<p>as well as with the security advisories.</p>

<p>For other changes in each particular release, please see the CHANGELOG corresponding to that version.  For all commits in each release, please follow the links below:</p>

<ul>
<li><a href="https://github.com/rails/rails/compare/v3.2.12...v3.2.13">Changes in 3.2.13</a></li>
<li><a href="https://github.com/rails/rails/compare/v3.1.11...v3.1.12">Changes in 3.1.12</a></li>
<li><a href="https://github.com/rails/rails/compare/v2.3.17...v2.3.18">Changes in 2.3.18</a></li>
</ul>


<p>Here are the checksums for the released gems:</p>

<h3>3.2.13</h3>

<p><code>
[aaron@higgins dist]$ shasum *3.2.13.gem
72b14536f1717121e8b2a5aa5a06c6194e02c87c  actionmailer-3.2.13.gem
a21166f7c364ff7825bf83f9757c33cc44fa0c00  actionpack-3.2.13.gem
9fa309dee3f87a53764db3aaefe3bbf6f9724ad2  activemodel-3.2.13.gem
469f6b4456d7fa1bf0336d488ad5878a6842e2da  activerecord-3.2.13.gem
0c89382354ffc5b4438ed37434b50d7cbc71d569  activeresource-3.2.13.gem
cdf230b698b28ae1cffb325ecbb9e219645ed68b  activesupport-3.2.13.gem
3785dc8d2af1521baddf2d90b67a9b61b2b31604  rails-3.2.13.gem
ff0607812bead596492272e4a4306ae3e950bdf4  railties-3.2.13.gem
</code></p>

<h3>3.1.12</h3>

<p><code>
[aaron@higgins dist]$ shasum *3.1.12.gem
b3f0ecee33032416170263508ccfb33d5dd65eef  actionmailer-3.1.12.gem
426fcf3f5d4e29ae6bf21f536a97d90d02bf73bb  actionpack-3.1.12.gem
2b01ba8bd85d67ded372f3908b694c1fa1ccb041  activemodel-3.1.12.gem
a3afc58fe3f7448ba09cdacb2046c9e10e474cb4  activerecord-3.1.12.gem
d3402193c0820f016b492162547194f942c96c1a  activeresource-3.1.12.gem
e25ed2f7e055d38b1bed482faf8b563a6b7e3899  activesupport-3.1.12.gem
75c2f85ed1e09d2bd1baa3efab5f097cdaef2a6b  rails-3.1.12.gem
618c5beb85124fbedfe41a72424079700f7a1d2c  railties-3.1.12.gem
</code></p>

<h3>2.3.18</h3>

<p><code>
[aaron@higgins dist]$ shasum *2.3.18.gem
09e361c4c96104303abad5faa4aec72ebe7c19d1  actionmailer-2.3.18.gem
deca0d8352858f734479b54162269e334faada21  actionpack-2.3.18.gem
e385b4b2e863592f9f06ca3248a67a18ea8c7e6c  activerecord-2.3.18.gem
ff4fb4a62c4d4007a6c596edf8f7055147948e60  activeresource-2.3.18.gem
1b9102fa31a47cf66b0c2583c99b707544d42054  activesupport-2.3.18.gem
f4aff07dce1db10ad6145e358344671cc482de70  rails-2.3.18.gem
</code></p>

<p>Happy Monday!</p>

<p>&lt;3&lt;3&lt;3</p>
]]></content>
  </entry>
  
  <entry>
    <title>[ANN] Rails 3.2.13.rc2 has been released!</title>
    <author>
      <name>tenderlove</name>
    </author>
    <link href="http://weblog.rubyonrails.org/2013/3/7/Rails-3-2-13-rc2-has-been-released/"/>
    <updated>2013-03-07T00:00:00-08:00</updated>
    <id>http://weblog.rubyonrails.org/2013/3/7/Rails-3-2-13-rc2-has-been-released/</id>
    <content type="html"><![CDATA[<p>Hi everybody.</p>

<p>I'd like to announce that Rails 3.2.13.rc2 has been released.</p>

<p>Rails 3.2.13.rc2 contains fixes for regressions found in rc1.  Please test out
rc2.  If you find regressions between 3.2.13.rc2 and 3.2.12, please email <a href="https://groups.google.com/forum/?fromgroups#!forum/rubyonrails-core">the
rails-core mailing list</a>, or <a href="https://github.com/rails/rails/issues/new">file an issue on GitHub</a>.</p>

<p>If there aren't any major regressions, 3.2.13 final will be released on March
13, 2013.</p>

<ul>
<li><a href="https://github.com/rails/rails/compare/v3.2.11...v3.2.12">Changes in 3.2.12</a></li>
</ul>


<p>Changes:</p>

<ul>
<li><a href="https://github.com/rails/rails/compare/v3.2.12...v3.2.13.rc1">3.2.12 to 3.2.13.rc1</a></li>
<li><a href="https://github.com/rails/rails/compare/v3.2.13.rc1...v3.2.13.rc2">3.2.13.rc1 to 3.2.13.rc2</a></li>
</ul>


<p>&lt;3&lt;3&lt;3</p>
]]></content>
  </entry>
  
  <entry>
    <title>[ANN] Rails 3.2.13.rc1 has been released!</title>
    <author>
      <name>steveklabnik</name>
    </author>
    <link href="http://weblog.rubyonrails.org/2013/2/27/Rails-3-2-13-rc1-has-been-released/"/>
    <updated>2013-02-27T00:00:00-08:00</updated>
    <id>http://weblog.rubyonrails.org/2013/2/27/Rails-3-2-13-rc1-has-been-released/</id>
    <content type="html"><![CDATA[<p>Hey everyone! I am pumped to announce that Rails 3.2.13.rc1 has been released!
If no regressions are found I will release 3.2.13 final in two weeks, on March
13, 2013. If you find one, please <a href="https://github.com/rails/rails/issues/new">Open an Issue on
GitHub</a> so that I can fix it before
the final release.</p>

<p>This is a bugfix release, with 287 commits. There is one big thing that is
technically a fix but is sort of a feature: Ruby 2.0 support. Big thanks to
Prem Sichanugrist for putting that together! Please give your applications a
try on Ruby 2.0 and let me know how that goes.</p>

<h2>CHANGES since 3.2.12</h2>

<p><em>Action Mailer</em></p>

<p>No changes.</p>

<p><em>Action Pack</em></p>

<ul>
<li><p>Determine the controller#action from only the matched path when using the
shorthand syntax. Previously the complete path was used, which led
to problems with nesting (scopes and namespaces).
Fixes #7554.
Backport #9361.</p>

<p>Example:</p>

<pre><code># this will route to questions#new
scope ':locale' do
  get 'questions/new'
end
</code></pre>

<p><em>Yves Senn</em></p></li>
<li><p>Fix <code>assert_template</code> with <code>render :stream =&gt; true</code>.
Fix #1743.
Backport #5288.</p>

<p><em>Sergey Nartimov</em></p></li>
<li><p>Eagerly populate the http method loookup cache so local project inflections do
not interfere with use of underscore method ( and we don't need locks )</p>

<p><em>Aditya Sanghi</em></p></li>
<li><p><code>BestStandardsSupport</code> no longer duplicates <code>X-UA-Compatible</code> values on
each request to prevent header size from blowing up.</p>

<p><em>Edward Anderson</em></p></li>
<li><p>Fixed JSON params parsing regression for non-object JSON content.</p>

<p><em>Dylan Smith</em></p></li>
<li><p>Prevent unnecessary asset compilation when using <code>javascript_include_tag</code> on
files with non-standard extensions.</p>

<p><em>Noah Silas</em></p></li>
<li><p>Fixes issue where duplicate assets can be required with sprockets.</p>

<p><em>Jeremy Jackson</em></p></li>
<li><p>Bump <code>rack</code> dependency to 1.4.3, eliminate <code>Rack::File</code> headers deprecation warning.</p>

<p><em>Sam Ruby + Carlos Antonio da Silva</em></p></li>
<li><p>Do not append second slash to <code>root_url</code> when using <code>trailing_slash: true</code></p>

<p>Fix #8700.
Backport #8701.</p>

<p>Example:</p>

<pre><code># before
root_url # =&gt; http://test.host//

# after
root_url # =&gt; http://test.host/
</code></pre>

<p><em>Yves Senn</em></p></li>
<li><p>Fix a bug in <code>content_tag_for</code> that prevents it for work without a block.</p>

<p><em>Jasl</em></p></li>
<li><p>Clear url helper methods when routes are reloaded by removing the methods
explicitly rather than just clearing the module because it didn't work
properly and could be the source of a memory leak.</p>

<p><em>Andrew White</em></p></li>
<li><p>Fix a bug in <code>ActionDispatch::Request#raw_post</code> that caused <code>env['rack.input']</code>
to be read but not rewound.</p>

<p><em>Matt Venables</em></p></li>
<li><p>More descriptive error messages when calling <code>render :partial</code> with
an invalid <code>:layout</code> argument.</p>

<p>Fixes #8376.</p>

<pre><code>render :partial =&gt; 'partial', :layout =&gt; true
# results in ActionView::MissingTemplate: Missing partial /true
</code></pre>

<p><em>Yves Senn</em></p></li>
<li><p>Accept symbols as <code>#send_data</code> :disposition value. [Backport #8329] <em>Elia Schito</em></p></li>
<li><p>Add i18n scope to <code>distance_of_time_in_words</code>. [Backport #7997] <em>Steve Klabnik</em></p></li>
<li><p>Fix side effect of <code>url_for</code> changing the <code>:controller</code> string option. [Backport #6003]
Before:</p>

<pre><code>controller = '/projects'
url_for :controller =&gt; controller, :action =&gt; 'status'

puts controller #=&gt; 'projects'
</code></pre>

<p>After</p>

<pre><code>puts controller #=&gt; '/projects'
</code></pre>

<p><em>Nikita Beloglazov + Andrew White</em></p></li>
<li><p>Introduce <code>ActionView::Template::Handlers::ERB.escape_whitelist</code>. This is a list
of mime types where template text is not html escaped by default. It prevents <code>Jack &amp; Joe</code>
from rendering as <code>Jack &amp;amp; Joe</code> for the whitelisted mime types. The default whitelist
contains text/plain. Fix #7976 [Backport #8235]</p>

<p><em>Joost Baaij</em></p></li>
<li><p><code>BestStandardsSupport</code> middleware now appends it's <code>X-UA-Compatible</code> value to app's
returned value if any. Fix #8086 [Backport #8093]</p>

<p><em>Nikita Afanasenko</em></p></li>
<li><p>prevent double slashes in engine urls when <code>Rails.application.default_url_options[:trailing_slash] = true</code> is set
Fix #7842</p>

<p><em>Yves Senn</em></p></li>
<li><p>Fix input name when <code>:multiple =&gt; true</code> and <code>:index</code> are set.</p>

<p>Before:</p>

<pre><code>check_box("post", "comment_ids", { :multiple =&gt; true, :index =&gt; "foo" }, 1)
#=&gt; &lt;input name=\"post[foo][comment_ids]\" type=\"hidden\" value=\"0\" /&gt;&lt;input id=\"post_foo_comment_ids_1\" name=\"post[foo][comment_ids]\" type=\"checkbox\" value=\"1\" /&gt;
</code></pre>

<p>After:</p>

<pre><code>check_box("post", "comment_ids", { :multiple =&gt; true, :index =&gt; "foo" }, 1)
#=&gt; &lt;input name=\"post[foo][comment_ids][]\" type=\"hidden\" value=\"0\" /&gt;&lt;input id=\"post_foo_comment_ids_1\" name=\"post[foo][comment_ids][]\" type=\"checkbox\" value=\"1\" /&gt;
</code></pre>

<p>Fix #8108</p>

<p><em>Daniel Fox, Grant Hutchins &amp; Trace Wax</em></p></li>
</ul>


<p><em>Active Model</em></p>

<ul>
<li>Specify type of singular association during serialization <em>Steve Klabnik</em></li>
</ul>


<p><em>Active Record</em></p>

<ul>
<li><p>Reverted 921a296a3390192a71abeec6d9a035cc6d1865c8, 'Quote numeric values
compared to string columns.' This caused several regressions.</p>

<p><em>Steve Klabnik</em></p></li>
<li><p>Fix overriding of attributes by default_scope on <code>ActiveRecord::Base#dup</code>.</p>

<p><em>Hiroshige UMINO</em></p></li>
<li><p>Fix issue with overriding Active Record reader methods with a composed object
and using that attribute as the scope of a <code>uniqueness_of</code> validation.
Backport #7072.</p>

<p><em>Peter Brown</em></p></li>
<li><p>Sqlite now preserves custom primary keys when copying or altering tables.
Fixes #9367.
Backport #2312.</p>

<p><em>Sean Scally + Yves Senn</em></p></li>
<li><p>Preloading <code>has_many :through</code> associations with conditions won't
cache the <code>:through</code> association. This will prevent invalid
subsets to be cached.
Fixes #8423.
Backport #9252.</p>

<p>Example:</p>

<pre><code>class User
  has_many :posts
  has_many :recent_comments, -&gt; { where('created_at &gt; ?', 1.week.ago) }, :through =&gt; :posts
end

a_user = User.includes(:recent_comments).first

# this is preloaded
a_user.recent_comments

# fetching the recent_comments through the posts association won't preload it.
a_user.posts
</code></pre>

<p><em>Yves Senn</em></p></li>
<li><p>Fix handling of dirty time zone aware attributes</p>

<p>Previously, when <code>time_zone_aware_attributes</code> were enabled, after
changing a datetime or timestamp attribute and then changing it back
to the original value, <code>changed_attributes</code> still tracked the
attribute as changed. This caused <code>[attribute]_changed?</code> and
<code>changed?</code> methods to return true incorrectly.</p>

<p>Example:</p>

<pre><code>in_time_zone 'Paris' do
  order = Order.new
  original_time = Time.local(2012, 10, 10)
  order.shipped_at = original_time
  order.save
  order.changed? # =&gt; false

  # changing value
  order.shipped_at = Time.local(2013, 1, 1)
  order.changed? # =&gt; true

  # reverting to original value
  order.shipped_at = original_time
  order.changed? # =&gt; false, used to return true
end
</code></pre>

<p>Backport of #9073
Fixes #8898</p>

<p><em>Lilibeth De La Cruz</em></p></li>
<li><p>Fix counter cache columns not updated when replacing <code>has_many :through</code>
associations.
Backport #8400.
Fix #7630.</p>

<p><em>Matthew Robertson</em></p></li>
<li><p>Don't update <code>column_defaults</code> when calling destructive methods on column with default value.
Backport c517602.
Fix #6115.</p>

<p><em>Piotr Sarnacki + Aleksey Magusev + Alan Daud</em></p></li>
<li><p>When <code>#count</code> is used in conjunction with <code>#uniq</code> we perform <code>count(:distinct =&gt; true)</code>.
Fix #6865.</p>

<p>Example:</p>

<p>  relation.uniq.count # => SELECT COUNT(DISTINCT *)</p>

<p><em>Yves Senn + Kaspar Schiess</em></p></li>
<li><p>Fix <code>ActiveRecord::Relation#pluck</code> when columns or tables are reserved words.
Backport #7536.
Fix #8968.</p>

<p><em>Ian Lesperance + Yves Senn + Kaspar Schiess</em></p></li>
<li><p>Don't run explain on slow queries for database adapters that don't support it.
Backport #6197.</p>

<p><em>Blake Smith</em></p></li>
<li><p>Revert round usec when comparing timestamp attributes in the dirty tracking.
Fixes #8460.</p>

<p><em>Andrew White</em></p></li>
<li><p>Revert creation of through association models when using <code>collection=[]</code>
on a <code>has_many :through</code> association from an unsaved model.
Fix #7661, #8269.</p>

<p><em>Ernie Miller</em></p></li>
<li><p>Fix undefined method <code>to_i</code> when calling <code>new</code> on a scope that uses an
Array; Fix FloatDomainError when setting integer column to NaN.
Fixes #8718, #8734, #8757.</p>

<p><em>Jason Stirk + Tristan Harward</em></p></li>
<li><p>Serialized attributes can be serialized in integer columns.
Fix #8575.</p>

<p><em>Rafael Mendonça França</em></p></li>
<li><p>Keep index names when using <code>alter_table</code> with sqlite3.
Fix #3489.
Backport #8522.</p>

<p><em>Yves Senn</em></p></li>
<li><p>Recognize migrations placed in directories containing numbers and 'rb'.
Fix #8492.
Backport of #8500.</p>

<p><em>Yves Senn</em></p></li>
<li><p>Add <code>ActiveRecord::Base.cache_timestamp_format</code> class attribute to control
the format of the timestamp value in the cache key.
This allows users to improve the precision of the cache key.
Fixes #8195.</p>

<p><em>Rafael Mendonça França</em></p></li>
<li><p>Add <code>:nsec</code> date format. This can be used to improve the precision of cache key.
Please note that this format only works with Ruby 1.9, Ruby 1.8 will ignore it completely.</p>

<p><em>Jamie Gaskins</em></p></li>
<li><p>Unscope <code>update_column(s)</code> query to ignore default scope.</p>

<p>When applying <code>default_scope</code> to a class with a where clause, using
<code>update_column(s)</code> could generate a query that would not properly update
the record due to the where clause from the <code>default_scope</code> being applied
to the update query.</p>

<pre><code>class User &lt; ActiveRecord::Base
  default_scope where(active: true)
end

user = User.first
user.active = false
user.save!

user.update_column(:active, true) # =&gt; false
</code></pre>

<p>In this situation we want to skip the default_scope clause and just
update the record based on the primary key. With this change:</p>

<pre><code>user.update_column(:active, true) # =&gt; true
</code></pre>

<p>Backport of #8436 fix.</p>

<p><em>Carlos Antonio da Silva</em></p></li>
<li><p>Fix performance problem with primary_key method in PostgreSQL adapter when having many schemas.
Uses pg_constraint table instead of pg_depend table which has many records in general.
Fix #8414</p>

<p><em>kennyj</em></p></li>
<li><p>Do not instantiate intermediate Active Record objects when eager loading.
These records caused <code>after_find</code> to run more than expected.
Fix #3313
Backport of #8403</p>

<p><em>Yves Senn</em></p></li>
<li><p>Fix <code>pluck</code> to work with joins. Backport of #4942.</p>

<p><em>Carlos Antonio da Silva</em></p></li>
<li><p>Fix a problem with <code>translate_exception</code> method in a non English environment.
Backport of #6397.</p>

<p><em>kennyj</em></p></li>
<li><p>Fix dirty attribute checks for TimeZoneConversion with nil and blank
datetime attributes. Setting a nil datetime to a blank string should not
result in a change being flagged.
Fixes #8310.
Backport of #8311.</p>

<p><em>Alisdair McDiarmid</em></p></li>
<li><p>Prevent mass assignment to the type column of polymorphic associations when using <code>build</code>.
Fixes #8265.
Backport of #8291.</p>

<p><em>Yves Senn</em></p></li>
<li><p>When running migrations on Postgresql, the <code>:limit</code> option for <code>binary</code> and <code>text</code> columns is
silently dropped.
Previously, these migrations caused sql exceptions, because Postgresql doesn't support limits
on these types.</p>

<p><em>Victor Costan</em></p></li>
<li><p><code>#pluck</code> can be used on a relation with <code>select</code> clause.
Fixes #7551.
Backport of #8176.</p>

<p>Example:</p>

<pre><code>Topic.select([:approved, :id]).order(:id).pluck(:id)
</code></pre>

<p><em>Yves Senn</em></p></li>
<li><p>Use <code>nil?</code> instead of <code>blank?</code> to check whether dynamic finder with a bang
should raise RecordNotFound.
Fixes #7238.</p>

<p><em>Nikita Afanasenko</em></p></li>
<li><p>Fix deleting from a HABTM join table upon destroying an object of a model
with optimistic locking enabled.
Fixes #5332.</p>

<p><em>Nick Rogers</em></p></li>
<li><p>Use query cache/uncache when using ENV["DATABASE_URL"].
Fixes #6951.
Backport of #8074.</p>

<p><em>kennyj</em></p></li>
<li><p>Do not create useless database transaction when building <code>has_one</code> association.</p>

<p>Example:</p>

<pre><code>User.has_one :profile
User.new.build_profile
</code></pre>

<p>Backport of #8154.</p>

<p><em>Bogdan Gusiev</em></p></li>
<li><p><code>AR::Base#attributes_before_type_cast</code> now returns unserialized values for serialized attributes.</p>

<p><em>Nikita Afanasenko</em></p></li>
<li><p>Fix issue that raises <code>NameError</code> when overriding the <code>accepts_nested_attributes</code> in child classes.</p>

<p>Before:</p>

<pre><code>class Shared::Person &lt; ActiveRecord::Base
  has_one :address

  accepts_nested_attributes :address, :reject_if =&gt; :all_blank
end

class Person &lt; Shared::Person
  accepts_nested_attributes :address
end

Person
#=&gt; NameError: method `address_attributes=' not defined in Person
</code></pre>

<p>After:</p>

<pre><code>Person
#=&gt; Person(id: integer, ...)
</code></pre>

<p>Fixes #8131.</p>

<p><em>Gabriel Sobrinho, Ricardo Henrique</em></p></li>
</ul>


<p><em>Active Resource</em></p>

<p>No changes.</p>

<p><em>Active Support</em></p>

<ul>
<li><p>Fix DateTime comparison with DateTime::Infinity object.</p>

<p><em>Dan Kubb</em></p></li>
<li><p>Remove surrogate unicode character encoding from ActiveSupport::JSON.encode
The encoding scheme was broken for unicode characters outside the basic
multilingual plane; since json is assumed to be UTF-8, and we already force the
encoding to UTF-8 simply pass through the un-encoded characters.</p>

<p><em>Brett Carter</em></p></li>
<li><p>Fix mocha v0.13.0 compatibility. <em>James Mead</em></p></li>
<li><p><code>#as_json</code> isolates options when encoding a hash. [Backport #8185]
Fix #8182</p>

<p><em>Yves Senn</em></p></li>
<li><p>Handle the possible Permission Denied errors atomic.rb might trigger due to
its chown and chmod calls. [Backport #8027]</p>

<p><em>Daniele Sluijters</em></p></li>
</ul>


<p><em>Railties</em></p>

<p>No changes.</p>

<p><em>Full listing</em></p>

<p>To see the full list of changes, <a href="https://github.com/rails/rails/compare/v3.2.12...v3.2.13.rc1">check out all the commits on
GitHub</a>.</p>

<h2>SHA-1</h2>

<p>If you'd like to verify that your gem is the same as the one I've uploaded,
please use these SHA-1 hashes:</p>

<ul>
<li><code>6a33c2d10abb5512499addb675df658e179f2e79</code>  actionmailer-3.2.13.rc1.gem</li>
<li><code>11d8303470698c5b0ac68f187a15093c07383c89</code>  actionpack-3.2.13.rc1.gem</li>
<li><code>a72dafd8b1e3372cc4dda9015b93bf5509b25baa</code>  activemodel-3.2.13.rc1.gem</li>
<li><code>3c6463ab11658b5ab0fe6a4ad06eb52968ef4492</code>  activerecord-3.2.13.rc1.gem</li>
<li><code>06cec200b95dc1f64614cd03432e9ab06742a865</code>  activeresource-3.2.13.rc1.gem</li>
<li><code>5ff59cacae5295baf30a6fb8fb656037f22af3c2</code>  activesupport-3.2.13.rc1.gem</li>
<li><code>facf4549445922d9dc2a836283ae928fa52df4f8</code>  rails-3.2.13.rc1.gem</li>
<li><code>55e44f621efbf531d9ccade6d27259f7dabae167</code>  railties-3.2.13.rc1.gem</li>
</ul>


<p>&lt;3&lt;3&lt;3</p>
]]></content>
  </entry>
  
  <entry>
    <title>Rails 4.0: Beta 1 released!</title>
    <author>
      <name>dhh</name>
    </author>
    <link href="http://weblog.rubyonrails.org/2013/2/25/Rails-4-0-beta1/"/>
    <updated>2013-02-25T16:00:00-08:00</updated>
    <id>http://weblog.rubyonrails.org/2013/2/25/Rails-4-0-beta1/</id>
    <content type="html"><![CDATA[<p>Hot on the heels of the first production version of Ruby 2.0 comes the first beta version of Rails 4.0. The two form a great pair and are already running in production on a number of applications, including <a href="http://basecamp.com/breeze">Basecamp Breeze</a>. In fact, Ruby 2.0 is the preferred Ruby to use with Rails 4.0.</p>

<p>The purpose of this beta is to get as many people as possible to try to upgrade from Rails 3.2 and earlier and to get an adventurous few to start new applications directly on Rails 4.0. That's the only way we're going to suss out all the issues and ensure that we can launch a solid final release. So please help us with that if you can!</p>

<p>Rails 4.0 is packed with new goodies and farewells to old goodies past their expiration date.</p>

<p>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 <a href="http://37signals.com/svn/posts/3112-how-basecamp-next-got-to-be-so-damn-fast-without-using-much-client-side-ui">pioneered for Rails in the new version of Basecamp</a> and focuses on three aspects:</p>

<ol>
<li>Make it super easy to do Russian Doll-caching through <a href="http://37signals.com/svn/posts/3113-how-key-based-cache-expiration-works">key-based expiration</a> with automatic dependency management of nested templates (explored first in the <a href="https://github.com/rails/cache_digests">cache_digests</a> plugin).</li>
<li>Speed-up the client-side with <a href="https://github.com/rails/turbolinks/">Turbolinks</a>, which essentially turns your app into a single-page javascript application in terms of speed, but with none of the developmental drawbacks (except, maybe, compatibility issues with some existing JavaScript packages).</li>
<li><a href="https://github.com/rails/rails/commit/ed5c938fa36995f06d4917d9543ba78ed506bb8d">Declarative etags</a> makes it even easier to ensure you're taking advantage of HTTP freshness.</li>
</ol>


<p>Rails is of course still a great JSON server for people who want to build client-side JS views, but with the progress we've made for Rails 4.0, you certainly won't need to go down that route just to have a super fast application.</p>

<p>We've also added <a href="http://tenderlovemaking.com/2012/07/30/is-it-live.html">live streaming for persistent connections</a> and Rails 4.0 is now safe for threaded servers out of the box (no more need for config.threadsafe!).</p>

<p>Active Record has received a ton of love as well to make everything related to scoping and the query structure more consistent.</p>

<p>Given all the fun we've had with security issues, we have some great updates there as well:</p>

<ul>
<li>Session store is now encrypted by default (formerly just signed).</li>
<li><a href="https://github.com/rails/strong_parameters">Strong Parameters</a> take over from attr_protected (now a <a href="https://github.com/rails/protected_attributes">plugin</a>) to guard against foreign parameters.</li>
<li>Security headers like X-Frame-Options, X-XSS-Protection, X-Content-Type-Options are on by default with solid values.</li>
<li>XML Parameter parsing has been sent to a <a href="https://github.com/rails/actionpack-xml_parser">plugin</a>.</li>
</ul>


<p>On top of these new features and fixes, we have hundreds more of all sorts. Everything has been combed over, streamlined, simplified, and we've extracted out lots of old APIs and things that just don't fit "most people most of the time".</p>

<p><a href="https://github.com/rails/activeresource">Active Resource</a>, <a href="https://github.com/rails/rails-observers">Active Record Observers</a>, and Action Pack <a href="https://github.com/rails/actionpack-page_caching">page</a> and <a href="https://github.com/rails/actionpack-action_caching">action caching</a> are all examples of things that are no longer in core, but lives on in plugins.</p>

<p>We encourage you to peruse the CHANGELOGs for all the Rails frameworks and delight over the hundreds of improvements we've made to Rails 4.0: <a href="https://github.com/rails/rails/blob/v4.0.0.beta1/actionpack/CHANGELOG.md">Action Pack</a>, <a href="https://github.com/rails/rails/blob/v4.0.0.beta1/activemodel/CHANGELOG.md">Active Model</a>, <a href="https://github.com/rails/rails/blob/v4.0.0.beta1/activerecord/CHANGELOG.md">Active Record</a>, <a href="https://github.com/rails/rails/blob/v4.0.0.beta1/activesupport/CHANGELOG.md">Active Support</a>, <a href="https://github.com/rails/rails/blob/v4.0.0.beta1/railties/CHANGELOG.md">Rails</a>.</p>

<p>Now let's all work together to ensure the release is final and enjoy the bad-ass combination of Ruby on Rails 24! (Or 42?). Please report all the issues you find on the <a href="https://github.com/rails/rails/issues?state=open">Rails issue tracker</a>. We're still working on the <a href="http://edgeguides.rubyonrails.org/upgrading_ruby_on_rails.html#upgrading-from-rails-3-2-to-rails-4-0">upgrade guide from 3.2 to 4.0</a>, but that's a good place to start for help on how to do it. As always, install betas with <code>gem install rails --version 4.0.0.beta1 --no-ri --no-rdoc</code> (--pre and ri generation is busted on RubyGems 2.0 at the moment) or depend on the <a href="https://github.com/rails/rails/tree/v4.0.0.beta1">v4.0.0.beta1 tag</a>.</p>
]]></content>
  </entry>
  
  <entry>
    <title>Maintenance policy for Ruby on Rails</title>
    <author>
      <name>steveklabnik</name>
    </author>
    <link href="http://weblog.rubyonrails.org/2013/2/24/maintenance-policy-for-ruby-on-rails/"/>
    <updated>2013-02-24T00:00:00-08:00</updated>
    <id>http://weblog.rubyonrails.org/2013/2/24/maintenance-policy-for-ruby-on-rails/</id>
    <content type="html"><![CDATA[<p>Since the most recent patch releases there has been some confusion about what
versions of Ruby on Rails are currently supported, and when people can expect
new versions.  Our maintenance policy is as follows.</p>

<p>Support of the Rails framework is divided into four groups: New features, bug
fixes, security issues, and severe security issues.  They are handled as
follows, all versions in x.y.z format:</p>

<h2>New Features</h2>

<p>New Features are only added to the master branch and will not be made available
in point releases.</p>

<h2>Bug fixes</h2>

<p>Only the latest release series will receive bug fixes. When enough bugs are
fixed and its deemed worthy to release a new gem, this is the branch it happens
from.</p>

<p>Currently included series: 3.2.z</p>

<p>After the Rails 4 release: 4.0.z</p>

<h2>Security issues:</h2>

<p>The current release series and the next most recent one will receive patches
and new versions in case of a security issue.</p>

<p>These releases are created by taking the last released version, applying the
security patches, and releasing. Those patches are then applied to the end of
the x-y-stable branch. For example, a theoretical 1.2.3 security release would
be built from 1.2.2, and then added to the end of 1-2-stable. This means that
security releases are easy to upgrade to if you're running the latest version
of Rails.</p>

<p>Currently included series: 3.2.z, 3.1.z</p>

<p>After the Rails 4 release: 4.0.z, 3.2.z</p>

<h2>Severe security issues:</h2>

<p>For severe security issues we will provide new versions as above, and also the
last major release series will receive patches and new versions. The
classification of the security issue is judged by the core team.</p>

<p>Currently included series: 3.2.z, 3.1.z, 2.3.z</p>

<p>After the Rails 4 release: 4.0.z, 3.2.z</p>

<h2>Unsupported Release Series</h2>

<p>When a release series is no longer supported, it's your own responsibility to
deal with bugs and security issues.  We may provide back-ports of the fixes and
publish them to git, however there will be no new versions released.  If you
are not comfortable maintaining your own versions, you should upgrade to a
supported version.</p>

<p>You should also be aware that Ruby 1.8 will reach End of Life in June 2013, no
further Ruby security releases will be provided after that point.  If your
application is only compatible Ruby 1.8 you should upgrade accordingly.</p>
]]></content>
  </entry>
  
  <entry>
    <title>[SEC][ANN] Rails 3.2.12, 3.1.11, and 2.3.17 have been released!</title>
    <author>
      <name>tenderlove</name>
    </author>
    <link href="http://weblog.rubyonrails.org/2013/2/11/SEC-ANN-Rails-3-2-12-3-1-11-and-2-3-17-have-been-released/"/>
    <updated>2013-02-11T00:00:00-08:00</updated>
    <id>http://weblog.rubyonrails.org/2013/2/11/SEC-ANN-Rails-3-2-12-3-1-11-and-2-3-17-have-been-released/</id>
    <content type="html"><![CDATA[<p>Hi everybody.</p>

<p>I'd like to announce that Rails 3.2.12, 3.1.11, and 2.3.17 have been released.</p>

<p>3.2.12 and 3.1.11 contain one security fix, and 2.3.17 contains two security fixes.  It is recommended that you update immediately.</p>

<p>You can read about the security fixes by following these links:</p>

<ul>
<li><a href="https://groups.google.com/forum/?fromgroups=#!topic/rubyonrails-security/AFBKNY7VSH8">CVE-2013-0276</a></li>
<li><a href="https://groups.google.com/forum/?fromgroups=#!topic/rubyonrails-security/KtmwSbEpzrU">CVE-2013-0277</a></li>
</ul>


<p>Please note that today a new JSON gem was released, and it also contains an important security fix.  You should update the JSON gem as soon as possible.  You can read about the security issue in the JSON gem here:</p>

<ul>
<li><a href="https://groups.google.com/forum/?fromgroups=#!topic/rubyonrails-security/4_YvCpLzL58">CVE-2013-0269</a></li>
</ul>


<p>In order to ease upgrading, the only major changes in each gem is the security fix.  To see the detailed changes for each version, follow the links below:</p>

<ul>
<li><a href="https://github.com/rails/rails/compare/v3.2.11...v3.2.12">Changes in 3.2.12</a></li>
<li><a href="https://github.com/rails/rails/compare/v3.1.10...v3.1.11">Changes in 3.1.11</a></li>
<li><a href="https://github.com/rails/rails/compare/v2.3.16...v2.3.17">Changes in 2.3.17</a></li>
</ul>


<p>Thanks to the people who responsibly reported these security issues.</p>

<p>Please note that per our <a href="https://groups.google.com/forum/?fromgroups=#!topic/rubyonrails-security/G4TTUDDYbNA">maintenance policy</a> there will be no 3.0.x version released.</p>

<p>Here are the SHA-1 checksums for each gem:</p>

<h2>Rails 3.2.12</h2>

<p><code>
[aaron@higgins dist]$ shasum *3.2.*
5627c6d044cc52876128459d960f8805006b5f97  actionmailer-3.2.12.gem
336f76c045b6bcbd204831897131182cff82ddf8  actionpack-3.2.12.gem
89bec5d68861ad5d79ca776ef5d6df7c1cfc2b11  activemodel-3.2.12.gem
7d4327c54900f45c60947a63350e865843e193ef  activerecord-3.2.12.gem
4b8ed4190f98a85b800ee7893bae5afd1bee0874  activeresource-3.2.12.gem
c9e44eed288140f556e6543b93fc45f8dd57a415  activesupport-3.2.12.gem
24b3b4633d7f131e61e50decc3aa11590941c6e2  rails-3.2.12.gem
a84262f1968e83141d290c034b20a28d38886d10  railties-3.2.12.gem
</code></p>

<h2>Rails 3.1.11</h2>

<p><code>
[aaron@higgins dist]$ shasum *3.1.*
d80816e69614c1f0d96cb7d0f4a38bfdc8d84ff5  actionmailer-3.1.11.gem
f65cea0682b6051869d4125f7b441a7c6f59fcbe  actionpack-3.1.11.gem
549ec2b67d4332b38cef1620b23e00e50e0774e6  activemodel-3.1.11.gem
3d342764b7ba3bae05190f15bcb35d401cd8121e  activerecord-3.1.11.gem
19bd70bad6c4e4a555127a7738e71ac4829e6f61  activeresource-3.1.11.gem
7267b2f87bea5bd285f5d1bfe49bb2ba19df7c94  activesupport-3.1.11.gem
ca57e1243451385689343dbe2bb42e23058284df  rails-3.1.11.gem
48cc801bdb7c31c4b6939235a60ef3e5008f5dbb  railties-3.1.11.gem
</code></p>

<h2>Rails 2.3.17</h2>

<p><code>
[aaron@higgins dist]$ shasum *2.3.*
5df1fe13db46ac10dec8bb607ef515881dcf09c5  actionmailer-2.3.17.gem
d1165517a185ae73ca8a4ac89549e695a23fedfa  actionpack-2.3.17.gem
b24ff71e46b798d7c38504531cb7622955d9a20c  activerecord-2.3.17.gem
9cc2a7bd60a959dcba099425954a1b9c53235ce5  activeresource-2.3.17.gem
4ccc935fdc4d7ede78a1c376453ecb502e48b7ed  activesupport-2.3.17.gem
9613a97cb726f00de59ad6d0f901f7434f9c4733  rails-2.3.17.gem
</code></p>

<p>&lt;3&lt;3&lt;3</p>
]]></content>
  </entry>
  
  <entry>
    <title>[SEC][ANN] Rails 3.0.20, and 2.3.16 have been released!</title>
    <author>
      <name>tenderlove</name>
    </author>
    <link href="http://weblog.rubyonrails.org/2013/1/28/Rails-3-0-20-and-2-3-16-have-been-released/"/>
    <updated>2013-01-28T00:00:00-08:00</updated>
    <id>http://weblog.rubyonrails.org/2013/1/28/Rails-3-0-20-and-2-3-16-have-been-released/</id>
    <content type="html"><![CDATA[<p>Hi everybody.</p>

<p>I'd like to announce that 3.0.20, and 2.3.16 have been released.  These releases contain one <strong>extremely critical security fix</strong> so please update <strong>IMMEDIATELY</strong>.</p>

<p>You can read about the security fix by following this link:</p>

<ul>
<li><a href="https://groups.google.com/forum/?fromgroups=#!topic/rubyonrails-security/1h2DR63ViGo">CVE-2013-0333</a></li>
</ul>


<p>In order to ease upgrading, the only major changes in each gem is the security fix.  To see the detailed changes for each version, follow the links below:</p>

<ul>
<li><a href="https://github.com/rails/rails/compare/v3.0.19...v3.0.20">Changes in 3.0.20</a></li>
<li><a href="https://github.com/rails/rails/compare/v2.3.15...v2.3.16">Changes in 2.3.16</a></li>
</ul>


<p>Thanks to the people who responsibly reported these security issues.</p>

<p>Please note that per our <a href="https://groups.google.com/forum/?fromgroups=#!topic/rubyonrails-security/G4TTUDDYbNA">maintenance policy</a> this will be the last release for the 3.0.x series.</p>

<p>Here are the SHA-1 checksums for each gem:</p>

<h3>3.0.20</h3>

<p><code>
[aaron@higgins dist]$ shasum *3.0.20*
c5b1a446d921dbd512a2d418c50f144b4540a657  actionmailer-3.0.20.gem
79ec243f6ec301b0a73ad45f89d4ea2335f90346  actionpack-3.0.20.gem
80c7d881ed64ed7a66f4d82b12c2b98b43f6fbde  activemodel-3.0.20.gem
d8fc6e02bf46f9b5f86c3a954932d67da211302b  activerecord-3.0.20.gem
e465e7d582c6d72c487d132e5fac3c3af4626353  activeresource-3.0.20.gem
5bc7b2f1ad70a2781c4a41a2f4eaa75b999750e4  activesupport-3.0.20.gem
ba9fb9dba41ce047feef11b4179cd9c3f81b2857  rails-3.0.20.gem
42b0025e4cb483d491a809b9d9deb6fd182c2a57  railties-3.0.20.gem
</code></p>

<h3>2.3.16</h3>

<p><code>
[aaron@higgins dist]$ shasum *2.3.16*
ab1a47a08d42352d9e8c276d28e6ed6990c23556  actionmailer-2.3.16.gem
f81ac75eb9edbb363a6d7bbe175a208e97ea3d4f  actionpack-2.3.16.gem
4ce36062f1f0b326b16e42b9fde5f1ab0610bffc  activerecord-2.3.16.gem
3698787f9ab8432f0c10268e22fbfcf682fa79cc  activeresource-2.3.16.gem
90490f62db73c4be9ed69d96592afa0b98e79738  activesupport-2.3.16.gem
239253159f9793e2372c83dcf9d0bd7bff343f7d  rails-2.3.16.gem
</code></p>

<p>&lt;3&lt;3&lt;3</p>
]]></content>
  </entry>
  
  <entry>
    <title>[SEC][ANN] Rails 3.2.11, 3.1.10, 3.0.19, and 2.3.15 have been released!</title>
    <author>
      <name>tenderlove</name>
    </author>
    <link href="http://weblog.rubyonrails.org/2013/1/8/Rails-3-2-11-3-1-10-3-0-19-and-2-3-15-have-been-released/"/>
    <updated>2013-01-08T00:00:00-08:00</updated>
    <id>http://weblog.rubyonrails.org/2013/1/8/Rails-3-2-11-3-1-10-3-0-19-and-2-3-15-have-been-released/</id>
    <content type="html"><![CDATA[<p>Hi everybody.</p>

<p>I'd like to announce that 3.2.11, 3.1.10, 3.0.19, and 2.3.15 have been released.  These releases contain two <strong>extremely critical security fixes</strong> so please update <strong>IMMEDIATELY</strong>.</p>

<p>You can read about the security fixes by following these links:</p>

<ul>
<li><a href="https://groups.google.com/group/rubyonrails-security/browse_thread/thread/b75585bae4326af2">CVE-2013-0155</a></li>
<li><a href="https://groups.google.com/group/rubyonrails-security/browse_thread/thread/eb56e482f9d21934">CVE-2013-0156</a></li>
</ul>


<p>In order to ease upgrading, the only major changes in each gem are the security fixes.  To see the detailed changes for each version, follow the links below:</p>

<ul>
<li><a href="https://github.com/rails/rails/compare/v3.2.10...v3.2.11">Changes in 3.2.11</a></li>
<li><a href="https://github.com/rails/rails/compare/v3.1.9...v3.1.10">Changes in 3.1.10</a></li>
<li><a href="https://github.com/rails/rails/compare/v3.0.18...v3.0.19">Changes in 3.0.19</a></li>
<li><a href="https://github.com/rails/rails/compare/v2.3.14...v2.3.15">Changes in 2.3.15</a></li>
</ul>


<p>Thanks to the people who responsibly reported these security issues.</p>

<p>Here are the SHA-1 checksums for each gem:</p>

<h3>3.2.11</h3>

<p><code>
[aaron@higgins dist]$ shasum *3.2.11*
933cd2821b30cdff4a2e0b5cc63f4d2c6b29affe  actionmailer-3.2.11.gem
54731c51b55bf0215392971b982139775c0bfa2b  actionpack-3.2.11.gem
5ccde66568d8051405c01063f1afaed13bd01082  activemodel-3.2.11.gem
f360c17968486479b0a4207e7eccbe379186a9d2  activerecord-3.2.11.gem
c61ff513be8a8aef898d2e5c4c9508d60727c556  activeresource-3.2.11.gem
41a4e8c382594283026d977554c1e18233198ca8  activesupport-3.2.11.gem
8fa6d19a0daea910e39a0911b2240c2a7b630fb1  rails-3.2.11.gem
ffaec7c3e5211283108cf5afab8e79be76090a0d  railties-3.2.11.gem
</code></p>

<h3>3.1.10</h3>

<p><code>
[aaron@higgins dist]$ shasum *3.1.10*
e3dce983ebd0ee8970c5ddab46b05ac432c8b029  actionmailer-3.1.10.gem
84e536e732255e5dfd3d8053c10ed98dcb45ac80  actionpack-3.1.10.gem
db1a3ac836d988dc1fc7c64d29ded7a277047419  activemodel-3.1.10.gem
ea3ad8514265516033009d97efc1fe7b3d2b09ed  activerecord-3.1.10.gem
0843646278b42d9ca796e157295851fd9938fe96  activeresource-3.1.10.gem
b55ef7f66de0bb79fcfa480e8df3696bffbff7f8  activesupport-3.1.10.gem
4ed7d159191faa1a469cd9efdf9e6a4cdc907195  rails-3.1.10.gem
f288986df0fabd2035569199ea3d5f1f46a56db7  railties-3.1.10.gem
</code></p>

<h3>3.0.19</h3>

<p><code>
[aaron@higgins dist]$ shasum *3.0.19*
f8376f907b2230ac75882e1a3cfa8d5cdd6df800  actionmailer-3.0.19.gem
68b319d86530a5d4291e13d6ab5f357a1e52c05b  actionpack-3.0.19.gem
f0fb577ea7446ff229752bc799ca86dd53aa9cda  activemodel-3.0.19.gem
c12324d78b22697d426148010901f79b366c0502  activerecord-3.0.19.gem
8dbc7c8c80f5baeec823966aa225b23f4c2a799c  activeresource-3.0.19.gem
b525b778f82f844a56ff993211825b9811bf82bd  activesupport-3.0.19.gem
c2beb0711d28a07cb2747c83962c7d453951e2d6  rails-3.0.19.gem
de286ada16b3fc76129767dc612926e0b4f71dda  railties-3.0.19.gem
</code></p>

<h3>2.3.15</h3>

<p><code>
[aaron@higgins dist]$ shasum *2.3.15*
5ce45c70851dd534a72814620a6e57b42d360b88  actionmailer-2.3.15.gem
fa174c40f17fa5db952ba3a7c95a4ab0b5467594  actionpack-2.3.15.gem
e7391c92c82f974be7e65765819824e87bdb3cfd  activerecord-2.3.15.gem
4644b7a27993f7860d9e176f51dfa52d8f029ec9  activeresource-2.3.15.gem
64843e3676c20a49060605546dfcdddaef2ea1a8  activesupport-2.3.15.gem
c8c0c49c63ca0f9acc3e0967b38d92b1c0b115af  rails-2.3.15.gem
</code></p>

<p>&lt;3&lt;3&lt;3</p>
]]></content>
  </entry>
  
  <entry>
    <title>[ANN] Rails 3.2.10, 3.1.9, and 3.0.18 have been released!</title>
    <author>
      <name>tenderlove</name>
    </author>
    <link href="http://weblog.rubyonrails.org/2013/1/2/Rails-3-2-10--3-1-9--and-3-0-18-have-been-released/"/>
    <updated>2013-01-02T00:00:00-08:00</updated>
    <id>http://weblog.rubyonrails.org/2013/1/2/Rails-3-2-10--3-1-9--and-3-0-18-have-been-released/</id>
    <content type="html"><![CDATA[<p>Rails versions 3.2.10, 3.1.9, and 3.0.18 have been released.  These releases contain an important security fix.  It is recommended that <strong>all users upgrade immediately</strong>.</p>

<p>The security identifier is CVE-2012-5664, and you can read about the issue <a href="https://groups.google.com/group/rubyonrails-security/browse_thread/thread/c2353369fea8c53">here</a>.</p>

<p>For other change in each particular release, please see the CHANGELOG corresponding to that version.  For all commits in each release, please follow the links below:</p>

<ul>
<li><a href="https://github.com/rails/rails/compare/v3.2.9...v3.2.10">Changes in 3.2.10</a></li>
<li><a href="https://github.com/rails/rails/compare/v3.1.8...v3.1.9">Changes in 3.1.9</a></li>
<li><a href="https://github.com/rails/rails/compare/v3.0.17...v3.0.18">Changes in 3.0.18</a></li>
</ul>


<p>We're sorry to drop a release like this so close to the holidays but regrettably the exploit has already been publicly disclosed and we don't feel we can delay the release.</p>

<p>To that end, we've minimized the number of changes in each release so that upgrading should be as smooth as possible.</p>

<p>Happy Holidays!</p>

<p>&lt;3&lt;3&lt;3</p>
]]></content>
  </entry>
  
  <entry>
    <title>What Is New in Rails Contributors</title>
    <author>
      <name>fxn</name>
    </author>
    <link href="http://weblog.rubyonrails.org/2012/12/28/what-is-new-in-rails-contributors/"/>
    <updated>2012-12-28T00:00:00-08:00</updated>
    <id>http://weblog.rubyonrails.org/2012/12/28/what-is-new-in-rails-contributors/</id>
    <content type="html"><![CDATA[<h2>What is Rails Contributors?</h2>

<p><a href="http://contributors.rubyonrails.org">Rails Contributors</a> is a website that keeps track of all contributions made to the Ruby on Rails code base.</p>

<p>The application tries hard to give credit as accurately as possible, which is something you cannot do with <code>git log</code>. For example, according to Git the author of <a href="https://github.com/rails/rails/commit/ef91cddb48d1fa8d1a34e8e5ac68fe9eb56c160f">this commit</a> is "@schneems and @mattt", but you do not want to credit "@schneems and @mattt" right? Rails Contributors automatically splits the string, applies <a href="https://github.com/fxn/rails-contributors/blob/master/app/models/names_manager.rb">mappings</a>, and gives credit both to Richard Schneeman, and Mattt Thompson.</p>

<p>Known typos, emails, and handles are associated to a canonical name to have everything aggregated per contributor rather than scattered in several unrelated listings. Heuristics also capture contributors from commit messages, and even from CHANGELOGs in the diff of commits imported from Subversion.</p>

<p>The purpose of all this work is to give credit, provide visibility to your contributions to Rails, and last but not least, to say thank you.</p>

<h2>What Is New?</h2>

<p>A new version of the website has just been published, changes are:</p>

<ul>
<li><p>More mappings: the application knows about <a href="https://github.com/fxn/rails-contributors/blob/master/app/models/names_manager.rb">more mappings and false positives</a>.</p></li>
<li><p>New page for releases: There is a <a href="http://contributors.rubyonrails.org/releases">new shiny page for releases</a> where you can see who contributed what in any of them. The breakdown is approximate for old releases, since all we have from Subversion is the Git history. Commits are classified with <code>git rev-list</code>.</p></li>
<li><p>Better Unicode handling: Some names with non-ASCII characters came up from Git using different UTF8 byte representations. The application applies now NFC normalization thoroughly to address that.</p></li>
<li><p>Robust commit import: about one thousand commits were missing in the previous version because they were unreachable from the branch tips due to rarities in the git history. The commit importer is now more aggressive looking for commits.</p></li>
<li><p>Credit for Rails core in Subversion commits: Rails used Subversion in about its first four years. Subversion does not distinguish author and committer, you only have the committer. If the application determines that the author is not the committer using its heuristics, the committer now gets also credited. This is fair with what happens nowadays, where the committer gets credited by his work on a pull request via the merge commit.</p></li>
<li><p>Internal changes: A lot of work has no external visibility indeed, you know. We migrated from <a href="https://github.com/mojombo/grit">grit</a> to <a href="https://github.com/libgit2/rugged">rugged</a>, and there were significant refactors and speedups.</p></li>
</ul>


<p>Enjoy!</p>
]]></content>
  </entry>
  
  <entry>
    <title>The People Behind Rails 4</title>
    <author>
      <name>fxn</name>
    </author>
    <link href="http://weblog.rubyonrails.org/2012/11/21/the-people-behind-rails-4/"/>
    <updated>2012-11-21T00:00:00-08:00</updated>
    <id>http://weblog.rubyonrails.org/2012/11/21/the-people-behind-rails-4/</id>
    <content type="html"><![CDATA[<p>Rails 4 is coming along nicely <a href="http://blog.wyeworks.com/2012/11/13/rails-4-compilation-links/">with a ton of new stuff</a>, but this major release would have not been possible without the help of some people whose contributions have been outstanding. We want to dedicate this post to them, to show our appreciation and recognition for their extraordinary work:</p>

<p><a href="http://contributors.rubyonrails.org/contributors/arun-agrawal/commits">Arun Agrawal</a> has been helping with some housekeeping tasks. He puts a lot of effort to remove warnings, fix broken builds, remove some unneeded code, and ensure Rails works well with JRuby.</p>

<p><a href="http://contributors.rubyonrails.org/contributors/vijay-dev/commits">Vijay Dev</a> leads the docrails front. He reviews documentation patches, which is a lot of work, and cross-merges docrails and Rails master periodically.</p>

<p><a href="http://contributors.rubyonrails.org/contributors/guillermo-iguaran/commits">Guillermo Iguaran</a> is a regular active core contributor. Recently he has extracted old-style mass-assignment protection to the new <a href="https://github.com/rails/protected_attributes">protected_attributes gem</a>, and is helping with the assets pipeline related projects.</p>

<p><a href="http://contributors.rubyonrails.org/contributors/kennyj/commits">Toshinori Kajihara (kennyj)</a> helps to fix and give attention to Active Record issues, which are the most part of Rails open issues.</p>

<p><a href="http://contributors.rubyonrails.org/contributors/steve-klabnik/commits">Steve Klabnik</a> is working on Rails issues like crazy. I mean, GitHub notifications generated by his activity flood your inbox. Giving sensible feedback, dynamizeing threads, and closing issues. He has been key in halving the number of open issues.</p>

<p><a href="http://contributors.rubyonrails.org/contributors/francesco-rodriguez/commits">Francesco Rodríguez</a> has mainly contributed to the documentation, and also helps with tickets and code. Francesco has extracted page and action caching out to gems.</p>

<p><a href="http://contributors.rubyonrails.org/contributors/piotr-sarnacki/commits">Piotr Sarnacki</a> is an old-timer. Piotr helps constantly in the project and has done a remarkable work on Rails engines and Action Pack.</p>

<p><a href="http://contributors.rubyonrails.org/contributors/prem-sichanugrist/commits">Prem Sichanugrist</a> has been helping regularly since the Rails 3 days in many ways. He recently performed the daunting task of converting all Rails guides from Textile to Markdown.</p>

<p><a href="http://contributors.rubyonrails.org/contributors/carlos-antonio-da-silva/commits">Carlos Antonio da Silva</a> is among the most prolific Rails committers. He contributes in all fronts, code, docs, issues, discussions, etc.</p>

<p><a href="http://contributors.rubyonrails.org/contributors/andrew-white/commits">Andrew White</a> has also been helping regularly for a couple of years or so. He is a solid contributor in several areas and in particular knows routing very well.</p>

<p>:metal:</p>
]]></content>
  </entry>
  
  <entry>
    <title>Rails 3.2.9 has been released!</title>
    <author>
      <name>spastorino</name>
    </author>
    <link href="http://weblog.rubyonrails.org/2012/11/12/ann-rails-3-2-9-has-been-released/"/>
    <updated>2012-11-12T00:00:00-08:00</updated>
    <id>http://weblog.rubyonrails.org/2012/11/12/ann-rails-3-2-9-has-been-released/</id>
    <content type="html"><![CDATA[<p>Hi everyone,</p>

<p>Rails 3.2.9 has been released without new changes since 3.2.9.rc3.</p>

<h2>IMPORTANT!</h2>

<p>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.</p>

<p>A good way to limit the effectiveness of such attacks is to configure your frontend servers to limit the size of the HTTP request line, headers and body. Nginx does this by default. Apache can be configured to do this by setting the LimitRequestBody directive.</p>

<p>In addition, all Ruby 1.9 users are recommended to upgrade to <a href="http://www.ruby-lang.org/en/news/2012/11/09/ruby-1-9-3-p327-is-released/">ruby-1.9.3 patchlevel 327</a> to get this security fix.</p>

<h2>CHANGES since 3.2.8</h2>

<p><em>Action Mailer</em></p>

<ul>
<li><p>Do not render views when mail() isn't called.
Fix #7761</p>

<p><em>Yves Senn</em></p></li>
</ul>


<p><em>Action Pack</em></p>

<ul>
<li><p>Lock sprockets to 2.2.x
REASON: We had some pending fixes in sprockets and sass-rails to make possible to use sprockets version > 2.2. We will do a more conservative sprockets upgrade for this release.
In a next release we can relax the dependency again.
See #8099 for more information.</p>

<p><em>Guillermo Iguaran</em></p></li>
<li><p>Clear url helpers when reloading routes.</p>

<p><em>Santiago Pastorino</em></p></li>
<li><p>Revert the shorthand routes scoped with <code>:module</code> option fix
This added a regression since it is changing the URL mapping.
This makes the stable release backward compatible.</p>

<p><em>Rafael Mendonça França</em></p></li>
<li><p>Revert the <code>assert_template</code> fix to not pass with ever string that matches the template name.
This added a regression since people were relying on this buggy behavior.
This will introduce back #3849 but this stable release will be backward compatible.
Fixes #8068.</p>

<p><em>Rafael Mendonça França</em></p></li>
<li><p>Revert the rename of internal variable on ActionController::TemplateAssertions to prevent
naming collisions. This added a regression related with shoulda-matchers, since it is
expecting the <a href="https://github.com/thoughtbot/shoulda-matchers/blob/9e1188eea68c47d9a56ce6280e45027da6187ab1/lib/shoulda/matchers/action_controller/render_with_layout_matcher.rb#L74">instance variable @layouts</a>.
This will introduce back #7459 but this stable release will be backward compatible.
Fixes #8068.</p>

<p><em>Rafael Mendonça França</em></p></li>
<li><p>Accept :remote as symbolic option for <code>link_to</code> helper. <em>Riley Lynch</em></p></li>
<li><p>Warn when the <code>:locals</code> option is passed to <code>assert_template</code> outside of a view test case
Fix #3415</p>

<p><em>Yves Senn</em></p></li>
<li><p>Rename internal variables on ActionController::TemplateAssertions to prevent
naming collisions. @partials, @templates and @layouts are now prefixed with an underscore.
Fix #7459</p>

<p><em>Yves Senn</em></p></li>
<li><p><code>resource</code> and <code>resources</code> don't modify the passed options hash
Fix #7777</p>

<p><em>Yves Senn</em></p></li>
<li><p>Precompiled assets include aliases from foo.js to foo/index.js and vice versa.</p>

<pre><code># Precompiles phone-&lt;digest&gt;.css and aliases phone/index.css to phone.css.
config.assets.precompile = [ 'phone.css' ]

# Precompiles phone/index-&lt;digest&gt;.css and aliases phone.css to phone/index.css.
config.assets.precompile = [ 'phone/index.css' ]

# Both of these work with either precompile thanks to their aliases.
&lt;%= stylesheet_link_tag 'phone', media: 'all' %&gt;
&lt;%= stylesheet_link_tag 'phone/index', media: 'all' %&gt;
</code></pre>

<p><em>Jeremy Kemper</em></p></li>
<li><p><code>assert_template</code> is no more passing with what ever string that matches
with the template name.</p>

<p>Before when we have a template <code>/layout/hello.html.erb</code>, <code>assert_template</code>
was passing with any string that matches. This behavior allowed false
positive like:</p>

<pre><code>assert_template "layout"
assert_template "out/hello"
</code></pre>

<p>Now it only passes with:</p>

<pre><code>assert_template "layout/hello"
assert_template "hello"
</code></pre>

<p>Fixes #3849.</p>

<p><em>Hugolnx</em></p></li>
<li><p>Handle <code>ActionDispatch::Http::UploadedFile</code> like <code>Rack::Test::UploadedFile</code>, don't call to_param on it. Since
<code>Rack::Test::UploadedFile</code> isn't API compatible this is needed to test file uploads that rely on <code>tempfile</code>
being available.</p>

<p><em>Tim Vandecasteele</em></p></li>
<li><p>Fixed a bug with shorthand routes scoped with the <code>:module</code> option not
adding the module to the controller as described in issue #6497.
This should now work properly:</p>

<pre><code>scope :module =&gt; "engine" do
  get "api/version" # routes to engine/api#version
end
</code></pre>

<p><em>Luiz Felipe Garcia Pereira</em></p></li>
<li><p>Respect <code>config.digest = false</code> for <code>asset_path</code></p>

<p>Previously, the <code>asset_path</code> internals only respected the <code>:digest</code>
option, but ignored the global config setting. This meant that
<code>config.digest = false</code> could not be used in conjunction with
<code>config.compile = false</code> this corrects the behavior.</p>

<p><em>Peter Wagenet</em></p></li>
<li><p>Fix #7646, the log now displays the correct status code when an exception is raised.</p>

<p><em>Yves Senn</em></p></li>
<li><p>Fix handling of date selects when using both disabled and discard options.
Fixes #7431.</p>

<p><em>Vasiliy Ermolovich</em></p></li>
<li><p>Fix select_tag when option_tags is nil.
Fixes #7404.</p>

<p><em>Sandeep Ravichandran</em></p></li>
<li><p><code>javascript_include_tag :all</code> will now not include <code>application.js</code> if the file does not exists. <em>Prem Sichanugrist</em></p></li>
<li><p>Support cookie jar options (e.g., domain :all) for all session stores.
Fixes GH#3047, GH#2483.</p>

<p><em>Ravil Bayramgalin</em></p></li>
<li><p>Performance Improvement to send_file: Avoid having to pass an open file handle as the response body. Rack::Sendfile
will usually intercept the response and just uses the path directly, so no reason to open the file. This performance
improvement also resolves an issue with jRuby encodings, and is the reason for the backport, see issue #6844.</p>

<p><em>Jeremy Kemper &amp; Erich Menge</em></p></li>
</ul>


<p><em>Active Model</em></p>

<ul>
<li><p>Due to a change in builder, nil values and empty strings now generates
closed tags, so instead of this:</p>

<pre><code>&lt;pseudonyms nil=\"true\"&gt;&lt;/pseudonyms&gt;
</code></pre>

<p>It generates this:</p>

<pre><code>&lt;pseudonyms nil=\"true\"/&gt;
</code></pre>

<p><em>Carlos Antonio da Silva</em></p></li>
</ul>


<p><em>Active Record</em></p>

<ul>
<li><p>Fix issue with collection associations calling first(n)/last(n) and attempting
to set the inverse association when <code>:inverse_of</code> was used. Fixes #8087.</p>

<p><em>Carlos Antonio da Silva</em></p></li>
<li><p>Fix ActiveRecord#update_column return value.</p>

<p><em>Aliaxandr</em></p></li>
<li><p>Fix bug when Column is trying to type cast boolean values to integer.
Fixes #8067.</p>

<p><em>Rafael Mendonça França</em></p></li>
<li><p>Fix bug where <code>rake db:test:prepare</code> tries to load the structure.sql into development database.
Fixes #8032.</p>

<p><em>Grace Liu + Rafael Mendonça França</em></p></li>
<li><p>Fixed support for <code>DATABASE_URL</code> environment variable for rake db tasks. <em>Grace Liu</em></p></li>
<li><p>Fix bug where <code>update_columns</code> and <code>update_column</code> would not let you update the primary key column.</p>

<p><em>Henrik Nyh</em></p></li>
<li><p>Decode URI encoded attributes on database connection URLs.</p>

<p><em>Shawn Veader</em></p></li>
<li><p>Fix AR#dup to nullify the validation errors in the dup'ed object. Previously the original
and the dup'ed object shared the same errors.</p>

<ul>
<li>Christian Seiler*</li>
</ul>
</li>
<li><p>Synchronize around deleting from the reserved connections hash.
Fixes #7955</p></li>
<li><p>PostgreSQL adapter correctly fetches default values when using
multiple schemas and domains in a db. Fixes #7914</p>

<p><em>Arturo Pie</em></p></li>
<li><p>Fix deprecation notice when loading a collection association that
selects columns from other tables, if a new record was previously
built using that association.</p>

<p><em>Ernie Miller</em></p></li>
<li><p>The postgres adapter now supports tables with capital letters.
Fix #5920</p>

<p><em>Yves Senn</em></p></li>
<li><p><code>CollectionAssociation#count</code> returns <code>0</code> without querying if the
parent record is not persisted.</p>

<p>Before:</p>

<pre><code>person.pets.count
# SELECT COUNT(*) FROM "pets" WHERE "pets"."person_id" IS NULL
# =&gt; 0
</code></pre>

<p>After:</p>

<pre><code>person.pets.count
# fires without sql query
# =&gt; 0
</code></pre>

<p><em>Francesco Rodriguez</em></p></li>
<li><p>Fix <code>reset_counters</code> crashing on <code>has_many :through</code> associations.
Fix #7822.</p>

<p><em>lulalala</em></p></li>
<li><p>ConnectionPool recognizes checkout_timeout spec key as taking
precedence over legacy wait_timeout spec key, can be used to avoid
conflict with mysql2 use of wait_timeout.  Closes #7684.</p>

<p><em>jrochkind</em></p></li>
<li><p>Rename field_changed? to _field_changed? so that users can create a field named field</p>

<p><em>Akira Matsuda</em>, backported by <em>Steve Klabnik</em></p></li>
<li><p>Fix creation of through association models when using <code>collection=[]</code>
on a <code>has_many :through</code> association from an unsaved model.
Fix #7661.</p>

<p><em>Ernie Miller</em></p></li>
<li><p>Explain only normal CRUD sql (select / update / insert / delete).
Fix problem that explains unexplainable sql. Closes #7544 #6458.</p>

<p><em>kennyj</em></p></li>
<li><p>Backport test coverage to ensure that PostgreSQL auto-reconnect functionality
remains healthy.</p>

<p><em>Steve Jorgensen</em></p></li>
<li><p>Use config['encoding'] instead of config['charset'] when executing
databases.rake in the mysql/mysql2. A correct option for a database.yml
is 'encoding'.</p>

<p><em>kennyj</em></p></li>
<li><p>Fix ConnectionAdapters::Column.type_cast_code integer conversion,
to always convert values to integer calling #to_i. Fixes #7509.</p>

<p><em>Thiago Pradi</em></p></li>
<li><p>Fix time column type casting for invalid time string values to correctly return nil.</p>

<p><em>Adam Meehan</em></p></li>
<li><p>Fix <code>becomes</code> when using a configured <code>inheritance_column</code>.</p>

<p><em>Yves Senn</em></p></li>
<li><p>Fix <code>reset_counters</code> when there are multiple <code>belongs_to</code> association with the
same foreign key and one of them have a counter cache.
Fixes #5200.</p>

<p><em>Dave Desrochers</em></p></li>
<li><p>Round usec when comparing timestamp attributes in the dirty tracking.
Fixes #6975.</p>

<p><em>kennyj</em></p></li>
<li><p>Use inversed parent for first and last child of has_many association.</p>

<p><em>Ravil Bayramgalin</em></p></li>
<li><p>Fix Column.microseconds and Column.fast_string_to_date to avoid converting
timestamp seconds to a float, since it occasionally results in inaccuracies
with microsecond-precision times. Fixes #7352.</p>

<p><em>Ari Pollak</em></p></li>
<li><p>Fix <code>increment!</code>, <code>decrement!</code>, <code>toggle!</code> that was skipping callbacks.
Fixes #7306.</p>

<p><em>Rafael Mendonça França</em></p></li>
<li><p>Fix AR#create to return an unsaved record when AR::RecordInvalid is
raised. Fixes #3217.</p>

<p><em>Dave Yeu</em></p></li>
<li><p>Remove unnecessary transaction when assigning has_one associations with a nil or equal value.
Fix #7191.</p>

<p><em>kennyj</em></p></li>
<li><p>Allow store to work with an empty column.
Fix #4840.</p>

<p><em>Jeremy Walker</em></p></li>
<li><p>Remove prepared statement from system query in postgresql adapter.
Fix #5872.</p>

<p><em>Ivan Evtuhovich</em></p></li>
<li><p>Make sure <code>:environment</code> task is executed before <code>db:schema:load</code> or <code>db:structure:load</code>
Fixes #4772.</p>

<p><em>Seamus Abshere</em></p></li>
</ul>


<p><em>Active Resource</em></p>

<ul>
<li>No changes</li>
</ul>


<p><em>Active Support</em></p>

<ul>
<li><p>Add logger.push_tags and .pop_tags to complement logger.tagged:</p>

<pre><code>class Job
  def before
    Rails.logger.push_tags :jobs, self.class.name
  end

  def after
    Rails.logger.pop_tags 2
  end
end
</code></pre>

<p><em>Jeremy Kemper</em></p></li>
<li><p>Add %:z and %::z format string support to ActiveSupport::TimeWithZone#strftime. [fixes #6962] <em>kennyj</em></p></li>
</ul>


<p><em>Railties</em></p>

<ul>
<li><p>Revert "Respect children paths filter settings"
This reverts commit 53778ec2d716f860646fd43957fd53c8db4da2fe.
Closes #8146</p>

<p><em>Santiago Pastorino</em></p></li>
<li><p>Don't eager-load app/assets and app/views <em>Elia Schito</em></p></li>
<li><p>Update supported ruby versions error message in ruby_version_check.rb <em>Lihan Li</em></p></li>
</ul>


<h2>SHA-1</h2>

<ul>
<li>0b460ffdac39cee7f3321bb430e212c2a42b5dec  actionmailer-3.2.9.gem</li>
<li>8c3657514132ae21d2da2abcad896d8f37c4f1ca  actionpack-3.2.9.gem</li>
<li>3e95d49bca396663d0cc4e94056f2d4e20923200  activemodel-3.2.9.gem</li>
<li>92f9f3aad6ae63786cc916baedda46801b423aab  activerecord-3.2.9.gem</li>
<li>fff833587b753eb0d17e7102f635e769138113f5  activeresource-3.2.9.gem</li>
<li>0989647ca08bb01bf3ab9490ea9b623f4deb065d  activesupport-3.2.9.gem</li>
<li>b2172077c391721bc008723fec92c986c6881e62  rails-3.2.9.gem</li>
<li>bd3e0418546e142cf6afb7fc0e0240545ec96e5c  railties-3.2.9.gem</li>
</ul>


<p>You can find a list of changes between v3.2.8 and v3.2.9 <a href="https://github.com/rails/rails/compare/v3.2.8...v3.2.9">here</a></p>

<p>Thanks to everyone!</p>
]]></content>
  </entry>
  
  <entry>
    <title>Rails 3.2.9.rc3 has been released!</title>
    <author>
      <name>spastorino</name>
    </author>
    <link href="http://weblog.rubyonrails.org/2012/11/9/ann-rails-3-2-9-rc3-has-been-released/"/>
    <updated>2012-11-09T00:00:00-08:00</updated>
    <id>http://weblog.rubyonrails.org/2012/11/9/ann-rails-3-2-9-rc3-has-been-released/</id>
    <content type="html"><![CDATA[<p>Hi everyone,</p>

<p>Rails 3.2.9.rc3 has been released. If no regressions are found I will
release 3.2.9 final this Monday 12th. If you find a regression open an
issue on github and mention me on it, mail me or tweet me, whatever but
let me know :).</p>

<h2>CHANGES since 3.2.9.rc2</h2>

<p><em>Action Mailer</em></p>

<ul>
<li>No changes</li>
</ul>


<p><em>Action Pack</em></p>

<ul>
<li><p>Lock sprockets to 2.2.x
REASON: We had some pending fixes in sprockets and sass-rails to make possible to use sprockets version > 2.2. We will do a more conservative sprockets upgrade for this release.
In a next release we can relax the dependency again.
See #8099 for more information.</p>

<p><em>Guillermo Iguaran</em></p></li>
<li><p>Clear url helpers when reloading routes.</p>

<p><em>Santiago Pastorino</em></p></li>
<li><p>Revert the shorthand routes scoped with <code>:module</code> option fix
This added a regression since it is changing the URL mapping.
This makes the stable release backward compatible.</p>

<p><em>Rafael Mendonça França</em></p></li>
</ul>


<p><em>Active Model</em></p>

<ul>
<li>No changes</li>
</ul>


<p><em>Active Record</em></p>

<ul>
<li>No changes</li>
</ul>


<p><em>Active Resource</em></p>

<ul>
<li>No changes</li>
</ul>


<p><em>Active Support</em></p>

<ul>
<li>No changes</li>
</ul>


<p><em>Railties</em></p>

<ul>
<li><p>Revert "Respect children paths filter settings"
This reverts commit 53778ec2d716f860646fd43957fd53c8db4da2fe.
Closes #8146</p>

<p><em>Santiago Pastorino</em></p></li>
</ul>


<h2>SHA-1</h2>

<ul>
<li>e830dbe5d93f6ea6ed8e32ac75e5c5a5dd4bd0fa  actionmailer-3.2.9.rc3.gem</li>
<li>f50456d082164447d149540a144515877cd714b2  actionpack-3.2.9.rc3.gem</li>
<li>60eca0f399779799e8ea7a8be6b68f3101fe5fe4  activemodel-3.2.9.rc3.gem</li>
<li>0cfec8581690d4a6072c686464ddd66e80ac094e  activerecord-3.2.9.rc3.gem</li>
<li>5414975de41a1dfbb6dbd9cd74b53969c63f2e96  activeresource-3.2.9.rc3.gem</li>
<li>e67293cf746f315cc631155c28d3891a3532bb74  activesupport-3.2.9.rc3.gem</li>
<li>8e62b4db1249024bbb1ea3a87fee701a0cfa5674  rails-3.2.9.rc3.gem</li>
<li>6b4365046903bcd60c99f81bd48cccd1b3faae39  railties-3.2.9.rc3.gem</li>
</ul>


<p>You can find a list of changes between v3.2.9.rc2 and v3.2.9.rc3 <a href="https://github.com/rails/rails/compare/v3.2.9.rc2...v3.2.9.rc3">here</a>
and an exhaustive list of changes since v3.2.8 <a href="https://github.com/rails/rails/compare/v3.2.8...v3.2.9.rc3">here</a>.</p>

<p>Thanks to everyone!</p>
]]></content>
  </entry>
  
  <entry>
    <title>Rails 3.2.9.rc2 has been released!</title>
    <author>
      <name>spastorino</name>
    </author>
    <link href="http://weblog.rubyonrails.org/2012/11/1/ann-rails-3-2-9-rc2-has-been-released/"/>
    <updated>2012-11-01T00:00:00-07:00</updated>
    <id>http://weblog.rubyonrails.org/2012/11/1/ann-rails-3-2-9-rc2-has-been-released/</id>
    <content type="html"><![CDATA[<p>Hi everyone,</p>

<p>Rails 3.2.9.rc2 has been released. If no regressions are found I will
release 3.2.9 final this Monday 5th. If you find a regression open an
issue on github and mention me on it, mail me or tweet me, whatever but
let me know :).</p>

<h2>CHANGES since 3.2.9.rc1</h2>

<p><em>Action Mailer</em></p>

<ul>
<li>No changes</li>
</ul>


<p><em>Action Pack</em></p>

<ul>
<li><p>Revert the <code>assert_template</code> fix to not pass with ever string that matches the template name.
This added a regression since people were relying on this buggy behavior.
This will introduce back #3849 but this stable release will be backward compatible.
Fixes #8068.</p>

<p><em>Rafael Mendonça França</em></p></li>
<li><p>Revert the rename of internal variable on ActionController::TemplateAssertions to prevent
naming collisions. This added a regression related with shoulda-matchers, since it is
expecting the <a href="https://github.com/thoughtbot/shoulda-matchers/blob/9e1188eea68c47d9a56ce6280e45027da6187ab1/lib/shoulda/matchers/action_controller/render_with_layout_matcher.rb#L74">instance variable @layouts</a>.
This will introduce back #7459 but this stable release will be backward compatible.
Fixes #8068.</p>

<p><em>Rafael Mendonça França</em></p></li>
</ul>


<p><em>Active Model</em></p>

<ul>
<li>No changes</li>
</ul>


<p><em>Active Record</em></p>

<ul>
<li><p>Fix issue with collection associations calling first(n)/last(n) and attempting
to set the inverse association when <code>:inverse_of</code> was used. Fixes #8087.</p>

<p><em>Carlos Antonio da Silva</em></p></li>
<li><p>Fix ActiveRecord#update_column return value.</p>

<p><em>Aliaxandr</em></p></li>
<li><p>Fix bug when Column is trying to type cast boolean values to integer.
Fixes #8067.</p>

<p><em>Rafael Mendonça França</em></p></li>
<li><p>Fix bug where <code>rake db:test:prepare</code> tries to load the structure.sql into development database.
Fixes #8032.</p>

<p><em>Grace Liu + Rafael Mendonça França</em></p></li>
<li><p>Fixed support for <code>DATABASE_URL</code> environment variable for rake db tasks. <em>Grace Liu</em></p></li>
</ul>


<p><em>Active Resource</em></p>

<ul>
<li>No changes</li>
</ul>


<p><em>Active Support</em></p>

<ul>
<li>No changes</li>
</ul>


<p><em>Railties</em></p>

<ul>
<li>No changes</li>
</ul>


<h2>SHA-1</h2>

<ul>
<li>3aaf1d1e6057177988b646b86650c5cb5bf0e16e  actionmailer-3.2.9.rc2.gem</li>
<li>c2ff861876ed951a33c01caacf2c17301319c7b1  actionpack-3.2.9.rc2.gem</li>
<li>642da29371a877fda18fc69c51daa882429d609a  activemodel-3.2.9.rc2.gem</li>
<li>f695caa3cac3b1d3f316bfd7d8f0ec69d61211ae  activerecord-3.2.9.rc2.gem</li>
<li>baec057af0cf2a6146b000282b86cf6eb87989e2  activeresource-3.2.9.rc2.gem</li>
<li>b15f9f13de730343448f35ed3b2f26af1ddd76e9  activesupport-3.2.9.rc2.gem</li>
<li>40b5e77a5123545b4e4b6c2e993a30cdb3a38bae  rails-3.2.9.rc2.gem</li>
<li>7921cbcd52302d31188537fb62fa5c75c2be5b2d  railties-3.2.9.rc2.gem</li>
</ul>


<p>You can find a list of changes between v3.2.9.rc1 and v3.2.9.rc2 <a href="https://github.com/rails/rails/compare/v3.2.9.rc1...v3.2.9.rc2">here</a>
and an exhaustive list of changes since v3.2.8 <a href="https://github.com/rails/rails/compare/v3.2.8...v3.2.9.rc2">here</a>.</p>

<p>Thanks to everyone!</p>
]]></content>
  </entry>
  
  <entry>
    <title>Rails 3.2.9.rc1 has been released!</title>
    <author>
      <name>spastorino</name>
    </author>
    <link href="http://weblog.rubyonrails.org/2012/10/29/ann-rails-3-2-9-rc1-has-been-released/"/>
    <updated>2012-10-29T00:00:00-07:00</updated>
    <id>http://weblog.rubyonrails.org/2012/10/29/ann-rails-3-2-9-rc1-has-been-released/</id>
    <content type="html"><![CDATA[<p>Hi everyone,</p>

<p>Rails 3.2.9.rc1 has been released. If no regressions are found I will
release 3.2.9 final this Thursday 1st. If you find a regression open an
issue on github and mention me on it, mail me or tweet me, whatever but
let me know :).</p>

<h2>CHANGES since 3.2.8</h2>

<p><em>Action Mailer</em></p>

<ul>
<li><p>Do not render views when mail() isn't called.
Fix #7761</p>

<p><em>Yves Senn</em></p></li>
</ul>


<p><em>Action Pack</em></p>

<ul>
<li><p>Accept :remote as symbolic option for <code>link_to</code> helper. <em>Riley Lynch</em></p></li>
<li><p>Warn when the <code>:locals</code> option is passed to <code>assert_template</code> outside of a view test case
Fix #3415</p>

<p><em>Yves Senn</em></p></li>
<li><p>Rename internal variables on ActionController::TemplateAssertions to prevent
naming collisions. @partials, @templates and @layouts are now prefixed with an underscore.
Fix #7459</p>

<p><em>Yves Senn</em></p></li>
<li><p><code>resource</code> and <code>resources</code> don't modify the passed options hash
Fix #7777</p>

<p><em>Yves Senn</em></p></li>
<li><p>Precompiled assets include aliases from foo.js to foo/index.js and vice versa.</p>

<pre><code># Precompiles phone-&lt;digest&gt;.css and aliases phone/index.css to phone.css.
config.assets.precompile = [ 'phone.css' ]

# Precompiles phone/index-&lt;digest&gt;.css and aliases phone.css to phone/index.css.
config.assets.precompile = [ 'phone/index.css' ]

# Both of these work with either precompile thanks to their aliases.
&lt;%= stylesheet_link_tag 'phone', media: 'all' %&gt;
&lt;%= stylesheet_link_tag 'phone/index', media: 'all' %&gt;
</code></pre>

<p><em>Jeremy Kemper</em></p></li>
<li><p><code>assert_template</code> is no more passing with what ever string that matches
with the template name.</p>

<p>Before when we have a template <code>/layout/hello.html.erb</code>, <code>assert_template</code>
was passing with any string that matches. This behavior allowed false
positive like:</p>

<pre><code>assert_template "layout"
assert_template "out/hello"
</code></pre>

<p>Now it only passes with:</p>

<pre><code>assert_template "layout/hello"
assert_template "hello"
</code></pre>

<p>Fixes #3849.</p>

<p><em>Hugolnx</em></p></li>
<li><p>Handle <code>ActionDispatch::Http::UploadedFile</code> like <code>Rack::Test::UploadedFile</code>, don't call to_param on it. Since
<code>Rack::Test::UploadedFile</code> isn't API compatible this is needed to test file uploads that rely on <code>tempfile</code>
being available.</p>

<p><em>Tim Vandecasteele</em></p></li>
<li><p>Fixed a bug with shorthand routes scoped with the <code>:module</code> option not
adding the module to the controller as described in issue #6497.
This should now work properly:</p>

<pre><code>scope :module =&gt; "engine" do
  get "api/version" # routes to engine/api#version
end
</code></pre>

<p><em>Luiz Felipe Garcia Pereira</em></p></li>
<li><p>Respect <code>config.digest = false</code> for <code>asset_path</code></p>

<p>Previously, the <code>asset_path</code> internals only respected the <code>:digest</code>
option, but ignored the global config setting. This meant that
<code>config.digest = false</code> could not be used in conjunction with
<code>config.compile = false</code> this corrects the behavior.</p>

<p><em>Peter Wagenet</em></p></li>
<li><p>Fix #7646, the log now displays the correct status code when an exception is raised.</p>

<p><em>Yves Senn</em></p></li>
<li><p>Fix handling of date selects when using both disabled and discard options.
Fixes #7431.</p>

<p><em>Vasiliy Ermolovich</em></p></li>
<li><p>Fix select_tag when option_tags is nil.
Fixes #7404.</p>

<p><em>Sandeep Ravichandran</em></p></li>
<li><p><code>javascript_include_tag :all</code> will now not include <code>application.js</code> if the file does not exists. <em>Prem Sichanugrist</em></p></li>
<li><p>Support cookie jar options (e.g., domain :all) for all session stores.
Fixes GH#3047, GH#2483.</p>

<p><em>Ravil Bayramgalin</em></p></li>
<li><p>Performance Improvement to send_file: Avoid having to pass an open file handle as the response body. Rack::Sendfile
will usually intercept the response and just uses the path directly, so no reason to open the file. This performance
improvement also resolves an issue with jRuby encodings, and is the reason for the backport, see issue #6844.</p>

<p><em>Jeremy Kemper &amp; Erich Menge</em></p></li>
</ul>


<p><em>Active Model</em></p>

<ul>
<li><p>Due to a change in builder, nil values and empty strings now generates
closed tags, so instead of this:</p>

<pre><code>&lt;pseudonyms nil=\"true\"&gt;&lt;/pseudonyms&gt;
</code></pre>

<p>It generates this:</p>

<pre><code>&lt;pseudonyms nil=\"true\"/&gt;
</code></pre>

<p><em>Carlos Antonio da Silva</em></p></li>
</ul>


<p><em>Active Record</em></p>

<ul>
<li><p>Fix bug where <code>update_columns</code> and <code>update_column</code> would not let you update the primary key column.</p>

<p><em>Henrik Nyh</em></p></li>
<li><p>Decode URI encoded attributes on database connection URLs.</p>

<p><em>Shawn Veader</em></p></li>
<li><p>Fix AR#dup to nullify the validation errors in the dup'ed object. Previously the original
and the dup'ed object shared the same errors.</p>

<ul>
<li>Christian Seiler*</li>
</ul>
</li>
<li><p>Synchronize around deleting from the reserved connections hash.
Fixes #7955</p></li>
<li><p>PostgreSQL adapter correctly fetches default values when using
multiple schemas and domains in a db. Fixes #7914</p>

<p><em>Arturo Pie</em></p></li>
<li><p>Fix deprecation notice when loading a collection association that
selects columns from other tables, if a new record was previously
built using that association.</p>

<p><em>Ernie Miller</em></p></li>
<li><p>The postgres adapter now supports tables with capital letters.
Fix #5920</p>

<p><em>Yves Senn</em></p></li>
<li><p><code>CollectionAssociation#count</code> returns <code>0</code> without querying if the
parent record is not persisted.</p>

<p>Before:</p>

<pre><code>person.pets.count
# SELECT COUNT(*) FROM "pets" WHERE "pets"."person_id" IS NULL
# =&gt; 0
</code></pre>

<p>After:</p>

<pre><code>person.pets.count
# fires without sql query
# =&gt; 0
</code></pre>

<p><em>Francesco Rodriguez</em></p></li>
<li><p>Fix <code>reset_counters</code> crashing on <code>has_many :through</code> associations.
Fix #7822.</p>

<p><em>lulalala</em></p></li>
<li><p>ConnectionPool recognizes checkout_timeout spec key as taking
precedence over legacy wait_timeout spec key, can be used to avoid
conflict with mysql2 use of wait_timeout.  Closes #7684.</p>

<p><em>jrochkind</em></p></li>
<li><p>Rename field_changed? to _field_changed? so that users can create a field named field</p>

<p><em>Akira Matsuda</em>, backported by <em>Steve Klabnik</em></p></li>
<li><p>Fix creation of through association models when using <code>collection=[]</code>
on a <code>has_many :through</code> association from an unsaved model.
Fix #7661.</p>

<p><em>Ernie Miller</em></p></li>
<li><p>Explain only normal CRUD sql (select / update / insert / delete).
Fix problem that explains unexplainable sql. Closes #7544 #6458.</p>

<p><em>kennyj</em></p></li>
<li><p>Backport test coverage to ensure that PostgreSQL auto-reconnect functionality
remains healthy.</p>

<p><em>Steve Jorgensen</em></p></li>
<li><p>Use config['encoding'] instead of config['charset'] when executing
databases.rake in the mysql/mysql2. A correct option for a database.yml
is 'encoding'.</p>

<p><em>kennyj</em></p></li>
<li><p>Fix ConnectionAdapters::Column.type_cast_code integer conversion,
to always convert values to integer calling #to_i. Fixes #7509.</p>

<p><em>Thiago Pradi</em></p></li>
<li><p>Fix time column type casting for invalid time string values to correctly return nil.</p>

<p><em>Adam Meehan</em></p></li>
<li><p>Fix <code>becomes</code> when using a configured <code>inheritance_column</code>.</p>

<p><em>Yves Senn</em></p></li>
<li><p>Fix <code>reset_counters</code> when there are multiple <code>belongs_to</code> association with the
same foreign key and one of them have a counter cache.
Fixes #5200.</p>

<p><em>Dave Desrochers</em></p></li>
<li><p>Round usec when comparing timestamp attributes in the dirty tracking.
Fixes #6975.</p>

<p><em>kennyj</em></p></li>
<li><p>Use inversed parent for first and last child of has_many association.</p>

<p><em>Ravil Bayramgalin</em></p></li>
<li><p>Fix Column.microseconds and Column.fast_string_to_date to avoid converting
timestamp seconds to a float, since it occasionally results in inaccuracies
with microsecond-precision times. Fixes #7352.</p>

<p><em>Ari Pollak</em></p></li>
<li><p>Fix <code>increment!</code>, <code>decrement!</code>, <code>toggle!</code> that was skipping callbacks.
Fixes #7306.</p>

<p><em>Rafael Mendonça França</em></p></li>
<li><p>Fix AR#create to return an unsaved record when AR::RecordInvalid is
raised. Fixes #3217.</p>

<p><em>Dave Yeu</em></p></li>
<li><p>Remove unnecessary transaction when assigning has_one associations with a nil or equal value.
Fix #7191.</p>

<p><em>kennyj</em></p></li>
<li><p>Allow store to work with an empty column.
Fix #4840.</p>

<p><em>Jeremy Walker</em></p></li>
<li><p>Remove prepared statement from system query in postgresql adapter.
Fix #5872.</p>

<p><em>Ivan Evtuhovich</em></p></li>
<li><p>Make sure <code>:environment</code> task is executed before <code>db:schema:load</code> or <code>db:structure:load</code>
Fixes #4772.</p>

<p><em>Seamus Abshere</em></p></li>
</ul>


<p><em>Active Resource</em></p>

<ul>
<li>No changes</li>
</ul>


<p><em>Active Support</em></p>

<ul>
<li><p>Add logger.push_tags and .pop_tags to complement logger.tagged:</p>

<pre><code>class Job
  def before
    Rails.logger.push_tags :jobs, self.class.name
  end

  def after
    Rails.logger.pop_tags 2
  end
end
</code></pre>

<p><em>Jeremy Kemper</em></p></li>
<li><p>Add %:z and %::z format string support to ActiveSupport::TimeWithZone#strftime. [fixes #6962] <em>kennyj</em></p></li>
</ul>


<p><em>Railties</em></p>

<ul>
<li><p>Don't eager-load app/assets and app/views <em>Elia Schito</em></p></li>
<li><p>Update supported ruby versions error message in ruby_version_check.rb <em>Lihan Li</em></p></li>
</ul>


<h2>SHA-1</h2>

<ul>
<li>24af6eff6b7c647d04eee9585184ba89f0746d40  actionmailer-3.2.9.rc1.gem</li>
<li>c34ea8f12308c9f6fc4d6b31ce8caa2a562b210a  actionpack-3.2.9.rc1.gem</li>
<li>8b3171fdde905c76a541286192e6cef211d83a70  activemodel-3.2.9.rc1.gem</li>
<li>0752e47880da4bb9be2b0309bce5a444a9271420  activerecord-3.2.9.rc1.gem</li>
<li>d8c1eeedbf3bc33d1560700cc70cb1752cdc811a  activeresource-3.2.9.rc1.gem</li>
<li>8ad917f70cc3b0a04864c8aa705a0e4997736872  activesupport-3.2.9.rc1.gem</li>
<li>6fdc627a032f1f3ded7830e044298e20fd3fc6ce  rails-3.2.9.rc1.gem</li>
<li>444da0c3f2a1e3200d2a613973062c2d3e4ad7d0  railties-3.2.9.rc1.gem</li>
</ul>


<p>You can find a list of changes between v3.2.8 and v3.2.9.rc1 <a href="https://github.com/rails/rails/compare/v3.2.8...v3.2.9.rc1">here</a></p>

<p>Thanks to everyone!</p>
]]></content>
  </entry>
  
  <entry>
    <title>Rails 3.2.8 has been released!</title>
    <author>
      <name>spastorino</name>
    </author>
    <link href="http://weblog.rubyonrails.org/2012/8/9/ann-rails-3-2-8-has-been-released/"/>
    <updated>2012-08-09T00:00:00-07:00</updated>
    <id>http://weblog.rubyonrails.org/2012/8/9/ann-rails-3-2-8-has-been-released/</id>
    <content type="html"><![CDATA[<p>Good news everyone! Rails version 3.2.8 has been released.</p>

<h2>IMPORTANT</h2>

<p>This version contains three important security fixes, please upgrade immediately.</p>

<ul>
<li><a href="https://groups.google.com/d/msg/rubyonrails-security/fV3QUToSMSw/eHBSFOUYHpYJ">CVE-2012-3463 Ruby on Rails Potential XSS Vulnerability in select_tag prompt</a></li>
<li><a href="https://groups.google.com/d/msg/rubyonrails-security/kKGNeMrnmiY/r2yM7xy-G48J">CVE-2012-3464 Potential XSS Vulnerability in Ruby on Rails</a></li>
<li><a href="https://groups.google.com/d/msg/rubyonrails-security/FgVEtBajcTY/tYLS1JJTu38J">CVE-2012-3465 XSS Vulnerability in strip_tags</a></li>
</ul>


<p>One of security fixes impacts all users and is related to HTML escaping code. The other two fixes impacts people using select_tag's prompt option and strip_tags helper from ActionPack.</p>

<p>We are also removing all the deprecation warnings that we introduced in 3.2.x.
We have decided to stop introducing API deprecations in all point releases going forward. From now on, it'll only happen in majors/minors.</p>

<h2>CHANGES since 3.2.7</h2>

<p><em>Action Mailer</em></p>

<ul>
<li>No changes</li>
</ul>


<p><em>Action Pack</em></p>

<ul>
<li><p>html_escape should escape single quotes. <em>Santiago Pastorino</em></p></li>
<li><p>Reverted the deprecation of <code>:confirm</code>. <em>Rafael Mendonça França</em></p></li>
<li><p>Reverted the deprecation of <code>:disable_with</code>. <em>Rafael Mendonça França</em></p></li>
<li><p>Reverted the deprecation of <code>:mouseover</code> option to <code>image_tag</code>. <em>Rafael Mendonça França</em></p></li>
<li><p>Reverted the deprecation of <code>button_to_function</code> and <code>link_to_function</code> helpers. <em>Rafael Mendonça França</em></p></li>
</ul>


<p><em>Active Model</em></p>

<ul>
<li>No changes</li>
</ul>


<p><em>Active Record</em></p>

<ul>
<li><p>Do not set RAILS_ENV to "development" when using <code>db:test:prepare</code> and related rake tasks.
This was causing the truncation of the development database data when using RSpec.
In RC2 was fixed again when using config.active_record.schema_format = :sql
<em>Rafael Mendonça França</em></p></li>
<li><p>Do not consider the numeric attribute as changed if the old value is zero and the new value is not a string. Fixes #7237. <em>Rafael Mendonça França</em></p></li>
<li><p>Removes the deprecation of <code>update_attribute</code>. <em>fxn</em></p></li>
<li><p>Reverted the deprecation of <code>composed_of</code>. <em>Rafael Mendonça França</em></p></li>
<li><p>Reverted the deprecation of <code>*_sql</code> association options. They will
be deprecated in 4.0 instead. <em>Jon Leighton</em></p></li>
<li><p>Do not eager load AR session store. ActiveRecord::SessionStore depends on the abstract store
in Action Pack. Eager loading this class would break client code that eager loads Active Record
standalone.
Fixes #7160</p>

<p><em>Xavier Noria</em></p></li>
<li><p>Do not set RAILS_ENV to "development" when using <code>db:test:prepare</code> and related rake tasks.
This was causing the truncation of the development database data when using RSpec.
Fixes #7175.</p>

<p><em>Rafael Mendonça França</em></p></li>
</ul>


<p><em>Active Resource</em></p>

<ul>
<li>No changes</li>
</ul>


<p><em>Active Support</em></p>

<ul>
<li><p>Fix ActiveSupport integration with Mocha > 0.12.1. <em>Mike Gunderloy</em></p></li>
<li><p>Reverted the deprecation of ActiveSupport::JSON::Variable. <em>Rafael Mendonça França</em></p></li>
</ul>


<p><em>Railties</em></p>

<ul>
<li>ERB scaffold generator use the <code>:data =&gt; { :confirm =&gt; "Text" }</code> syntax instead of <code>:confirm</code>. <em>Rafael Mendonça França</em></li>
</ul>


<h2>SHA-1</h2>

<ul>
<li>20525face84f3cdc8b0fc039e0f75ec4963e3677  actionmailer-3.2.8.gem</li>
<li>ccc63cc2fcb3131b92d45cf5834aa629857d7258  actionpack-3.2.8.gem</li>
<li>df7fb9febe248201fd1ad741a2044324f4c90cc9  activemodel-3.2.8.gem</li>
<li>96e876f625b98915d2b1994c06ea057bf7dd23b8  activerecord-3.2.8.gem</li>
<li>195e1e4653e6e06f469ea20e181727ef9d940ee7  activeresource-3.2.8.gem</li>
<li>e5136f556b62343425cc147a8990bd043430354d  activesupport-3.2.8.gem</li>
<li>35581ffc256d73d217537170b0e116cf4545752e  rails-3.2.8.gem</li>
<li>e44accc5d057866087856a521398250fe082b70b  railties-3.2.8.gem</li>
</ul>


<p>You can find an exhaustive list of changes on
<a href="https://github.com/rails/rails/compare/v3.2.7...v3.2.8">github</a>.</p>

<p>Thanks to everyone!</p>
]]></content>
  </entry>
  
  <entry>
    <title>Rails 3.1.8 has been released!</title>
    <author>
      <name>spastorino</name>
    </author>
    <link href="http://weblog.rubyonrails.org/2012/8/9/ann-rails-3-1-8-has-been-released/"/>
    <updated>2012-08-09T00:00:00-07:00</updated>
    <id>http://weblog.rubyonrails.org/2012/8/9/ann-rails-3-1-8-has-been-released/</id>
    <content type="html"><![CDATA[<p>Good news everyone! Rails version 3.1.8 has been released.</p>

<p>This release of Rails contains three important security fixes:</p>

<ul>
<li><a href="https://groups.google.com/d/msg/rubyonrails-security/fV3QUToSMSw/eHBSFOUYHpYJ">CVE-2012-3463 Ruby on Rails Potential XSS Vulnerability in select_tag prompt</a></li>
<li><a href="https://groups.google.com/d/msg/rubyonrails-security/kKGNeMrnmiY/r2yM7xy-G48J">CVE-2012-3464 Potential XSS Vulnerability in Ruby on Rails</a></li>
<li><a href="https://groups.google.com/d/msg/rubyonrails-security/FgVEtBajcTY/tYLS1JJTu38J">CVE-2012-3465 XSS Vulnerability in strip_tags</a></li>
</ul>


<p>All changes can be found on <a href="https://github.com/rails/rails/compare/v3.1.7...v3.1.8">github</a>.</p>

<p>Thanks everyone!</p>
]]></content>
  </entry>
  
  <entry>
    <title>Rails 3.0.17 has been released!</title>
    <author>
      <name>spastorino</name>
    </author>
    <link href="http://weblog.rubyonrails.org/2012/8/9/ann-rails-3-0-17-has-been-released/"/>
    <updated>2012-08-09T00:00:00-07:00</updated>
    <id>http://weblog.rubyonrails.org/2012/8/9/ann-rails-3-0-17-has-been-released/</id>
    <content type="html"><![CDATA[<p>Good news everyone! Rails version 3.0.17 has been released.</p>

<p>This release of Rails contains three important security fixes:</p>

<ul>
<li><a href="https://groups.google.com/d/msg/rubyonrails-security/fV3QUToSMSw/eHBSFOUYHpYJ">CVE-2012-3463 Ruby on Rails Potential XSS Vulnerability in select_tag prompt</a></li>
<li><a href="https://groups.google.com/d/msg/rubyonrails-security/kKGNeMrnmiY/r2yM7xy-G48J">CVE-2012-3464 Potential XSS Vulnerability in Ruby on Rails</a></li>
<li><a href="https://groups.google.com/d/msg/rubyonrails-security/FgVEtBajcTY/tYLS1JJTu38J">CVE-2012-3465 XSS Vulnerability in strip_tags</a></li>
</ul>


<p>All changes can be found on <a href="https://github.com/rails/rails/compare/v3.0.16...v3.0.17">github</a>.</p>

<p>Thanks everyone!</p>
]]></content>
  </entry>
  
</feed>