Bump activesupport from 6.0.1 to 6.0.3.1

[dependabot[bot]]

⚠️ Dependabot is rebasing this PR ⚠️

If you make any changes to it yourself then they will take precedence over the rebase.

---

Bumps activesupport from 6.0.1 to 6.0.3.1.

Release notes

Sourced from activesupport's releases.

6.0.3

In this version, we fixed warnings when used with Ruby 2.7 across the entire framework.

Following are the list of other changes, per-framework.

Active Support

• Array#to_sentence no longer returns a frozen string.

  Before:

  ['one', 'two'].to_sentence.frozen?
  # => true
  

  After:

  ['one', 'two'].to_sentence.frozen?
  # => false
  

  Nicolas Dular

• Update ActiveSupport::Messages::Metadata#fresh? to work for cookies with expiry set when ActiveSupport.parse_json_times = true.

  Christian Gregg

Active Model

• No changes.

Active Record

• Recommend applications don't use the database kwarg in connected_to

  The database kwarg in connected_to was meant to be used for one-off scripts but is often used in requests. This is really dangerous because it re-establishes a connection every time. It's deprecated in 6.1 and will be removed in 6.2 without replacement. This change soft deprecates it in 6.0 by removing documentation.

  Eileen M. Uchitelle

• Fix support for PostgreSQL 11+ partitioned indexes.

  Sebastián Palma

• Add support for beginless ranges, introduced in Ruby 2.7.

  Josh Goodall

... (truncated)

Changelog

Sourced from activesupport's changelog.

Rails 6.0.3.1 (May 18, 2020)

• [CVE-2020-8165] Deprecate Marshal.load on raw cache read in RedisCacheStore

• [CVE-2020-8165] Avoid Marshal.load on raw cache value in MemCacheStore

Rails 6.0.3 (May 06, 2020)

• Array#to_sentence no longer returns a frozen string.

  Before:

  ['one', 'two'].to_sentence.frozen?
  # => true
  

  After:

  ['one', 'two'].to_sentence.frozen?
  # => false
  

  Nicolas Dular

• Update ActiveSupport::Messages::Metadata#fresh? to work for cookies with expiry set when ActiveSupport.parse_json_times = true.

  Christian Gregg

Rails 6.0.2.2 (March 19, 2020)

• No changes.

Rails 6.0.2.1 (December 18, 2019)

• No changes.

Rails 6.0.2 (December 13, 2019)

• Eager load translations during initialization.

  Diego Plentz

• Use per-thread CPU time clock on ActiveSupport::Notifications.

  George Claghorn

Commits

• 34991a6 Preparing for 6.0.3.1 release
• 2c8fe2a bumping version, updating changelog
• 0ad524a update changelog
• bd39a13 activesupport: Deprecate Marshal.load on raw cache read in RedisCacheStore
• 0a7ce52 activesupport: Avoid Marshal.load on raw cache value in MemCacheStore
• b738f19 Preparing for 6.0.3 release
• 509b9da Preparing for 6.0.3.rc1 release
• 02d07cc adds missing require [Fixes #39042]
• f2f7bcc Fix Builder::XmlMarkup lazy load in Array#to_xml
• 320734e Merge pull request #36941 from ts-3156/master
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/yegor256/0rsk/network/alerts).

[0crat]

@yegor256/z please, pay attention to this pull request

[codecov-commenter]

Codecov Report

Merging #63 into master will not change coverage. The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #63   +/-   ##
=======================================
  Coverage   38.69%   38.69%           
=======================================
  Files          28       28           
  Lines         752      752           
=======================================
  Hits          291      291           
  Misses        461      461           

---

Continue to review full report at Codecov.

Legend - Click here to learn more Δ = absolute <relative> (impact), ø = not affected, ? = missing data Powered by Codecov. Last update dc1e1af...d63fd4a. Read the comment docs.

[0crat]

@yegor256/z everybody who has role REV is banned at #63; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

[0crat]

@yegor256/z everybody who has role REV is banned at #63; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

[0crat]

@yegor256/z everybody who has role REV is banned at #63; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

[0crat]

@yegor256/z everybody who has role REV is banned at #63; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

[0crat]

@yegor256/z everybody who has role REV is banned at #63; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

[0crat]

@yegor256/z everybody who has role REV is banned at #63; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

[0crat]

@yegor256/z everybody who has role REV is banned at #63; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

[0crat]

@yegor256/z everybody who has role REV is banned at #63; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

[0crat]

@yegor256/z everybody who has role REV is banned at #63; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

[0crat]

@yegor256/z everybody who has role REV is banned at #63; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

[0crat]

@yegor256/z everybody who has role REV is banned at #63; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

[dependabot[bot]]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.

[0crat]

Job gh:yegor256/0rsk#63 is not assigned, can't get performer

[0crat]

Pull request #63 was not merged, no payment for ARC, see §28