activesupport 5.1.6 → 5.2.0

data/CHANGELOG.md

@@ -1,6 +1,11 @@
-## Rails 5.1.6 (March 29, 2018) ##
+## Rails 5.2.0 (April 09, 2018) ##
 
-*   Return all mappings for a timezone identifier in `country_zones`
+*   Caching: MemCache and Redis `read_multi` and `fetch_multi` speedup.
+    Read from the local in-memory cache before consulting the backend.
+
+    *Gabriel Sobrinho*
+
+*   Return all mappings for a timezone identifier in `country_zones`.
 
     Some timezones like `Europe/London` have multiple mappings in
     `ActiveSupport::TimeZone::MAPPING` so return all of them instead
@@ -16,758 +21,502 @@
 
     *Andrew White*
 
+*   Add support for connection pooling on RedisCacheStore.
 
-## Rails 5.1.5 (February 14, 2018) ##
-
-*   No changes.
-
-
-## Rails 5.1.4 (September 07, 2017) ##
-
-*   No changes.
-
-
-## Rails 5.1.4.rc1 (August 24, 2017) ##
-
-*   No changes.
-
-
-## Rails 5.1.3 (August 03, 2017) ##
-
-*   No changes.
-
-
-## Rails 5.1.3.rc3 (July 31, 2017) ##
-
-*   Fix modulo operations involving durations
-
-    Rails 5.1 introduce an `ActiveSupport::Duration::Scalar` class as a wrapper
-    around a numeric value as a way of ensuring a duration was the outcome of
-    an expression. However the implementation was missing support for modulo
-    operations. This support has now been added and should result in a duration
-    being returned from expressions involving modulo operations.
-
-    Prior to Rails 5.1:
-
-        5.minutes % 2.minutes
-        => 60
-
-    Now:
-
-        5.minutes % 2.minutes
-        => 1 minute
-
-    Fixes #29603 and #29743.
-
-    *Sayan Chakraborty*, *Andrew White*
-
-*   Fix division where a duration is the denominator
-
-    PR #29163 introduced a change in behavior when a duration was the denominator
-    in a calculation - this was incorrect as dividing by a duration should always
-    return a `Numeric`. The behavior of previous versions of Rails has been restored.
-
-    Fixes #29592.
-
-    *Andrew White*
-
-
-## Rails 5.1.3.rc2 (July 25, 2017) ##
-
-*   No changes.
-
-
-## Rails 5.1.3.rc1 (July 19, 2017) ##
-
-*   No changes.
-
-
-## Rails 5.1.2 (June 26, 2017) ##
-
-*   Cache: Restore the `options = nil` argument for `LocalStore#clear`
-    that was removed in 5.1.0. Restores compatibility with backends that
-    take an options argument and use the local cache strategy.
-
-    *Jeremy Daer*
-
-*   Fix implicit coercion calculations with scalars and durations
-
-    Previously calculations where the scalar is first would be converted to a duration
-    of seconds but this causes issues with dates being converted to times, e.g:
-
-        Time.zone = "Beijing"           # => Asia/Shanghai
-        date = Date.civil(2017, 5, 20)  # => Mon, 20 May 2017
-        2 * 1.day                       # => 172800 seconds
-        date + 2 * 1.day                # => Mon, 22 May 2017 00:00:00 CST +08:00
-
-    Now the `ActiveSupport::Duration::Scalar` calculation methods will try to maintain
-    the part structure of the duration where possible, e.g:
-
-        Time.zone = "Beijing"           # => Asia/Shanghai
-        date = Date.civil(2017, 5, 20)  # => Mon, 20 May 2017
-        2 * 1.day                       # => 2 days
-        date + 2 * 1.day                # => Mon, 22 May 2017
-
-    Fixes #29160, #28970.
-
-    *Andrew White*
-
-
-## Rails 5.1.1 (May 12, 2017) ##
+    *fatkodima*
 
-*   No changes.
+*   Support hash as first argument in `assert_difference`. This allows to specify multiple
+    numeric differences in the same assertion.
 
+        assert_difference ->{ Article.count } => 1, ->{ Post.count } => 2
 
-## Rails 5.1.0 (April 27, 2017) ##
+    *Julien Meichelbeck*
 
-*   `ActiveSupport::EventedFileUpdateChecker` no longer listens to
-    directories outside of the application directory.
+*   Add missing instrumentation for `read_multi` in `ActiveSupport::Cache::Store`.
 
-    *radiospiel*
+    *Ignatius Reza Lesmana*
 
-*   Return unmapped timezones from `country_zones`
+*   `assert_changes` will always assert that the expression changes,
+    regardless of `from:` and `to:` argument combinations.
 
-    If a country doesn't exist in the MAPPINGS hash then create a new
-    `ActiveSupport::Timezone` instance using the supplied timezone id.
+    *Daniel Ma*
 
-    Fixes #28431.
+*   Use SHA-1 to generate non-sensitive digests, such as the ETag header.
 
-    *Andrew White*
+    Enabled by default for new apps; upgrading apps can opt in by setting
+    `config.active_support.use_sha1_digests = true`.
 
-*   Add ActiveSupport::Deprecation::DeprecatedConstantAccessor
+    *Dmitri Dolguikh*, *Eugene Kenny*
 
-    Provides transparent deprecation of constants, compatible with exceptions.
-    Example usage:
+*   Changed default behaviour of `ActiveSupport::SecurityUtils.secure_compare`,
+    to make it not leak length information even for variable length string.
 
