Fixes #32129.

Add pg 1.0.0 compatibility to 5.2.0.rc1 Changelog

[ci skip]

[ci skip]

Merge Previews/Variants controller into one Representations controller.

Update `guides/CHANGELOG.md`

To Rails 5.2.0.beta1 was added "Threading and Code Execution in Rails" Guide
by 8bfa617e.

To Rails 5.2.0.rc1 was added "Active Storage Overview" Guide
by 48fbc4ae.

This commit adds changelogs about adding these guides.
I think it deserves to be mentioned in`guides/CHANGELOG.md`

This has been removed in 7123c9bc.

There is no reason `attributes=` doesn't take `assign_attributes`.

Use column alias of primary_key in limited_ids_for

Don't accidentally lose includes in serialization

Active Record distinct & order #count regression

Actually `reflection.klass` should be valid AR model unless
`polymorphic?`. Previously it worked limitedly by ignoring `NameError`
even if `reflection.klass` is invalid, and our isolated testing depends
on the limited working.
Probably we should also check the klass validity in `check_validity!`
properly. Until that time, I restored the error suppression for now.

Closes #32113.

Make `reflection.klass` raise if `polymorphic?` not to be misused

This is an alternative of #29722, and revert of #29601 and a1fcbd97.

Currently, association creation and normal association finding doesn't
respect `store_full_sti_class`. But eager loading and preloading respect
the setting. This means that if set `store_full_sti_class = false`
(`true` by default), eager loading and preloading can not find
created polymorphic records.

Association creation and finding should work consistently.

BC dates are supported by both date and datetime types.

https://www.postgresql.org/docs/current/static/datatype-datetime.html

Since #1097, new datetime allows year zero as 1 BC, but new date does
not. It should be allowed even in new date consistently.

The values infinity and -infinity are supported by both date and
timestamp types.

https://www.postgresql.org/docs/current/static/datatype-datetime.html#DATATYPE-DATETIME-SPECIAL-TABLE

And also, it can not be known whether a value is infinity correctly
unless cast a value.

I've added `QueryAttribute#infinity?` to handle that case.

Closes #27585.

Consistent behavior for session and cookies with to_h and to_hash method

Expand AR::Base.abstract_class documentation

[ci skip]

Add ActiveModel::Attributes#attributes

Raise an error if advisory lock in migrator was not released.

Prevent older versions of Chrome from appending a Content-Type header containing the Blob type, rendering the request invalid if we intend not to provide a Content-Type. This behavior was observed in Chrome 58.

See 948b9319 for context

Currently the place where we limit what gets sent to the database is in
the implementation for `partial_writes`. We should also be restricting
it to column names when partial writes are turned off.

Note that we're using `&` instead of just defaulting to
`self.class.column_names`, as the instance version of `attribute_names`
does not include attributes which are uninitialized (were not included
in the select clause)

Fix customizing the download Content-Type for a directly-uploaded blob via a signed URL. See e8286ee2.

Move up activestorage' changelog added by 5292cdf5

[ci skip]

It wasn't fixed in Rails 5.2.0.rc1 since it was backported after this release.

Use lazy load hook to configure ActiveStorage::Blob

- Update the default HSTS max-age value to 31536000 seconds (1 year)
  to meet the minimum max-age requirement for https://hstspreload.org/.

Closes #32096.

`content_security_policy_nonce_generator` specifies request as an argument when calling.
https://github.com/rails/rails/blob/ddb7da8535b07f51b7a8f5e3062cc8ffbd4ff23b/actionpack/lib/action_dispatch/http/content_security_policy.rb#L100

So without this fix, will raise `ArgumentError` when start server.

Improve generated file `app/assets/javascripts/application.js` of plugin

Correct method documentation