Update activerecord requirement from >= 5.1, < 7.1 to >= 5.1, < 7.2

[dependabot]

Updates the requirements on activerecord to permit the latest version.

Release notes

Sourced from activerecord's releases.

7.1.0

Active Support

• Fix AS::MessagePack with ENV["RAILS_MAX_THREADS"].

  Jonathan Hefner

• Add a new public API for broadcasting logs

  This feature existed for a while but was until now a private API. Broadcasting log allows to send log message to difference sinks (STDOUT, a file ...) and is used by default in the development environment to write logs both on STDOUT and in the "development.log" file.

  Basic usage:

  stdout_logger = Logger.new(STDOUT)
  file_logger = Logger.new("development.log")
  broadcast = ActiveSupport::BroadcastLogger.new(stdout_logger, file_logger)
  broadcast.info("Hello!") # The "Hello!" message is written on STDOUT and in the log file.

  Adding other sink(s) to the broadcast:

  broadcast = ActiveSupport::BroadcastLogger.new
  broadcast.broadcast_to(Logger.new(STDERR))

  Remove a sink from the broadcast:

  stdout_logger = Logger.new(STDOUT)
  broadcast = ActiveSupport::BroadcastLogger.new(stdout_logger)
  broadcast.stop_broadcasting_to(stdout_logger)

  Edouard Chin

• Fix Range#overlap? not taking empty ranges into account on Ruby < 3.3

  Nobuyoshi Nakada, Shouichi Kamiya, Hartley McGuire

• Use Ruby 3.3 Range#overlap? if available

  Yasuo Honda

... (truncated)

Changelog

Sourced from activerecord's changelog.

Rails 7.1.0 (October 05, 2023)

• No changes.

Rails 7.1.0.rc2 (October 01, 2023)

• Remove -shm and -wal SQLite files when rails db:drop is run.

  Niklas Häusele

• Revert the change to raise an ArgumentError when #accepts_nested_attributes_for is declared more than once for an association in the same class.

  The reverted behavior broke the case where the #accepts_nested_attributes_for was defined in a concern and where overridden in the class that included the concern.

  Rafael Mendonça França

Rails 7.1.0.rc1 (September 27, 2023)

• Better naming for unique constraints support.

  Naming unique keys leads to misunderstanding it's a short-hand of unique indexes. Just naming it unique constraints is not misleading.

  In Rails 7.1.0.beta1 or before:

  add_unique_key :sections, [:position], deferrable: :deferred, name: "unique_section_position"
  remove_unique_key :sections, name: "unique_section_position"

  Now:

  add_unique_constraint :sections, [:position], deferrable: :deferred, name: "unique_section_position"
  remove_unique_constraint :sections, name: "unique_section_position"

  Ryuta Kamizono

• Fix duplicate quoting for check constraint expressions in schema dump when using MySQL

  A check constraint with an expression, that already contains quotes, lead to an invalid schema dump with the mysql2 adapter.

  Fixes #42424.

... (truncated)

Commits

• d39db5d Preparing for 7.1.0 release
• b6842b2 Merge pull request #49391 from ipc103/transaction-tracking-on-reconnect
• 1490788 Merge pull request #49470 from rails/rm-eager-load-model-schema
• bfc686f Merge pull request #49483 from fatkodima/fix-uniq-validation-for-expr-indexes
• 48b8372 Merge pull request #49478 from p8/activerecord/women-write-books-too
• ad93852 Merge pull request #49465 from yahonda/add_gitignore_test_storage
• 4b5927a Ensure PG connection is configured before looking up types
• 8340f8f Preparing for 7.1.0.rc2 release
• 5f3ec41 Sync CHANGELOG
• f9133f7 Revert "Merge pull request #49056 from joshuay03/raise-on-duplicate-accepts-n...
• 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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @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)

[coveralls]

coverage: 97.059%. remained the same when pulling 273c1e2 on dependabot/bundler/activerecord-gte-5.1-and-lt-7.2 into ab4c1e8 on 1.2.

[dependabot]

Superseded by #443.