-        module Example
-          include ActiveSupport::Deprecation::DeprecatedConstantAccessor
-          deprecate_constant 'OldException', 'Elsewhere::NewException'
-        end
+    Renamed old `ActiveSupport::SecurityUtils.secure_compare` to `fixed_length_secure_compare`,
+    and started raising `ArgumentError` in case of length mismatch of passed strings.
 
-    *Dominic Cleal*
-
-*   Fixed bug in `DateAndTime::Compatibility#to_time` that caused it to
-    raise `RuntimeError: can't modify frozen Time` when called on any frozen `Time`.
-    Properly pass through the frozen `Time` or `ActiveSupport::TimeWithZone` object
-    when calling `#to_time`.
-
-    *Kevin McPhillips* & *Andrew White*
+    *Vipul A M*
 
-*   Remove implicit coercion deprecation of durations
+*   Make `ActiveSupport::TimeZone.all` return only time zones that are in
+    `ActiveSupport::TimeZone::MAPPING`.
 
-    In #28204 we deprecated implicit conversion of durations to a numeric which
-    represented the number of seconds in the duration because of unwanted side
-    effects with calculations on durations and dates. This unfortunately had
-    the side effect of forcing a explicit cast when configuring third-party
-    libraries like expiration in Redis, e.g:
+    Fixes #7245.
 
-        redis.expire("foo", 5.minutes)
+    *Chris LaRose*
 
-    To work around this we've removed the deprecation and added a private class
-    that wraps the numeric and can perform calculation involving durations and
-    ensure that they remain a duration irrespective of the order of operations.
+*   MemCacheStore: Support expiring counters.
 
-    *Andrew White*
+    Pass `expires_in: [seconds]` to `#increment` and `#decrement` options
+    to set the Memcached TTL (time-to-live) if the counter doesn't exist.
+    If the counter exists, Memcached doesn't extend its expiry when it's
+    incremented or decremented.
 
-*   Update `titleize` regex to allow apostrophes
+    ```
+    Rails.cache.increment("my_counter", 1, expires_in: 2.minutes)
+    ```
 
-    In 4b685aa the regex in `titleize` was updated to not match apostrophes to
-    better reflect the nature of the transformation. Unfortunately, this had the
-    side effect of breaking capitalization on the first word of a sub-string, e.g:
+    *Takumasa Ochi*
 
-        >> "This was 'fake news'".titleize
-        => "This Was 'fake News'"
+*   Handle `TZInfo::AmbiguousTime` errors.
 
-    This is fixed by extending the look-behind to also check for a word
-    character on the other side of the apostrophe.
+    Make `ActiveSupport::TimeWithZone` match Ruby's handling of ambiguous
+    times by choosing the later period, e.g.
 
-    Fixes #28312.
+    Ruby:
+    ```
+    ENV["TZ"] = "Europe/Moscow"
+    Time.local(2014, 10, 26, 1, 0, 0)   # => 2014-10-26 01:00:00 +0300
+    ```
 
-    *Andrew White*
+    Before:
+    ```
+    >> "2014-10-26 01:00:00".in_time_zone("Moscow")
+    TZInfo::AmbiguousTime: 26/10/2014 01:00 is an ambiguous local time.
+    ```
 
-*   Add `rfc3339` aliases to `xmlschema` for `Time` and `ActiveSupport::TimeWithZone`
+    After:
+    ```
+    >> "2014-10-26 01:00:00".in_time_zone("Moscow")
+    => Sun, 26 Oct 2014 01:00:00 MSK +03:00
+    ```
 
-    For naming consistency when using the RFC 3339 profile of ISO 8601 in applications.
+    Fixes #17395.
 
     *Andrew White*
 
-*   Add `Time.rfc3339` parsing method
-
-    `Time.xmlschema` and consequently its alias `iso8601` accepts timestamps
-    without a offset in contravention of the RFC 3339 standard. This method
-    enforces that constraint and raises an `ArgumentError` if it doesn't.
+*   Redis cache store.
+
+    ```
+    # Defaults to `redis://localhost:6379/0`. Only use for dev/test.
+    config.cache_store = :redis_cache_store
+
+    # Supports all common cache store options (:namespace, :compress,
+    # :compress_threshold, :expires_in, :race_condition_ttl) and all
+    # Redis options.
+    cache_password = Rails.application.secrets.redis_cache_password
+    config.cache_store = :redis_cache_store, driver: :hiredis,
+      namespace: 'myapp-cache', compress: true, timeout: 1,
+      url: "redis://:#{cache_password}@myapp-cache-1:6379/0"
+
+    # Supports Redis::Distributed with multiple hosts
+    config.cache_store = :redis_cache_store, driver: :hiredis
+      namespace: 'myapp-cache', compress: true,
+      url: %w[
+        redis://myapp-cache-1:6379/0
+        redis://myapp-cache-1:6380/0
+        redis://myapp-cache-2:6379/0
+        redis://myapp-cache-2:6380/0
+        redis://myapp-cache-3:6379/0
+        redis://myapp-cache-3:6380/0
+      ]
+
+    # Or pass a builder block
+    config.cache_store = :redis_cache_store,
+      namespace: 'myapp-cache', compress: true,
+      redis: -> { Redis.new … }
+    ```
+
+    Deployment note: Take care to use a *dedicated Redis cache* rather
+    than pointing this at your existing Redis server. It won't cope well
+    with mixed usage patterns and it won't expire cache entries by default.
+
+    Redis cache server setup guide: https://redis.io/topics/lru-cache
 
-    *Andrew White*
+    *Jeremy Daer*
 
-*   Add `ActiveSupport::TimeZone.rfc3339` parsing method
+*   Cache: Enable compression by default for values > 1kB.
 
-    Previously, there was no way to get a RFC 3339 timestamp into a specific
-    timezone without either using `parse` or chaining methods. The new method
-    allows parsing directly into the timezone, e.g:
+    Compression has long been available, but opt-in and at a 16kB threshold.
+    It wasn't enabled by default due to CPU cost. Today it's cheap and typical
+    cache data is eminently compressible, such as HTML or JSON fragments.
+    Compression dramatically reduces Memcached/Redis mem usage, which means
+    the same cache servers can store more data, which means higher hit rates.
 
-        >> Time.zone = "Hawaii"
-        => "Hawaii"
-        >> Time.zone.rfc3339("1999-12-31T14:00:00Z")
-        => Fri, 31 Dec 1999 14:00:00 HST -10:00
+    To disable compression, pass `compress: false` to the initializer.
 
-    This new method has stricter semantics than the current `parse` method,
-    and will raise an `ArgumentError` instead of returning nil, e.g:
+    *Jeremy Daer*
 
-        >> Time.zone = "Hawaii"
-        => "Hawaii"
-        >> Time.zone.rfc3339("foobar")
-        ArgumentError: invalid date
-        >> Time.zone.parse("foobar")
-        => nil
+*   Allow `Range#include?` on TWZ ranges.
 
