actionpack 6.0.5.1 → 6.1.0

data/CHANGELOG.md

@@ -1,166 +1,182 @@
-## Rails 6.0.5.1 (July 12, 2022) ##
+## Rails 6.1.0 (December 09, 2020) ##
 
-*   No changes.
+*   Support for the HTTP header `Feature-Policy` has been revised to reflect
+    its [rename](https://github.com/w3c/webappsec-permissions-policy/pull/379) to [`Permissions-Policy`](https://w3c.github.io/webappsec-permissions-policy/#permissions-policy-http-header-field).
 
+    ```ruby
+    Rails.application.config.permissions_policy do |p|
+      p.camera     :none
+      p.gyroscope  :none
+      p.microphone :none
+      p.usb        :none
+      p.fullscreen :self
+      p.payment    :self, "https://secure-example.com"
+    end
+    ```
 
-## Rails 6.0.5 (May 09, 2022) ##
-
-*   No changes.
-
-
-## Rails 6.0.4.8 (April 26, 2022) ##
-
-*   Allow Content Security Policy DSL to generate for API responses.
-
-    *Tim Wade*
-
-## Rails 6.0.4.7 (March 08, 2022) ##
-
-*   No changes.
-
-
-## Rails 6.0.4.6 (February 11, 2022) ##
-
-*   No changes.
+    *Julien Grillot*
 
+*   Allow `ActionDispatch::HostAuthorization` to exclude specific requests.
 
-## Rails 6.0.4.5 (February 11, 2022) ##
+    Host Authorization checks can be skipped for specific requests. This allows for health check requests to be permitted for requests with missing or non-matching host headers.
 
-*   Under certain circumstances, the middleware isn't informed that the
-    response body has been fully closed which result in request state not
-    being fully reset before the next request
+    *Chris Bisnett*
 
-    [CVE-2022-23633]
+*   Add `config.action_dispatch.request_id_header` to allow changing the name of
+    the unique X-Request-Id header
 
+    *Arlston Fernandes*
 
-## Rails 6.0.4.4 (December 15, 2021) ##
+*   Deprecate `config.action_dispatch.return_only_media_type_on_content_type`.
 
-*   Fix issue with host protection not allowing host with port in development.
+    *Rafael Mendonça França*
 
+*   Change `ActionDispatch::Response#content_type` to return the full Content-Type header.
 
-## Rails 6.0.4.3 (December 14, 2021) ##
+    *Rafael Mendonça França*
 
-*   Fix issue with host protection not allowing localhost in development.
+*   Remove deprecated `ActionDispatch::Http::ParameterFilter`.
 
+    *Rafael Mendonça França*
 
-## Rails 6.0.4.2 (December 14, 2021) ##
+*   Added support for exclusive no-store Cache-Control header.
 
-*   Fix X_FORWARDED_HOST protection.  [CVE-2021-44528]
+    If `no-store` is set on Cache-Control header it is exclusive (all other cache directives are dropped).
 
-## Rails 6.1.4.1 (August 19, 2021) ##
+    *Chris Kruger*
 
-*   [CVE-2021-22942] Fix possible open redirect in Host Authorization middleware.
+*   Catch invalid UTF-8 parameters for POST requests and respond with BadRequest.
 
-    Specially crafted "X-Forwarded-Host" headers in combination with certain
-    "allowed host" formats can cause the Host Authorization middleware in Action
-    Pack to redirect users to a malicious website.
+    Additionally, perform `#set_binary_encoding` in `ActionDispatch::Http::Request#GET` and
+    `ActionDispatch::Http::Request#POST` prior to validating encoding.
 
-## Rails 6.0.4 (June 15, 2021) ##
+    *Adrianna Chang*
 
-*   Accept base64_urlsafe CSRF tokens to make forward compatible.
+*   Allow `assert_recognizes` routing assertions to work on mounted root routes.
 
-    Base64 strict-encoded CSRF tokens are not inherently websafe, which makes
-    them difficult to deal with. For example, the common practice of sending
-    the CSRF token to a browser in a client-readable cookie does not work properly
-    out of the box: the value has to be url-encoded and decoded to survive transport.
+    *Gannon McGibbon*
 
-    In Rails 6.1, we generate Base64 urlsafe-encoded CSRF tokens, which are inherently
-    safe to transport. Validation accepts both urlsafe tokens, and strict-encoded
-    tokens for backwards compatibility.
+*   Change default redirection status code for non-GET/HEAD requests to 308 Permanent Redirect for `ActionDispatch::SSL`.
 
-    In Rails 5.2.5, the CSRF token format is accidentally changed to urlsafe-encoded.
-    If you upgrade apps from 5.2.5, set the config `urlsafe_csrf_tokens = true`.
+    *Alan Tan*, *Oz Ben-David*
 
-    ```ruby
-    Rails.application.config.action_controller.urlsafe_csrf_tokens = true
-    ```
+*   Fix `follow_redirect!` to follow redirection with same HTTP verb when following
+    a 308 redirection.
 
-    *Scott Blum*, *Étienne Barrié*
+    *Alan Tan*
 
-*   Signed and encrypted cookies can now store `false` as their value when
-    `action_dispatch.use_cookies_with_metadata` is enabled.
+*   When multiple domains are specified for a cookie, a domain will now be
+    chosen only if it is equal to or is a superdomain of the request host.
 
-    *Rolandas Barysas*
+    *Jonathan Hefner*
 
+*   `ActionDispatch::Static` handles precompiled Brotli (.br) files.
 
-## Rails 6.0.3.7 (May 05, 2021) ##
+    Adds to existing support for precompiled gzip (.gz) files.
+    Brotli files are preferred due to much better compression.
 
-*   Prevent catastrophic backtracking during mime parsing
-    CVE-2021-22902
+    When the browser requests /some.js with `Accept-Encoding: br`,
+    we check for public/some.js.br and serve that file, if present, with
+    `Content-Encoding: br` and `Vary: Accept-Encoding` headers.
 
-*   Prevent regex DoS in HTTP token authentication
-    CVE-2021-22904
+    *Ryan Edward Hall*, *Jeremy Daer*
 
-*   Prevent string polymorphic route arguments.
+*   Add raise_on_missing_translations support for controllers.
 
-    `url_for` supports building polymorphic URLs via an array
-    of arguments (usually symbols and records). If a developer passes a
-    user input array, strings can result in unwanted route helper calls.
+    This configuration determines whether an error should be raised for missing translations.
+    It can be enabled through `config.i18n.raise_on_missing_translations`. Note that described
+    configuration also affects raising error for missing translations in views.
 
-    CVE-2021-22885
+    *fatkodima*
 
-    *Gannon McGibbon*
+*   Added `compact` and `compact!` to `ActionController::Parameters`.
 
-## Rails 6.0.3.6 (March 26, 2021) ##
-
-*   No changes.
+    *Eugene Kenny*
 
+*   Calling `each_pair` or `each_value` on an `ActionController::Parameters`
+    without passing a block now returns an enumerator.
 
-## Rails 6.0.3.5 (February 10, 2021) ##
+    *Eugene Kenny*
 
-*   Prevent open redirect when allowed host starts with a dot
+*   `fixture_file_upload` now uses path relative to `file_fixture_path`
 
-    [CVE-2021-22881]
+    Previously the path had to be relative to `fixture_path`.
+    You can change your existing code as follow:
 
-    Thanks to @tktech (https://hackerone.com/tktech) for reporting this
-    issue and the patch!
+    ```ruby
+    # Before
+    fixture_file_upload('files/dog.png')
 
-    *Aaron Patterson*
+    # After
+    fixture_file_upload('dog.png')
+    ```
 
+    *Edouard Chin*
 
-## Rails 6.0.3.4 (October 07, 2020) ##
+*   Remove deprecated `force_ssl` at the controller level.
 
-*   [CVE-2020-8264] Prevent XSS in Actionable Exceptions
+    *Rafael Mendonça França*
 
+*   The +helper+ class method for controllers loads helper modules specified as
+    strings/symbols with `String#constantize` instead of `require_dependency`.
 
-## Rails 6.0.3.3 (September 09, 2020) ##
+    Remember that support for strings/symbols is only a convenient API. You can
+    always pass a module object:
 
-*   No changes.
+    ```ruby
+    helper UtilsHelper
+    ```
 
+    which is recommended because it is simple and direct. When a string/symbol
+    is received, `helper` just manipulates and inflects the argument to obtain
+    that same module object.
 
-## Rails 6.0.3.2 (June 17, 2020) ##
+    *Xavier Noria*, *Jean Boussier*
 
-*   [CVE-2020-8185] Only allow ActionableErrors if show_detailed_exceptions is enabled
+*   Correctly identify the entire localhost IPv4 range as trusted proxy.
 
-## Rails 6.0.3.1 (May 18, 2020) ##
+    *Nick Soracco*
 
-*   [CVE-2020-8166] HMAC raw CSRF token before masking it, so it cannot be used to reconstruct a per-form token
+*   `url_for` will now use "https://" as the default protocol when
+    `Rails.application.config.force_ssl` is set to true.
 
-*   [CVE-2020-8164] Return self when calling #each, #each_pair, and #each_value instead of the raw @parameters hash
+    *Jonathan Hefner*
 
+*   Accept and default to base64_urlsafe CSRF tokens.
 
-## Rails 6.0.3 (May 06, 2020) ##
+    Base64 strict-encoded CSRF tokens are not inherently websafe, which makes
+    them difficult to deal with. For example, the common practice of sending
+    the CSRF token to a browser in a client-readable cookie does not work properly
+    out of the box: the value has to be url-encoded and decoded to survive transport.
 
-*   Include child session assertion count in ActionDispatch::IntegrationTest
+    Now, we generate Base64 urlsafe-encoded CSRF tokens, which are inherently safe
+    to transport. Validation accepts both urlsafe tokens, and strict-encoded tokens
+    for backwards compatibility.
 
-    `IntegrationTest#open_session` uses `dup` to create the new session, which
-    meant it had its own copy of `@assertions`. This prevented the assertions
-    from being correctly counted and reported.
+    *Scott Blum*
 
-    Child sessions now have their `attr_accessor` overriden to delegate to the
-    root session.
+*   Support rolling deploys for cookie serialization/encryption changes.
 
-    Fixes #32142
+    In a distributed configuration like rolling update, users may observe
+    both old and new instances during deployment. Users may be served by a
+    new instance and then by an old instance.
 
-    *Sam Bostock*
+    That means when the server changes `cookies_serializer` from `:marshal`
+    to `:hybrid` or the server changes `use_authenticated_cookie_encryption`
+    from `false` to `true`, users may lose their sessions if they access the
+    server during deployment.
 
+    We added fallbacks to downgrade the cookie format when necessary during
+    deployment, ensuring compatibility on both old and new instances.
 
-## Rails 6.0.2.2 (March 19, 2020) ##
+    *Masaki Hara*
 
-*   No changes.
+*   `ActionDispatch::Request.remote_ip` has ip address even when all sites are trusted.
 
+    Before, if all `X-Forwarded-For` sites were trusted, the `remote_ip` would default to `127.0.0.1`.
+    Now, the furthest proxy site is used. e.g.: It now gives an ip address when using curl from the load balancer.
 
-## Rails 6.0.2.1 (December 18, 2019) ##
+    *Keenan Brock*
 
 *   Fix possible information leak / session hijacking vulnerability.
 
@@ -169,339 +185,227 @@
 
     CVE-2019-16782.
 
+*   Include child session assertion count in ActionDispatch::IntegrationTest.
 
-## Rails 6.0.2 (December 13, 2019) ##
+    `IntegrationTest#open_session` uses `dup` to create the new session, which
+    meant it had its own copy of `@assertions`. This prevented the assertions
+    from being correctly counted and reported.
 
-*   Allow using mountable engine route helpers in System Tests.
+    Child sessions now have their `attr_accessor` overridden to delegate to the
+    root session.
 
-    *Chalo Fernandez*
+    Fixes #32142.
 
+    *Sam Bostock*
 
-## Rails 6.0.1 (November 5, 2019) ##
+*   Add SameSite protection to every written cookie.
 
-*   `ActionDispatch::SystemTestCase` now inherits from `ActiveSupport::TestCase`
-    rather than `ActionDispatch::IntegrationTest`. This permits running jobs in
-    system tests.
+    Enabling `SameSite` cookie protection is an addition to CSRF protection,
+    where cookies won't be sent by browsers in cross-site POST requests when set to `:lax`.
 
-    *George Claghorn*, *Edouard Chin*
+    `:strict` disables cookies being sent in cross-site GET or POST requests.
 
-*   Registered MIME types may contain extra flags:
+    Passing `:none` disables this protection and is the same as previous versions albeit a `; SameSite=None` is appended to the cookie.
 
-    ```ruby
-    Mime::Type.register "text/html; fragment", :html_fragment
-    ```
+    See upgrade instructions in config/initializers/new_framework_defaults_6_1.rb.
 
-    *Aaron Patterson*
+    More info [here](https://tools.ietf.org/html/draft-west-first-party-cookies-07)
 
+    _NB: Technically already possible as Rack supports SameSite protection, this is to ensure it's applied to all cookies_
 
-## Rails 6.0.0 (August 16, 2019) ##
+    *Cédric Fabianski*
 
-*   No changes.
+*   Bring back the feature that allows loading external route files from the router.
 
+    This feature existed back in 2012 but got reverted with the incentive that
+    https://github.com/rails/routing_concerns was a better approach. Turned out
+    that this wasn't fully the case and loading external route files from the router
+    can be helpful for applications with a really large set of routes.
+    Without this feature, application needs to implement routes reloading
+    themselves and it's not straightforward.
 
-## Rails 6.0.0.rc2 (July 22, 2019) ##
+    ```ruby
+    # config/routes.rb
 
-*   Add the ability to set the CSP nonce only to the specified directives.
+    Rails.application.routes.draw do
+      draw(:admin)
+    end
 
-    Fixes #35137.
+    # config/routes/admin.rb
 
-    *Yuji Yaginuma*
+    get :foo, to: 'foo#bar'
+    ```
 
-*   Keep part when scope option has value.
+    *Yehuda Katz*, *Edouard Chin*
 
-    When a route was defined within an optional scope, if that route didn't
-    take parameters the scope was lost when using path helpers. This commit
-    ensures scope is kept both when the route takes parameters or when it
-    doesn't.
+*   Fix system test driver option initialization for non-headless browsers.
 
-    Fixes #33219
+    *glaszig*
 
-    *Alberto Almagro*
+*   `redirect_to.action_controller` notifications now include the `ActionDispatch::Request` in
+    their payloads as `:request`.
 
-*   Change `ActionDispatch::Response#content_type` to return Content-Type header as it is.
+    *Austin Story*
 
-    Previously, `ActionDispatch::Response#content_type` returned value does NOT
-    contain charset part. This behavior changed to returned Content-Type header
-    containing charset part as it is.
+*   `respond_to#any` no longer returns a response's Content-Type based on the
+    request format but based on the block given.
 
-    If you want just MIME type, please use `ActionDispatch::Response#media_type`
-    instead.
+    Example:
 
-    Enable `action_dispatch.return_only_media_type_on_content_type` to use this change.
-    If not enabled, `ActionDispatch::Response#content_type` returns the same
-    value as before version, but its behavior is deprecate.
+    ```ruby
+      def my_action
+        respond_to do |format|
+          format.any { render(json: { foo: 'bar' }) }
+        end
+      end
 
-    *Yuji Yaginuma*
+      get('my_action.csv')
+    ```
 
-*   Calling `ActionController::Parameters#transform_keys/!` without a block now returns
-    an enumerator for the parameters instead of the underlying hash.
+    The previous behaviour was to respond with a `text/csv` Content-Type which
+    is inaccurate since a JSON response is being rendered.
 
-    *Eugene Kenny*
+    Now it correctly returns a `application/json` Content-Type.
 
-*   Fix a bug where DebugExceptions throws an error when malformed query parameters are provided
+    *Edouard Chin*
 
-    *Yuki Nishijima*, *Stan Lo*
+*   Replaces (back)slashes in failure screenshot image paths with dashes.
 
+    If a failed test case contained a slash or a backslash, a screenshot would be created in a
+    nested directory, causing issues with `tmp:clear`.
 
-## Rails 6.0.0.rc1 (April 24, 2019) ##
+    *Damir Zekic*
 
-*   Make system tests take a failed screenshot in a `before_teardown` hook
-    rather than an `after_teardown` hook.
+*   Add `params.member?` to mimic Hash behavior.
 
-    This helps minimize the time gap between when an assertion fails and when
-    the screenshot is taken (reducing the time in which the page could have
-    been dynamically updated after the assertion failed).
+    *Younes Serraj*
 
-    *Richard Macklin*
+*   `process_action.action_controller` notifications now include the following in their payloads:
 
-*   Introduce `ActionDispatch::ActionableExceptions`.
+    * `:request` - the `ActionDispatch::Request`
+    * `:response` - the `ActionDispatch::Response`
 
-    The `ActionDispatch::ActionableExceptions` middleware dispatches actions
-    from `ActiveSupport::ActionableError` descendants.
+    *George Claghorn*
 
-    Actionable errors let's you dispatch actions from Rails' error pages.
+*   Updated `ActionDispatch::Request.remote_ip` setter to clear set the instance
+    `remote_ip` to `nil` before setting the header that the value is derived
+    from.
 
-    *Vipul A M*, *Yao Jie*, *Genadi Samokovarov*
+    Fixes #37383.
 
-*   Raise an `ArgumentError` if a resource custom param contains a colon (`:`).
+    *Norm Provost*
 
-    After this change it's not possible anymore to configure routes like this:
+*   `ActionController::Base.log_at` allows setting a different log level per request.
 
-    ```
-    routes.draw do
-      resources :users, param: 'name/:sneaky'
+    ```ruby
+    # Use the debug level if a particular cookie is set.
+    class ApplicationController < ActionController::Base
+      log_at :debug, if: -> { cookies[:debug] }
     end
     ```
 
-    Fixes #30467.
+    *George Claghorn*
 
-    *Josua Schmid*
+*   Allow system test screen shots to be taken more than once in
+    a test by prefixing the file name with an incrementing counter.
 
+    Add an environment variable `RAILS_SYSTEM_TESTING_SCREENSHOT_HTML` to
+    enable saving of HTML during a screenshot in addition to the image.
+    This uses the same image name, with the extension replaced with `.html`
 
-## Rails 6.0.0.beta3 (March 11, 2019) ##
+    *Tom Fakes*
 
-*   No changes.
+*   Add `Vary: Accept` header when using `Accept` header for response.
 
+    For some requests like `/users/1`, Rails uses requests' `Accept`
+    header to determine what to return. And if we don't add `Vary`
+    in the response header, browsers might accidentally cache different
+    types of content, which would cause issues: e.g. javascript got displayed
+    instead of html content. This PR fixes these issues by adding `Vary: Accept`
+    in these types of requests. For more detailed problem description, please read:
 
-## Rails 6.0.0.beta2 (February 25, 2019) ##
+    https://github.com/rails/rails/pull/36213
 
-*   Make debug exceptions works in an environment where ActiveStorage is not loaded.
+    Fixes #25842.
 
-    *Tomoyuki Kurosawa*
+    *Stan Lo*
 
-*   `ActionDispatch::SystemTestCase.driven_by` can now be called with a block
-    to define specific browser capabilities.
+*   Fix IntegrationTest `follow_redirect!` to follow redirection using the same HTTP verb when following
+    a 307 redirection.
 
     *Edouard Chin*
 
+*   System tests require Capybara 3.26 or newer.
 
-## Rails 6.0.0.beta1 (January 18, 2019) ##
-
-*   Remove deprecated `fragment_cache_key` helper in favor of `combined_fragment_cache_key`.
-
-    *Rafael Mendonça França*
-
-*   Remove deprecated methods in `ActionDispatch::TestResponse`.
-
-    `#success?`, `missing?` and `error?` were deprecated in Rails 5.2 in favor of
-    `#successful?`, `not_found?` and `server_error?`.
+    *George Claghorn*
 
-    *Rafael Mendonça França*
+*   Reduced log noise handling ActionController::RoutingErrors.
 
-*   Introduce `ActionDispatch::HostAuthorization`.
+    *Alberto Fernández-Capel*
 
-    This is a new middleware that guards against DNS rebinding attacks by
-    explicitly permitting the hosts a request can be made to.
+*   Add DSL for configuring HTTP Feature Policy.
 
-    Each host is checked with the case operator (`#===`) to support `Regexp`,
-    `Proc`, `IPAddr` and custom objects as host allowances.
+    This new DSL provides a way to configure an HTTP Feature Policy at a
+    global or per-controller level. Full details of HTTP Feature Policy
+    specification and guidelines can be found at MDN:
 
-    *Genadi Samokovarov*
+    https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Feature-Policy
 
-*   Allow using `parsed_body` in `ActionController::TestCase`.
+    Example global policy:
 
-    In addition to `ActionDispatch::IntegrationTest`, allow using
-    `parsed_body` in `ActionController::TestCase`:
-
-    ```
-    class SomeControllerTest < ActionController::TestCase
-      def test_some_action
-        post :action, body: { foo: 'bar' }
-        assert_equal({ "foo" => "bar" }, response.parsed_body)
-      end
+    ```ruby
+    Rails.application.config.feature_policy do |f|
+      f.camera      :none
+      f.gyroscope   :none
+      f.microphone  :none
+      f.usb         :none
+      f.fullscreen  :self
+      f.payment     :self, "https://secure.example.com"
     end
     ```
 
-    Fixes #34676.
-
-    *Tobias Bühlmann*
-
-*   Raise an error on root route naming conflicts.
-
-    Raises an `ArgumentError` when multiple root routes are defined in the
-    same context instead of assigning nil names to subsequent roots.
+    Example controller level policy:
 
-    *Gannon McGibbon*
-
-*   Allow rescue from parameter parse errors:
-
-    ```
-    rescue_from ActionDispatch::Http::Parameters::ParseError do
-      head :unauthorized
+    ```ruby
+    class PagesController < ApplicationController
+      feature_policy do |p|
+        p.geolocation "https://example.com"
+      end
     end
     ```
 
-    *Gannon McGibbon*, *Josh Cheek*
-
-*   Reset Capybara sessions if failed system test screenshot raising an exception.
-
-    Reset Capybara sessions if `take_failed_screenshot` raise exception
-    in system test `after_teardown`.
-
-    *Maxim Perepelitsa*
-
-*   Use request object for context if there's no controller
-
-    There is no controller instance when using a redirect route or a
-    mounted rack application so pass the request object as the context
-    when resolving dynamic CSP sources in this scenario.
-
-    Fixes #34200.
-
-    *Andrew White*
-
-*   Apply mapping to symbols returned from dynamic CSP sources
-
-    Previously if a dynamic source returned a symbol such as :self it
-    would be converted to a string implicitly, e.g:
-
-        policy.default_src -> { :self }
-
-    would generate the header:
-
-        Content-Security-Policy: default-src self
-
-    and now it generates:
-
-        Content-Security-Policy: default-src 'self'
-
-    *Andrew White*
-
-*   Add `ActionController::Parameters#each_value`.
-
-    *Lukáš Zapletal*
-
-*   Deprecate `ActionDispatch::Http::ParameterFilter` in favor of `ActiveSupport::ParameterFilter`.
-
-    *Yoshiyuki Kinjo*
-
-*   Encode Content-Disposition filenames on `send_data` and `send_file`.
-    Previously, `send_data 'data', filename: "\u{3042}.txt"` sends
-    `"filename=\"\u{3042}.txt\""` as Content-Disposition and it can be
-    garbled.
-    Now it follows [RFC 2231](https://tools.ietf.org/html/rfc2231) and
-    [RFC 5987](https://tools.ietf.org/html/rfc5987) and sends
-    `"filename=\"%3F.txt\"; filename*=UTF-8''%E3%81%82.txt"`.
-    Most browsers can find filename correctly and old browsers fallback to ASCII
-    converted name.
-
-    *Fumiaki Matsushima*
+    *Jacob Bednarz*
 
-*   Expose `ActionController::Parameters#each_key` which allows iterating over
-    keys without allocating an array.
-
-    *Richard Schneeman*
-
-*   Purpose metadata for signed/encrypted cookies.
-
-    Rails can now thwart attacks that attempt to copy signed/encrypted value
-    of a cookie and use it as the value of another cookie.
-
-    It does so by stashing the cookie-name in the purpose field which is
-    then signed/encrypted along with the cookie value. Then, on a server-side
-    read, we verify the cookie-names and discard any attacked cookies.
-
-    Enable `action_dispatch.use_cookies_with_metadata` to use this feature, which
-    writes cookies with the new purpose and expiry metadata embedded.
-
-    *Assain Jaleel*
-
-*   Raises `ActionController::RespondToMismatchError` with conflicting `respond_to` invocations.
-
-    `respond_to` can match multiple types and lead to undefined behavior when
-    multiple invocations are made and the types do not match:
-
-        respond_to do |outer_type|
-          outer_type.js do
-            respond_to do |inner_type|
-              inner_type.html { render body: "HTML" }
-            end
-          end
-        end
-
-    *Patrick Toomey*
-
-*   `ActionDispatch::Http::UploadedFile` now delegates `to_path` to its tempfile.
-
-    This allows uploaded file objects to be passed directly to `File.read`
-    without raising a `TypeError`:
-
-        uploaded_file = ActionDispatch::Http::UploadedFile.new(tempfile: tmp_file)
-        File.read(uploaded_file)
-
-    *Aaron Kromer*
-
-*   Pass along arguments to underlying `get` method in `follow_redirect!`
-
-    Now all arguments passed to `follow_redirect!` are passed to the underlying
-    `get` method. This for example allows to set custom headers for the
-    redirection request to the server.
-
-        follow_redirect!(params: { foo: :bar })
-
-    *Remo Fritzsche*
-
-*   Introduce a new error page to when the implicit render page is accessed in the browser.
-
-    Now instead of showing an error page that with exception and backtraces we now show only
-    one informative page.
-
-    *Vinicius Stock*
-
-*   Introduce `ActionDispatch::DebugExceptions.register_interceptor`.
-
-    Exception aware plugin authors can use the newly introduced
-    `.register_interceptor` method to get the processed exception, instead of
-    monkey patching DebugExceptions.
-
-        ActionDispatch::DebugExceptions.register_interceptor do |request, exception|
-          HypoteticalPlugin.capture_exception(request, exception)
-        end
+*   Add the ability to set the CSP nonce only to the specified directives.
 
-    *Genadi Samokovarov*
+    Fixes #35137.
 
-*   Output only one Content-Security-Policy nonce header value per request.
+    *Yuji Yaginuma*
 
-    Fixes #32597.
+*   Keep part when scope option has value.
 
-    *Andrey Novikov*, *Andrew White*
+    When a route was defined within an optional scope, if that route didn't
+    take parameters the scope was lost when using path helpers. This commit
+    ensures scope is kept both when the route takes parameters or when it
+    doesn't.
 
-*   Move default headers configuration into their own module that can be included in controllers.
+    Fixes #33219.
 
-    *Kevin Deisz*
+    *Alberto Almagro*
 
-*   Add method `dig` to `session`.
+*   Added `deep_transform_keys` and `deep_transform_keys!` methods to ActionController::Parameters.
 
-    *claudiob*, *Takumi Shotoku*
+    *Gustavo Gutierrez*
 
-*   Controller level `force_ssl` has been deprecated in favor of
-    `config.force_ssl`.
+*   Calling `ActionController::Parameters#transform_keys`/`!` without a block now returns
+    an enumerator for the parameters instead of the underlying hash.
 
-    *Derek Prior*
+    *Eugene Kenny*
 
-*   Rails 6 requires Ruby 2.5.0 or newer.
+*   Fix strong parameters blocks all attributes even when only some keys are invalid (non-numerical).
+    It should only block invalid key's values instead.
 
-    *Jeremy Daer*, *Kasper Timm Hansen*
+    *Stan Lo*
 
 
-Please check [5-2-stable](https://github.com/rails/rails/blob/5-2-stable/actionpack/CHANGELOG.md) for previous changes.
+Please check [6-0-stable](https://github.com/rails/rails/blob/6-0-stable/actionpack/CHANGELOG.md) for previous changes.