No-Jira(deps): Bump activesupport from 6.0.3.1 to 6.1.3.2

[dependabot-preview]

Bumps activesupport from 6.0.3.1 to 6.1.3.2.

Release notes

Sourced from activesupport's releases.

6.1.3.1

Active Support

• No changes.

Active Model

• No changes.

Active Record

• No changes.

Action View

• No changes.

Action Pack

• No changes.

Active Job

• No changes.

Action Mailer

• No changes.

Action Cable

• No changes.

... (truncated)

Changelog

Sourced from activesupport's changelog.

Rails 6.1.3.2 (May 05, 2021)

• No changes.

Rails 6.1.3.1 (March 26, 2021)

• No changes.

Rails 6.1.3 (February 17, 2021)

• No changes.

Rails 6.1.2.1 (February 10, 2021)

• No changes.

Rails 6.1.2 (February 09, 2021)

• ActiveSupport::Cache::MemCacheStore now accepts an explicit nil for its addresses argument.

  config.cache_store = :mem_cache_store, nil
  is now equivalent to
  config.cache_store = :mem_cache_store
  and is also equivalent to
  config.cache_store = :mem_cache_store, ENV["MEMCACHE_SERVERS"] || "localhost:11211"
  which is the fallback behavior of Dalli

  This helps those migrating from :dalli_store, where an explicit nil was permitted.

  Michael Overmeyer

Rails 6.1.1 (January 07, 2021)

• Change IPAddr#to_json to match the behavior of the json gem returning the string representation instead of the instance variables of the object.

  Before:

... (truncated)

Commits

• 75ac626 Preparing for 6.1.3.2 release
• 9c21201 Prep for release
• 85c6823 v6.1.3.1
• 5aaaa16 Preparing for 6.1.3 release
• eddb809 Merge pull request #41441 from jonathanhefner/apidocs-inline-code-markup
• 130c128 Preparing for 6.1.2.1 release
• bf8c59c Preparing for 6.1.2 release
• ca798c0 Merge pull request #41381 from movermeyer/allow_for_nil_addresses_from_dalli_...
• 97a0a94 Fix warning with Ruby 2.7 on Time.at with keyword arguments
• 5400804 Merge pull request #41376 from fatkodima/memcached-normalize_key-nil
• 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 badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in the .dependabot/config.yml file in this repo:

• Update frequency
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)

[dependabot-preview]

Superseded by #53.