-    It will also raise an `ArgumentError` when either the time or offset
-    components are missing, e.g:
+    In #11474 we prevented TWZ ranges being iterated over which matched
+    Ruby's handling of Time ranges and as a consequence `include?`
+    stopped working with both Time ranges and TWZ ranges. However in
+    ruby/ruby@b061634 support was added for `include?` to use `cover?`
+    for 'linear' objects. Since we have no way of making Ruby consider
+    TWZ instances as 'linear' we have to override `Range#include?`.
 
-        >> Time.zone = "Hawaii"
-        => "Hawaii"
-        >> Time.zone.rfc3339("1999-12-31")
-        ArgumentError: invalid date
-        >> Time.zone.rfc3339("1999-12-31T14:00:00")
-        ArgumentError: invalid date
+    Fixes #30799.
 
     *Andrew White*
 
-*   Add `ActiveSupport::TimeZone.iso8601` parsing method
-
-    Previously, there was no way to get a ISO 8601 timestamp into a specific
-    timezone without either using `parse` or chaining methods. The new method
-    allows parsing directly into the timezone, e.g:
-
-        >> Time.zone = "Hawaii"
-        => "Hawaii"
-        >> Time.zone.iso8601("1999-12-31T14:00:00Z")
-        => Fri, 31 Dec 1999 14:00:00 HST -10:00
+*   Fix acronym support in `humanize`.
 
-    If the timestamp is a ISO 8601 date (YYYY-MM-DD), then the time is set
-    to midnight, e.g:
+    Acronym inflections are stored with lowercase keys in the hash but
+    the match wasn't being lowercased before being looked up in the hash.
+    This shouldn't have any performance impact because before it would
+    fail to find the acronym and perform the `downcase` operation anyway.
 
-        >> Time.zone = "Hawaii"
-        => "Hawaii"
-        >> Time.zone.iso8601("1999-12-31")
-        => Fri, 31 Dec 1999 00:00:00 HST -10:00
-
-    This new method has stricter semantics than the current `parse` method,
-    and will raise an `ArgumentError` instead of returning nil, e.g:
-
-        >> Time.zone = "Hawaii"
-        => "Hawaii"
-        >> Time.zone.iso8601("foobar")
-        ArgumentError: invalid date
-        >> Time.zone.parse("foobar")
-        => nil
+    Fixes #31052.
 
     *Andrew White*
 
-*   Deprecate implicit coercion of `ActiveSupport::Duration`
-
-    Currently `ActiveSupport::Duration` implicitly converts to a seconds
-    value when used in a calculation except for the explicit examples of
-    addition and subtraction where the duration is the receiver, e.g:
-
-        >> 2 * 1.day
-        => 172800
-
-    This results in lots of confusion especially when using durations
-    with dates because adding/subtracting a value from a date treats
-    integers as a day and not a second, e.g:
-
-        >> Date.today
-        => Wed, 01 Mar 2017
-        >> Date.today + 2 * 1.day
-        => Mon, 10 Apr 2490
+*   Add same method signature for `Time#prev_year` and `Time#next_year`
+    in accordance with `Date#prev_year`, `Date#next_year`.
 
-    To fix this we're implementing `coerce` so that we can provide a
-    deprecation warning with the intent of removing the implicit coercion
-    in Rails 5.2, e.g:
+    Allows pass argument for `Time#prev_year` and `Time#next_year`.
 
-        >> 2 * 1.day
-        DEPRECATION WARNING: Implicit coercion of ActiveSupport::Duration
-        to a Numeric is deprecated and will raise a TypeError in Rails 5.2.
-        => 172800
-
-    In Rails 5.2 it will raise `TypeError`, e.g:
-
-        >> 2 * 1.day
-        TypeError: ActiveSupport::Duration can't be coerced into Integer
+    Before:
+    ```
+    Time.new(2017, 9, 16, 17, 0).prev_year    # => 2016-09-16 17:00:00 +0300
+    Time.new(2017, 9, 16, 17, 0).prev_year(1)
+    # => ArgumentError: wrong number of arguments (given 1, expected 0)
 
-    This is the same behavior as with other types in Ruby, e.g:
+    Time.new(2017, 9, 16, 17, 0).next_year    # => 2018-09-16 17:00:00 +0300
+    Time.new(2017, 9, 16, 17, 0).next_year(1)
+    # => ArgumentError: wrong number of arguments (given 1, expected 0)
+    ```
 
