Only include files that contain changes since the last generation
of the API documentation.

Thus, only modified files are re-generated instead of the whole API.

The `created.rid` file won't contain the whole list of files anymore
if we generate several times the API but we don't really care about it,
only the generation date and time is important.

It is possible to fall back to the previous behavior by defining the ALL
environment variable running the `rake rdoc` task.

Dry downloader

Pathname might not be always initialized.

Fixed unnecessary nesting in handle_dependency

Fix a link to use RDoc syntax and make sure that the titles' level
match the section we are in since we are both documenting the new
and the legacy syntax.

fix respond_to? documentation [ci skip]

This nested if checked the same value as the containing case statement.
Moved the code in the if/else into when/else in the containing case.

Require 'pathname' explicitly

Update Syntax Highlighter to version 4 [ci skip]

Add ActiveSupport::Notifications hook to ActionCable::Server.broadcast

ActionCable, sometimes add_channel is not called.

Improve error message when record touch fails.

- Build Syntax Highlighter based on https://github.com/syntaxhighlighter/syntaxhighlighter/wiki/Building and use theme generated by fxn.
- This also bundles these brushes in the file itself- ruby,css,xml,sql,javascript,plain. Generation command used:
gulp build --compat --brushes=javascript,ruby,xml,sql,plain --theme=/Path/To/RailsSource/rails/guides/assets/stylesheets/syntaxhighlighter/shThemeRailsGuides.css
- rm all old js and css files
- Moved over how JS configuration is created for Syntax Highlighter
- Fixed layout for all imports
- Fixes bug with old copy paste, generating wrong space character on webkit https://github.com/syntaxhighlighter/syntaxhighlighter/blob/7caa9632e7fe470d944fc06b4db7d35352ebaa36/src/dom.js#L227

 Fixes #25655

Clarify Postgres initials. [skip ci]

Update Rails 5 release notes with syntax fixes. [ci skip]

The current error message only indicates that a touch can fail because the record is new. In practice, we saw cases where touches were failing because the record had been destroyed. `persisted?` checks `new_record?` *and* `destroyed?`. It was confusing to get a message about a new record when in reality we were destroying records.

I also included a helpful tip for users to consider using `persisted?`, `new_record?`, or `destroyed?` before touching.

Fix typo: accidently -> accidentally. [ci skip]

remove needless comments

Correct guide generation command [ci skip]

Remove unused `predicate_builder` for `BasicObjectHandler` and `RangeHandler`

`partial` option on the digest method is no more needed [ci skip]:

refer to rails command instead of rake in doc of `SourceAnnotationExtractor`

Clean backtrace in IRB

- `partial` option is not used anymore, this was removed in https://github.com/rails/rails/pull/23724

fix task name to remove

Follow up to #25431

Remove #select_one from Mysql2Adapter

Renamed NestedParametersTest to NestedParametersPermitTest

Revert "Rename `active_record_internal_metadatas` to `ar_internal_metadata"

Remove `create_table_info_cache` because it not be reused