Also add missing entries and use the formating convention
Logic in clone_empty method was dealing with old @dirty variable, which has changed by @html_safe in this commit: 139963c This was issuing a "not initialized variable" warning - related to: #5237 The logic applied by this method is already handled by the  override, so there is no need to reset the variable here.
* 3-2-2: bumping to 3.2.2 Ensure  respects the status of the buffer. Merge pull request #4834 from sskirby/fix_usage_of_psql_in_db_test_prepare Merge pull request #5084 from johndouthat/patch-1 updating RAILS_VERSION delete vulnerable AS::SafeBuffer# use AS::SafeBuffer#clone_empty for flushing the output_buffer add AS::SafeBuffer#clone_empty fix output safety issue with select options
* 3-2-stable-security: Ensure  respects the status of the buffer. delete vulnerable AS::SafeBuffer# use AS::SafeBuffer#clone_empty for flushing the output_buffer add AS::SafeBuffer#clone_empty fix output safety issue with select options
In asset_tag_helper_test.rb there is an assert on the number of bytes in a concatenated file. This test failed because Windows converts \n to \r\n as the default for "w". This is different than in *nix systems where there is no conversion done. THe test that failed was test_caching_stylesheet_link_tag_when_caching_on Using bin mode fixes this behavior on windows and makes no change on the *nix systems.
https://bugs.ruby-lang.org/projects/ruby-trunk/repository/revisions/34580 In this revision behavior of respond_to? had changed: now to ask about protected method one should pass second argument `true`
…n whiny nil
…n message verifier
…n ActiveSupport::Concern in Base64
This reverts commit abe915f. This broke all existing keys and it's wrong anyway. The array is just there as a convenience option for building the string. It's intentional that [ "stuff"] and "stuff" generates the same key.