-        >> 2 * "foo"
-        TypeError: String can't be coerced into Integer
-        >> "foo" * 2
-        => "foofoo"
+    After:
+    ```
+    Time.new(2017, 9, 16, 17, 0).prev_year    # => 2016-09-16 17:00:00 +0300
+    Time.new(2017, 9, 16, 17, 0).prev_year(1) # => 2016-09-16 17:00:00 +0300
 
-    As part of this deprecation add `*` and `/` methods to `AS::Duration`
-    so that calculations that keep the duration as the receiver work
-    correctly whether the final receiver is a `Date` or `Time`, e.g:
+    Time.new(2017, 9, 16, 17, 0).next_year    # => 2018-09-16 17:00:00 +0300
+    Time.new(2017, 9, 16, 17, 0).next_year(1) # => 2018-09-16 17:00:00 +0300
+    ```
 
-        >> Date.today
-        => Wed, 01 Mar 2017
-        >> Date.today + 1.day * 2
-        => Fri, 03 Mar 2017
+    *bogdanvlviv*
 
-    Fixes #27457.
+*   Add same method signature for `Time#prev_month` and `Time#next_month`
+    in accordance with `Date#prev_month`, `Date#next_month`.
 
-    *Andrew White*
+    Allows pass argument for `Time#prev_month` and `Time#next_month`.
 
-*   Update `DateTime#change` to support `:usec` and `:nsec` options.
+    Before:
+    ```
+    Time.new(2017, 9, 16, 17, 0).prev_month    # => 2017-08-16 17:00:00 +0300
+    Time.new(2017, 9, 16, 17, 0).prev_month(1)
+    # => ArgumentError: wrong number of arguments (given 1, expected 0)
 
-    Adding support for these options now allows us to update the `DateTime#end_of`
-    methods to match the equivalent `Time#end_of` methods, e.g:
+    Time.new(2017, 9, 16, 17, 0).next_month    # => 2017-10-16 17:00:00 +0300
+    Time.new(2017, 9, 16, 17, 0).next_month(1)
+    # => ArgumentError: wrong number of arguments (given 1, expected 0)
+    ```
 
-        datetime = DateTime.now.end_of_day
-        datetime.nsec == 999999999 # => true
+    After:
+    ```
+    Time.new(2017, 9, 16, 17, 0).prev_month    # => 2017-08-16 17:00:00 +0300
+    Time.new(2017, 9, 16, 17, 0).prev_month(1) # => 2017-08-16 17:00:00 +0300
 
-    Fixes #21424.
+    Time.new(2017, 9, 16, 17, 0).next_month    # => 2017-10-16 17:00:00 +0300
+    Time.new(2017, 9, 16, 17, 0).next_month(1) # => 2017-10-16 17:00:00 +0300
+    ```
 
-    *Dan Moore*, *Andrew White*
+    *bogdanvlviv*
 
-*   Add `ActiveSupport::Duration#before` and `#after` as aliases for `#until` and `#since`
+*   Add same method signature for `Time#prev_day` and `Time#next_day`
+    in accordance with `Date#prev_day`, `Date#next_day`.
 
-    These read more like English and require less mental gymnastics to read and write.
+    Allows pass argument for `Time#prev_day` and `Time#next_day`.
 
     Before:
+    ```
+    Time.new(2017, 9, 16, 17, 0).prev_day    # => 2017-09-15 17:00:00 +0300
+    Time.new(2017, 9, 16, 17, 0).prev_day(1)
+    # => ArgumentError: wrong number of arguments (given 1, expected 0)
 
-        2.weeks.since(customer_start_date)
-        5.days.until(today)
+    Time.new(2017, 9, 16, 17, 0).next_day    # => 2017-09-17 17:00:00 +0300
+    Time.new(2017, 9, 16, 17, 0).next_day(1)
+    # => ArgumentError: wrong number of arguments (given 1, expected 0)
+    ```
 
     After:
+    ```
+    Time.new(2017, 9, 16, 17, 0).prev_day    # => 2017-09-15 17:00:00 +0300
+    Time.new(2017, 9, 16, 17, 0).prev_day(1) # => 2017-09-15 17:00:00 +0300
 
-        2.weeks.after(customer_start_date)
-        5.days.before(today)
-
-    *Nick Johnstone*
-
-*   Soft-deprecated the top-level `HashWithIndifferentAccess` constant.
-    `ActiveSupport::HashWithIndifferentAccess` should be used instead.
-
-    Fixes #28157.
-
-    *Robin Dupret*
-
-*   In Core Extensions, make `MarshalWithAutoloading#load` pass through the second, optional
-    argument for `Marshal#load( source [, proc] )`. This way we don't have to do
-    `Marshal.method(:load).super_method.call(source, proc)` just to be able to pass a proc.
+    Time.new(2017, 9, 16, 17, 0).next_day    # => 2017-09-17 17:00:00 +0300
+    Time.new(2017, 9, 16, 17, 0).next_day(1) # => 2017-09-17 17:00:00 +0300
+    ```
 
-    *Jeff Latz*
+    *bogdanvlviv*
 
-*   `ActiveSupport::Gzip.decompress` now checks checksum and length in footer.
+*   `IO#to_json` now returns the `to_s` representation, rather than
+    attempting to convert to an array. This fixes a bug where `IO#to_json`
+    would raise an `IOError` when called on an unreadable object.
 
