Add Public Api for register new extensions for Rake Notes
Remove .scss, .sass, .less, .haml, .slim, coffee from Rake Notes. Now we have an API for register it in the corresponding gems
Supporting .ruby, .yml and .yaml Extension in Rake Notes
re-raise error if error occurs before committing in streaming

update the tests, using an if-else
Fix Shadowing extensions variable in Register Annotation Exentsions
Add config.annotations, in order to register new extensions for Rake notes at config level
Fix assertions
format ActiveRecord CHANGELOG. [ci skip]
fix `number_to_percentage` with `Float::NAN`, `Float::INFINITY`.

Closes #14405.

This is a follow-up to 9e997e9039435617b6a844158f5437e97f6bc107 to restore
the documented behavior.
`where.not` adds `references` for `includes`.

Closes #14406.
Add Changelog Entry ref #14379
Merge pull request #14090 from Fortisque/kevin/stream_error_in_main_thread_if_not_committed

re-raise error if error occurs before committing in streaming
Update command line  guide
Rake notes should picked up new Extensions registered in the config/application.rb file
Merge pull request #14379 from robertomiranda/rake-notes.config

Add Public Api for Register New Extensions for Rake Notes
Teach PostgreSQLAdapter#reset! to actually reset

It wasn't doing anything beyond clearing the statement cache.
Reap connections based on owning-thread death

.. not a general timeout.

Now, if a thread checks out a connection then dies, we can immediately
recover that connection and re-use it.

This should alleviate the pool exhaustion discussed in #12867. More
importantly, it entirely avoids the potential issues of the reaper
attempting to check whether connections are still active: as long as the
owning thread is alive, the connection is its business alone.

As a no-op reap is now trivial (only entails checking a thread status
per connection), we can also perform one in-line any time we decide to
sleep for a connection.
Merge pull request #14360 from matthewd/thread_aware_reaper

Track owning thread for connection pool
use a latch to avoid busy loops
test should only pass if the pool.size+1 checkout fails

Previously, any of the connection checkouts could have failed, and this
test would pass.