Add support for Reply-To field in mail_to helper
Don't raise on out-of-range datetimes passed by a user
Describe gotcha for 'status' option [ci skip]
Update Active Record's attribute query methods documentation to describe its full behaviour. [ci skip]
Merge pull request #18158 from YayConnolly/master

Describe gotcha for 'status' option [ci skip]
Fixing numeric attrs when set to same negative value

This bug occurs when an attribute of an ActiveRecord model is an
ActiveRecord::Type::Integer type or a ActiveRecord::Type::Decimal type (or any
other type that includes the ActiveRecord::Type::Numeric module. When the value
of the attribute is negative and is set to the same negative value, it is marked
as changed.

Take the following example of a Person model with the integer attribute age:

    class Person < ActiveRecord::Base
      # age          :integer(4)
    end

The following will produce the error:

    person = Person.new(age: -1)
    person.age = -1
    person.changes
    => { "age" => [-1, -1] }
    person.age_changed?
    => true

The problematic line is here:

    module ActiveRecord
      module Type
        module Numeric
          ...

          def non_numeric_string?(value)
            # 'wibble'.to_i will give zero, we want to make sure
            # that we aren't marking int zero to string zero as
            # changed.
            value.to_s !~ /\A\d+\.?\d*\z/
          end
        end
      end
    end

The regex match doesn't accept numbers with a leading '-'.
Clarify that the word present refers to Object#present?. [ci skip]

Update Active Record's attribute query methods documentation to clarify that whether an attribute is present is based on Object#present?. This gives people a place to go see what the exact definition of presence is. [ci skip]
fix typo in nodoc
Merge pull request #18163 from y-yagi/fix_nodoc_typo

fix typo in nodoc [ci skip]
Merge pull request #18162 from romaimperator/master

Fixing numeric attrs when set to same negative value
cleanup CHANGELOGs. [ci skip]
Add information about "allow_destroy" requiring an ID. [ci skip]

I just wasted an absurd amount of time trying to figure out why my model
wasn't being deleted even though I was setting `_destroy` to true like
the instructions said. Making the documentation a little bit clear so
that someone like me doesn't waste their time in future.
Replace deprecated `#load_schema` with `#load_schema_for`.
docs, replace ` with + for proper rdoc output. [ci skip]
Merge Pull Request #18157

Conflicts:
	activerecord/CHANGELOG.md
Merge pull request #18145 from georgemillo/patch-2

Add information about "allow_destroy" requiring an ID. [ci skip]
Changelog for 99a6f9e60ea55924b44f894a16f8de0162cf2702

Here you go, @senny. :grin:
Remove block from super
Fix connection leak when a thread checks in additional connections.

The code in `ConnectionPool#release` assumed that a single thread only
ever holds a single connection, and thus that releasing a connection
only requires the owning thread_id.

There is a trivial counterexample to this assumption: code that checks
out additional connections from the pool in the same thread. For
instance:

    connection_1 = ActiveRecord::Base.connection
    connection_2 = ActiveRecord::Base.connection_pool.checkout
    ActiveRecord::Base.connection_pool.checkin(connection_2)
    connection_3 = ActiveRecord::Base.connection

At this point, connection_1 has been removed from the
`@reserved_connections` hash, causing a NEW connection to be returned as
connection_3 and the loss of any tracking info on connection_1. As long
as the thread in this example lives, connection_1 will be inaccessible
and un-reapable. If this block of code runs more times than the size of
the connection pool in a single thread, every subsequent connection
attempt will timeout, as all of the available connections have been
leaked.

Reverts parts of 9e457a8654fa89fe329719f88ae3679aefb21e56 and
essentially all of 4367d2f05cbeda855820e25a08353d4b7b3457ac
Merge pull request #18166 from merongivian/search_field_refactor

Remove block from super