-    *Dylan Thacker-Smith*
+    Fixes #26132.
 
-*   Cache `ActiveSupport::TimeWithZone#to_datetime` before freezing.
+    *Paul Kuruvilla*
 
-    *Adam Rice*
-
-*   Deprecate `ActiveSupport.halt_callback_chains_on_return_false`.
+*   Remove deprecated `halt_callback_chains_on_return_false` option.
 
     *Rafael Mendonça França*
 
-*   Remove deprecated behavior that halts callbacks when the return is false.
+*   Remove deprecated `:if` and `:unless` string filter for callbacks.
 
     *Rafael Mendonça França*
 
-*   Deprecate passing string to `:if` and `:unless` conditional options
-    on `set_callback` and `skip_callback`.
-
-    *Ryuta Kamizono*
-
-*   Raise `ArgumentError` when passing string to define callback.
-
-    *Ryuta Kamizono*
-
-*   Updated Unicode version to 9.0.0
-
-    Now we can handle new emojis such like "👩‍👩‍👧‍👦" ("\u{1F469}\u{200D}\u{1F469}\u{200D}\u{1F467}\u{200D}\u{1F466}").
-
-    version 8.0.0
-
-        "👩‍👩‍👧‍👦".mb_chars.grapheme_length # => 4
-        "👩‍👩‍👧‍👦".mb_chars.reverse # => "👦👧‍👩‍👩‍"
-
-    version 9.0.0
-
-        "👩‍👩‍👧‍👦".mb_chars.grapheme_length # => 1
-        "👩‍👩‍👧‍👦".mb_chars.reverse # => "👩‍👩‍👧‍👦"
-
-    *Fumiaki MATSUSHIMA*
-
-*   Changed `ActiveSupport::Inflector#transliterate` to raise `ArgumentError` when it receives
-    anything except a string.
-
-    *Kevin McPhillips*
-
-*   Fixed bugs that `StringInquirer#respond_to_missing?` and
-    `ArrayInquirer#respond_to_missing?` do not fallback to `super`.
+*   `Hash#slice` now falls back to Ruby 2.5+'s built-in definition if defined.
 
     *Akira Matsuda*
 
-*   Fix inconsistent results when parsing large durations and constructing durations from code
-
-        ActiveSupport::Duration.parse('P3Y') == 3.years # It should be true
-
-    Duration parsing made independent from any moment of time:
-    Fixed length in seconds is assigned to each duration part during parsing.
-
-    Changed duration of months and years in seconds to more accurate and logical:
-
-     1. The value of 365.2425 days in Gregorian year is more accurate
-        as it accounts for every 400th non-leap year.
-
-     2. Month's length is bound to year's duration, which makes
-        sensible comparisons like `12.months == 1.year` to be `true`
-        and nonsensical ones like `30.days == 1.month` to be `false`.
-
-    Calculations on times and dates with durations shouldn't be affected as
-    duration's numeric value isn't used in calculations, only parts are used.
+*   Deprecate `secrets.secret_token`.
 
-    Methods on `Numeric` like `2.days` now use these predefined durations
-    to avoid duplication of duration constants through the codebase and
-    eliminate creation of intermediate durations.
+    The architecture for secrets had a big upgrade between Rails 3 and Rails 4,
+    when the default changed from using `secret_token` to `secret_key_base`.
 
-    *Andrey Novikov*, *Andrew White*
+    `secret_token` has been soft deprecated in documentation for four years
+    but is still in place to support apps created before Rails 4.
+    Deprecation warnings have been added to help developers upgrade their
+    applications to `secret_key_base`.
 
-*   Change return value of `Rational#duplicable?`, `ComplexClass#duplicable?`
-    to false.
+    *claudiob*, *Kasper Timm Hansen*
 
-    *utilum*
-
-*   Change return value of `NilClass#duplicable?`, `FalseClass#duplicable?`,
-    `TrueClass#duplicable?`, `Symbol#duplicable?` and `Numeric#duplicable?`
-    to true with Ruby 2.4+. These classes can dup with Ruby 2.4+.
+*   Return an instance of `HashWithIndifferentAccess` from `HashWithIndifferentAccess#transform_keys`.
 
     *Yuji Yaginuma*
 
-*   Remove deprecated class `ActiveSupport::Concurrency::Latch`.
+*   Add key rotation support to `MessageEncryptor` and `MessageVerifier`.
 
-    *Andrew White*
+    This change introduces a `rotate` method to both the `MessageEncryptor` and
+    `MessageVerifier` classes. This method accepts the same arguments and
+    options as the given classes' constructor. The `encrypt_and_verify` method
+    for `MessageEncryptor` and the `verified` method for `MessageVerifier` also
+    accept an optional keyword argument `:on_rotation` block which is called
+    when a rotated instance is used to decrypt or verify the message.
 
-*   Remove deprecated separator argument from `parameterize`.
+    *Michael J Coyne*
 
-    *Andrew White*
+*   Deprecate `Module#reachable?` method.
 
-*   Remove deprecated method `Numeric#to_formatted_s`.
+    *bogdanvlviv*
 
-    *Andrew White*
+*   Add `config/credentials.yml.enc` to store production app secrets.
 
