Bump actionpack from 7.0.1 to 7.0.2.2

[dependabot]

Bumps actionpack from 7.0.1 to 7.0.2.2.

Release notes

Sourced from actionpack's releases.

7.0.2

Active Support

• Fix ActiveSupport::EncryptedConfiguration to be compatible with Psych 4

  Stephen Sugden

• Improve File.atomic_write error handling.

  Daniel Pepper

Active Model

• Use different cache namespace for proxy calls

  Models can currently have different attribute bodies for the same method names, leading to conflicts. Adding a new namespace :active_model_proxy fixes the issue.

  Chris Salzberg

Active Record

• Fix PG.connect keyword arguments deprecation warning on ruby 2.7.

  Nikita Vasilevsky

• Fix the ability to exclude encryption params from being autofiltered.

  Mark Gangl

• Dump the precision for datetime columns following the new defaults.

  Rafael Mendonça França

• Make sure encrypted attributes are not being filtered twice.

  Nikita Vasilevsky

• Dump the database schema containing the current Rails version.

  Since rails/rails#42297, Rails now generate datetime columns with a default precision of 6. This means that users upgrading to Rails 7.0 from 6.1, when loading the database schema, would get the new precision value, which would not match the production schema.

... (truncated)

Changelog

Sourced from actionpack's changelog.

Rails 7.0.2.2 (February 11, 2022)

• No changes.

Rails 7.0.2.1 (February 11, 2022)

• Under certain circumstances, the middleware isn't informed that the response body has been fully closed which result in request state not being fully reset before the next request

  [CVE-2022-23633]

Rails 7.0.2 (February 08, 2022)

• No changes.

Commits

• 2459c20 Preparing for 7.0.2.2 release
• 4ff529b Preparing release
• 365e0fe Preparing for 7.0.2.1 release
• 7791cd6 updating changelog
• 3c0420c ActionDispatch::Executor don't fully trust body#close
• 76489d8 Preparing for 7.0.2 release
• 346d733 Merge pull request #44354 from rails/to-fs-as-the-primary
• See full diff 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.

[dependabot]

Superseded by #150.