-*   Remove deprecated method `alias_method_chain`.
+    Allows saving any authentication credentials for third party services
+    directly in repo encrypted with `config/master.key` or `ENV["RAILS_MASTER_KEY"]`.
 
-    *Andrew White*
+    This will eventually replace `Rails.application.secrets` and the encrypted
+    secrets introduced in Rails 5.1.
 
-*   Remove deprecated constant `MissingSourceFile`.
+    *DHH*, *Kasper Timm Hansen*
 
-    *Andrew White*
+*   Add `ActiveSupport::EncryptedFile` and `ActiveSupport::EncryptedConfiguration`.
 
-*   Remove deprecated methods `Module.qualified_const_defined?`,
-    `Module.qualified_const_get` and `Module.qualified_const_set`.
+    Allows for stashing encrypted files or configuration directly in repo by
+    encrypting it with a key.
 
-    *Andrew White*
+    Backs the new credentials setup above, but can also be used independently.
 
-*   Remove deprecated `:prefix` option from `number_to_human_size`.
+    *DHH*, *Kasper Timm Hansen*
 
-    *Andrew White*
+*   `Module#delegate_missing_to` now raises `DelegationError` if target is nil,
+    similar to `Module#delegate`.
 
-*   Remove deprecated method `ActiveSupport::HashWithIndifferentAccess.new_from_hash_copying_default`.
+    *Anton Khamets*
 
-    *Andrew White*
+*   Update `String#camelize` to provide feedback when wrong option is passed.
 
-*   Remove deprecated file `active_support/core_ext/time/marshal.rb`.
+    `String#camelize` was returning nil without any feedback when an
+    invalid option was passed as a parameter.
 
-    *Andrew White*
-
-*   Remove deprecated file `active_support/core_ext/struct.rb`.
-
-    *Andrew White*
-
-*   Remove deprecated file `active_support/core_ext/module/method_transplanting.rb`.
-
-    *Andrew White*
-
-*   Remove deprecated method `Module.local_constants`.
-
-    *Andrew White*
+    Previously:
 
-*   Remove deprecated file `active_support/core_ext/kernel/debugger.rb`.
+        'one_two'.camelize(true)
+        # => nil
 
-    *Andrew White*
+    Now:
 
-*   Remove deprecated method `ActiveSupport::Cache::Store#namespaced_key`.
+        'one_two'.camelize(true)
+        # => ArgumentError: Invalid option, use either :upper or :lower.
 
-    *Andrew White*
+    *Ricardo Díaz*
 
-*   Remove deprecated method `ActiveSupport::Cache::Strategy::LocalCache::LocalStore#set_cache_value`.
+*   Fix modulo operations involving durations.
 
-    *Andrew White*
+    Rails 5.1 introduced `ActiveSupport::Duration::Scalar` as a wrapper
+    around numeric values as a way of ensuring a duration was the outcome of
+    an expression. However, the implementation was missing support for modulo
+    operations. This support has now been added and should result in a duration
+    being returned from expressions involving modulo operations.
 
-*   Remove deprecated method `ActiveSupport::Cache::MemCacheStore#escape_key`.
+    Prior to Rails 5.1:
 
-    *Andrew White*
+        5.minutes % 2.minutes
+        # => 60
 
-*   Remove deprecated method `ActiveSupport::Cache::FileStore#key_file_path`.
+    Now:
 
-    *Andrew White*
+        5.minutes % 2.minutes
+        # => 1 minute
 
-*   Ensure duration parsing is consistent across DST changes.
+    Fixes #29603 and #29743.
 
-    Previously `ActiveSupport::Duration.parse` used `Time.current` and
-    `Time#advance` to calculate the number of seconds in the duration
-    from an arbitrary collection of parts. However as `advance` tries to
-    be consistent across DST boundaries this meant that either the
-    duration was shorter or longer depending on the time of year.
+    *Sayan Chakraborty*, *Andrew White*
 
-    This was fixed by using an absolute reference point in UTC which
-    isn't subject to DST transitions. An arbitrary date of Jan 1st, 2000
-    was chosen for no other reason that it seemed appropriate.
+*   Fix division where a duration is the denominator.
 
-    Additionally, duration parsing should now be marginally faster as we
-    are no longer creating instances of `ActiveSupport::TimeWithZone`
-    every time we parse a duration string.
+    PR #29163 introduced a change in behavior when a duration was the denominator
+    in a calculation - this was incorrect as dividing by a duration should always
+    return a `Numeric`. The behavior of previous versions of Rails has been restored.
 
-    Fixes #26941.
+    Fixes #29592.
 
     *Andrew White*
 
-*   Use `Hash#compact` and `Hash#compact!` from Ruby 2.4. Old Ruby versions
-    will continue to get these methods from Active Support as before.
-
-    *Prathamesh Sonpatki*
-
-*   Fix `ActiveSupport::TimeZone#strptime`.
-    Support for timestamps in format of seconds (%s) and milliseconds (%Q).
-
-    Fixes #26840.
-
-    *Lev Denisov*
-
-*   Fix `DateAndTime::Calculations#copy_time_to`. Copy `nsec` instead of `usec`.
-
-    Jumping forward or backward between weeks now preserves nanosecond digits.
-
-    *Josua Schmid*
-
-*   Fix `ActiveSupport::TimeWithZone#in` across DST boundaries.
-
-    Previously calls to `in` were being sent to the non-DST aware
-    method `Time#since` via `method_missing`. It is now aliased to
-    the DST aware `ActiveSupport::TimeWithZone#+` which handles
-    transitions across DST boundaries, e.g:
-
-        Time.zone = "US/Eastern"
-
-        t = Time.zone.local(2016,11,6,1)
-        # => Sun, 06 Nov 2016 01:00:00 EDT -05:00
-
-        t.in(1.hour)
-        # => Sun, 06 Nov 2016 01:00:00 EST -05:00
-
-    Fixes #26580.
-
-    *Thomas Balthazar*
-
-*   Remove unused parameter `options = nil` for `#clear` of
-    `ActiveSupport::Cache::Strategy::LocalCache::LocalStore` and
-    `ActiveSupport::Cache::Strategy::LocalCache`.
-
-    *Yosuke Kabuto*
-
-*   Fix `thread_mattr_accessor` subclass no longer overwrites parent.
-
-    Assigning a value to a subclass using `thread_mattr_accessor` no
-    longer changes the value of the parent class. This brings the
-    behavior inline with the documentation.
+*   Add purpose and expiry support to `ActiveSupport::MessageVerifier` and
+   `ActiveSupport::MessageEncryptor`.
 
-    Given:
+    For instance, to ensure a message is only usable for one intended purpose:
 
-        class Account
-          thread_mattr_accessor :user
-        end
+        token = @verifier.generate("x", purpose: :shipping)
 
-        class Customer < Account
-        end
+        @verifier.verified(token, purpose: :shipping) # => "x"
+        @verifier.verified(token)                     # => nil
 
-        Account.user = "DHH"
-        Customer.user = "Rafael"
+    Or make it expire after a set time:
 
-    Before:
-
-        Account.user  # => "Rafael"
+        @verifier.generate("x", expires_in: 1.month)
+        @verifier.generate("y", expires_at: Time.now.end_of_year)
 
-    After:
+    Showcased with `ActiveSupport::MessageVerifier`, but works the same for
+    `ActiveSupport::MessageEncryptor`'s `encrypt_and_sign` and `decrypt_and_verify`.
 
-        Account.user  # => "DHH"
+    Pull requests: #29599, #29854
 
-    *Shinichi Maeshima*
+    *Assain Jaleel*
 
-*   Since weeks are no longer converted to days, add `:weeks` to the list of
-    parts that `ActiveSupport::TimeWithZone` will recognize as possibly being
-    of variable duration to take account of DST transitions.
+*   Make the order of `Hash#reverse_merge!` consistent with `HashWithIndifferentAccess`.
 
-    Fixes #26039.
+    *Erol Fornoles*
 
-    *Andrew White*
+*   Add `freeze_time` helper which freezes time to `Time.now` in tests.
 
-*   Defines `Regexp.match?` for Ruby versions prior to 2.4. The predicate
-    has the same interface, but it does not have the performance boost. Its
-    purpose is to be able to write 2.4 compatible code.
-
-    *Xavier Noria*
-
-*   Allow `MessageEncryptor` to take advantage of authenticated encryption modes.
+    *Prathamesh Sonpatki*
 
-    AEAD modes like `aes-256-gcm` provide both confidentiality and data
-    authenticity, eliminating the need to use `MessageVerifier` to check if the
-    encrypted data has been tampered with. This speeds up encryption/decryption
-    and results in shorter cipher text.
+*   Default `ActiveSupport::MessageEncryptor` to use AES 256 GCM encryption.
 
-    *Bart de Water*
+    On for new Rails 5.2 apps. Upgrading apps can find the config as a new
+    framework default.
 
-*   Introduce `assert_changes` and `assert_no_changes`.
+    *Assain Jaleel*
 
-    `assert_changes` is a more general `assert_difference` that works with any
-    value.
+*   Cache: `write_multi`.
 
-        assert_changes 'Error.current', from: nil, to: 'ERR' do
-          expected_bad_operation
-        end
+        Rails.cache.write_multi foo: 'bar', baz: 'qux'
 
-    Can be called with strings, to be evaluated in the binding (context) of
-    the block given to the assertion, or a lambda.
+    Plus faster fetch_multi with stores that implement `write_multi_entries`.
+    Keys that aren't found may be written to the cache store in one shot
+    instead of separate writes.
 
-        assert_changes -> { Error.current }, from: nil, to: 'ERR' do
-          expected_bad_operation
-        end
+    The default implementation simply calls `write_entry` for each entry.
+    Stores may override if they're capable of one-shot bulk writes, like
+    Redis `MSET`.
 
-    The `from` and `to` arguments are compared with the case operator (`===`).
+    *Jeremy Daer*
 
-        assert_changes 'Error.current', from: nil, to: Error do
-          expected_bad_operation
-        end
+*   Add default option to module and class attribute accessors.
 
-    This is pretty useful, if you need to loosely compare a value. For example,
-    you need to test a token has been generated and it has that many random
-    characters.
+        mattr_accessor :settings, default: {}
 
-        user = User.start_registration
-        assert_changes 'user.token', to: /\w{32}/ do
-          user.finish_registration
-        end
+    Works for `mattr_reader`, `mattr_writer`, `cattr_accessor`, `cattr_reader`,
+    and `cattr_writer` as well.
 
     *Genadi Samokovarov*
 
-*   Fix `ActiveSupport::TimeZone#strptime`. Now raises `ArgumentError` when the
-    given time doesn't match the format. The error is the same as the one given
-    by Ruby's `Date.strptime`. Previously it raised
-    `NoMethodError: undefined method empty? for nil:NilClass.` due to a bug.
+*   Add `Date#prev_occurring` and `Date#next_occurring` to return specified next/previous occurring day of week.
 
-    Fixes #25701.
+    *Shota Iguchi*
 
-    *John Gesimondo*
+*   Add default option to `class_attribute`.
 
-*   `travel/travel_to` travel time helpers, now raise on nested calls,
-    as this can lead to confusing time stubbing.
+    Before:
 
-    Instead of:
+        class_attribute :settings
+        self.settings = {}
 
-        travel_to 2.days.from_now do
-          # 2 days from today
-          travel_to 3.days.from_now do
-            # 5 days from today
-          end
-        end
+    Now:
 
-    preferred way to achieve above is:
+        class_attribute :settings, default: {}
 
-        travel 2.days do
-          # 2 days from today
-        end
+    *DHH*
 
-        travel 5.days do
-          # 5 days from today
-        end
+*   `#singularize` and `#pluralize` now respect uncountables for the specified locale.
 
-    *Vipul A M*
+    *Eilis Hamilton*
 
-*   Support parsing JSON time in ISO8601 local time strings in
-    `ActiveSupport::JSON.decode` when `parse_json_times` is enabled.
-    Strings in the format of `YYYY-MM-DD hh:mm:ss` (without a `Z` at
-    the end) will be parsed in the local timezone (`Time.zone`). In
-    addition, date strings (`YYYY-MM-DD`) are now parsed into `Date`
-    objects.
+*   Add `ActiveSupport::CurrentAttributes` to provide a thread-isolated attributes singleton.
+    Primary use case is keeping all the per-request attributes easily available to the whole system.
 
-    *Grzegorz Witek*
+    *DHH*
 
-*   Fixed `ActiveSupport::Logger.broadcast` so that calls to `#silence` now
-    properly delegate to all loggers. Silencing now properly suppresses logging
-    to both the log and the console.
+*   Fix implicit coercion calculations with scalars and durations.
 
-    *Kevin McPhillips*
+    Previously, calculations where the scalar is first would be converted to a duration
+    of seconds, but this causes issues with dates being converted to times, e.g:
 
-*   Remove deprecated arguments in `assert_nothing_raised`.
+        Time.zone = "Beijing"           # => Asia/Shanghai
+        date = Date.civil(2017, 5, 20)  # => Mon, 20 May 2017
+        2 * 1.day                       # => 172800 seconds
+        date + 2 * 1.day                # => Mon, 22 May 2017 00:00:00 CST +08:00
 
-    *Rafel Mendonça França*
+    Now, the `ActiveSupport::Duration::Scalar` calculation methods will try to maintain
+    the part structure of the duration where possible, e.g:
 
-*   `Date.to_s` doesn't produce too many spaces. For example, `to_s(:short)`
-    will now produce `01 Feb` instead of ` 1 Feb`.
+        Time.zone = "Beijing"           # => Asia/Shanghai
+        date = Date.civil(2017, 5, 20)  # => Mon, 20 May 2017
+        2 * 1.day                       # => 2 days
+        date + 2 * 1.day                # => Mon, 22 May 2017
 
-    Fixes #25251.
+    Fixes #29160, #28970.
 
-    *Sean Griffin*
+    *Andrew White*
 
-*   Introduce `Module#delegate_missing_to`.
+*   Add support for versioned cache entries. This enables the cache stores to recycle cache keys, greatly saving
+    on storage in cases with frequent churn. Works together with the separation of `#cache_key` and `#cache_version`
+    in Active Record and its use in Action Pack's fragment caching.
 
-    When building a decorator, a common pattern emerges:
+    *DHH*
 
-        class Partition
-          def initialize(first_event)
-            @events = [ first_event ]
-          end
+*   Pass gem name and deprecation horizon to deprecation notifications.
 
-          def people
-            if @events.first.detail.people.any?
-              @events.collect { |e| Array(e.detail.people) }.flatten.uniq
-            else
-              @events.collect(&:creator).uniq
-            end
-          end
+    *Willem van Bergen*
 
-          private
-            def respond_to_missing?(name, include_private = false)
-              @events.respond_to?(name, include_private)
-            end
+*   Add support for `:offset` and `:zone` to `ActiveSupport::TimeWithZone#change`.
 
-            def method_missing(method, *args, &block)
-              @events.send(method, *args, &block)
-            end
-        end
+    *Andrew White*
 
-    With `Module#delegate_missing_to`, the above is condensed to:
+*   Add support for `:offset` to `Time#change`.
 
-        class Partition
-          delegate_missing_to :@events
+    Fixes #28723.
 
-          def initialize(first_event)
-            @events = [ first_event ]
-          end
+    *Andrew White*
 
-          def people
-            if @events.first.detail.people.any?
-              @events.collect { |e| Array(e.detail.people) }.flatten.uniq
-            else
-              @events.collect(&:creator).uniq
-            end
-          end
-        end
+*   Add `fetch_values` for `HashWithIndifferentAccess`.
 
-    *Genadi Samokovarov*, *DHH*
+    The method was originally added to `Hash` in Ruby 2.3.0.
 
-*   Rescuable: If a handler doesn't match the exception, check for handlers
-    matching the exception's cause.
+    *Josh Pencheon*
 
-    *Jeremy Daer*
 
-Please check [5-0-stable](https://github.com/rails/rails/blob/5-0-stable/activesupport/CHANGELOG.md) for previous changes.
+Please check [5-1-stable](https://github.com/rails/rails/blob/5-1-stable/activesupport/CHANGELOG.md) for previous changes.