Bump the all-dependencies group with 6 updates

[dependabot]

Bumps the all-dependencies group with 6 updates:

Package	From	To
sqlalchemy	2.0.23	2.0.26
sqlakeyset	2.0.1701229837	2.0.1706067133
black	23.12.1	24.1.1
pg8000	1.30.3	1.30.4
pytest	7.4.3	8.0.0
pytest-asyncio	0.23.2	0.23.5

Updates sqlalchemy from 2.0.23 to 2.0.26

Release notes

Sourced from sqlalchemy's releases.

2.0.26

Released: February 11, 2024

orm

• [orm] [bug] Replaced the "loader depth is excessively deep" warning with a shorter message added to the caching badge within SQL logging, for those statements where the ORM disabled the cache due to a too-deep chain of loader options. The condition which this warning highlights is difficult to resolve and is generally just a limitation in the ORM's application of SQL caching. A future feature may include the ability to tune the threshold where caching is disabled, but for now the warning will no longer be a nuisance.

  References: #10896

• [orm] [bug] Fixed issue where it was not possible to use a type (such as an enum) within a _orm.Mapped container type if that type were declared locally within the class body. The scope of locals used for the eval now includes that of the class body itself. In addition, the expression within _orm.Mapped may also refer to the class name itself, if used as a string or with future annotations mode.

  References: #10899

• [orm] [bug] Fixed issue where using _orm.Session.delete() along with the _orm.Mapper.version_id_col feature would fail to use the correct version identifier in the case that an additional UPDATE were emitted against the target object as a result of the use of _orm.relationship.post_update on the object. The issue is similar to #10800 just fixed in version 2.0.25 for the case of updates alone.

  References: #10967

• [orm] [bug] Fixed issue where an assertion within the implementation for _orm.with_expression() would raise if a SQL expression that was not cacheable were used; this was a 2.0 regression since 1.4.

  References: #10990

examples

• [examples] [bug] Fixed regression in history_meta example where the use of _schema.MetaData.to_metadata() to make a copy of the history table would also copy indexes (which is a good thing), but causing naming conflicts indexes regardless of naming scheme used for those indexes. A "_history" suffix is now added to these indexes in the same way as is

... (truncated)

Commits

• See full diff in compare view

Updates sqlakeyset from 2.0.1701229837 to 2.0.1706067133

Commits

• See full diff in compare view

Updates black from 23.12.1 to 24.1.1

Release notes

Sourced from black's releases.

24.1.1

Bugfix release to fix a bug that made Black unusable on certain file systems with strict limits on path length.

Preview style

• Consistently add trailing comma on typed parameters (#4164)

Configuration

• Shorten the length of the name of the cache file to fix crashes on file systems that do not support long paths (#4176)

24.1.0

Highlights

This release introduces the new 2024 stable style (#4106), stabilizing the following changes:

• Add parentheses around if-else expressions (#2278)
• Dummy class and function implementations consisting only of ... are formatted more compactly (#3796)
• If an assignment statement is too long, we now prefer splitting on the right-hand side (#3368)
• Hex codes in Unicode escape sequences are now standardized to lowercase (#2916)
• Allow empty first lines at the beginning of most blocks (#3967, #4061)
• Add parentheses around long type annotations (#3899)
• Enforce newline after module docstrings (#3932, #4028)
• Fix incorrect magic trailing comma handling in return types (#3916)
• Remove blank lines before class docstrings (#3692)
• Wrap multiple context managers in parentheses if combined in a single with statement (#3489)
• Fix bug in line length calculations for power operations (#3942)
• Add trailing commas to collection literals even if there's a comment after the last entry (#3393)
• When using --skip-magic-trailing-comma or -C, trailing commas are stripped from subscript expressions with more than 1 element (#3209)
• Add extra blank lines in stubs in a few cases (#3564, #3862)
• Accept raw strings as docstrings (#3947)
• Split long lines in case blocks (#4024)
• Stop removing spaces from walrus operators within subscripts (#3823)
• Fix incorrect formatting of certain async statements (#3609)
• Allow combining # fmt: skip with other comments (#3959)

There are already a few improvements in the --preview style, which are slated for the 2025 stable style. Try them out and share your feedback. In the past, the preview style has included some features that we were not able to stabilize. This year, we're

... (truncated)

Changelog

Sourced from black's changelog.

24.1.1

Bugfix release to fix a bug that made Black unusable on certain file systems with strict limits on path length.

Preview style

• Consistently add trailing comma on typed parameters (#4164)

Configuration

• Shorten the length of the name of the cache file to fix crashes on file systems that do not support long paths (#4176)

24.1.0

Highlights

This release introduces the new 2024 stable style (#4106), stabilizing the following changes:

• Add parentheses around if-else expressions (#2278)
• Dummy class and function implementations consisting only of ... are formatted more compactly (#3796)
• If an assignment statement is too long, we now prefer splitting on the right-hand side (#3368)
• Hex codes in Unicode escape sequences are now standardized to lowercase (#2916)
• Allow empty first lines at the beginning of most blocks (#3967, #4061)
• Add parentheses around long type annotations (#3899)
• Enforce newline after module docstrings (#3932, #4028)
• Fix incorrect magic trailing comma handling in return types (#3916)
• Remove blank lines before class docstrings (#3692)
• Wrap multiple context managers in parentheses if combined in a single with statement (#3489)
• Fix bug in line length calculations for power operations (#3942)
• Add trailing commas to collection literals even if there's a comment after the last entry (#3393)
• When using --skip-magic-trailing-comma or -C, trailing commas are stripped from subscript expressions with more than 1 element (#3209)
• Add extra blank lines in stubs in a few cases (#3564, #3862)
• Accept raw strings as docstrings (#3947)
• Split long lines in case blocks (#4024)
• Stop removing spaces from walrus operators within subscripts (#3823)
• Fix incorrect formatting of certain async statements (#3609)
• Allow combining # fmt: skip with other comments (#3959)

There are already a few improvements in the --preview style, which are slated for the 2025 stable style. Try them out and share your feedback. In the past, the preview style has included some features that we were not able to stabilize. This year, we're

... (truncated)

Commits

• e026c93 Prepare release 24.1.1 (#4186)
• 79fc115 chore: ignore node_modules (produced by a pre-commit check) (#4184)
• 8bf0454 Consistently add trailing comma on typed parameters (#4164)
• 1607e9a Fix missing space in option description (#4182)
• ed770ba Fix cache file length (#4176)
• 659c29a New changelog
• 0e6e46b Prepare release 24.1.0 (#4170)
• 4f47cac Add --unstable flag (#4096)
• bccec8a Show warning on invalid toml configuration (#4165)
• 7d78946 Describe 2024 module docstring more accurately (#4168)
• Additional commits viewable in compare view

Updates pg8000 from 1.30.3 to 1.30.4

Commits

• f6f416c Prepare for new release
• 8adb556 Add support for more range and multirange types
• 796cd01 Make Connection.parameter_statuses a dict
• a93944e Fix doctest for PostgreSQL 15+
• 433e01f Fix doctest problem with IDENTIFY_SYSTEM command
• a2dc1e8 Fix copy tests for PostgreSQL 16
• c662f40 PostgreSQL versions: add 16, drop 11
• See full diff in compare view

Updates pytest from 7.4.3 to 8.0.0

Release notes

Sourced from pytest's releases.

pytest 8.0.0 (2024-01-27)

See 8.0.0rc1 and 8.0.0rc2 for the full changes since pytest 7.4!

Bug Fixes

• #11842: Properly escape the reason of a skip <pytest.mark.skip ref>{.interpreted-text role="ref"} mark when writing JUnit XML files.
• #11861: Avoid microsecond exceeds 1_000_000 when using log-date-format with %f specifier, which might cause the test suite to crash.

8.0.0rc2

pytest 8.0.0rc2 (2024-01-17)

Improvements

• #11233: Improvements to -r for xfailures and xpasses:
  • Report tracebacks for xfailures when -rx is set.
  • Report captured output for xpasses when -rX is set.
  • For xpasses, add - in summary between test name and reason, to match how xfail is displayed.
• #11825: The pytest_plugin_registered{.interpreted-text role="hook"} hook has a new plugin_name parameter containing the name by which plugin is registered.

Bug Fixes

• #11706: Fix reporting of teardown errors in higher-scoped fixtures when using [--maxfail]{.title-ref} or [--stepwise]{.title-ref}.

• #11758: Fixed IndexError: string index out of range crash in if highlighted[-1] == "\n" and source[-1] != "\n". This bug was introduced in pytest 8.0.0rc1.

• #9765, #11816: Fixed a frustrating bug that afflicted some users with the only error being assert mod not in mods. The issue was caused by the fact that str(Path(mod)) and mod.__file__ don't necessarily produce the same string, and was being erroneously used interchangably in some places in the code.

  This fix also broke the internal API of PytestPluginManager.consider_conftest by introducing a new parameter -- we mention this in case it is being used by external code, even if marked as private.

pytest 8.0.0rc1 (2023-12-30)

See https://docs.pytest.org/en/latest/changelog.html#pytest-8-0-0rc1-2023-12-30 for the rendered changelog.

Breaking Changes

Old Deprecations Are Now Errors

• #7363: PytestRemovedIn8Warning deprecation warnings are now errors by default.

  Following our plan to remove deprecated features with as little disruption as possible, all warnings of type PytestRemovedIn8Warning now generate errors instead of warning messages by default.

  The affected features will be effectively removed in pytest 8.1, so please consult the deprecations{.interpreted-text role="ref"} section in the docs for directions on how to update existing code.

  In the pytest 8.0.X series, it is possible to change the errors back into warnings as a stopgap measure by adding this to your pytest.ini file:

  [pytest]

... (truncated)

Commits

• 478f823 Prepare release version 8.0.0
• 6085900 [8.0.x] fix: avoid rounding microsecond to 1_000_000 (#11863)
• 3b41c65 [8.0.x] Escape skip reason in junitxml (#11845)
• 747072a [8.0.x] Update docstring of scripts/generate-gh-release-notes.py (#11768)
• 011a475 Properly attach packages to the GH release notes (#11839) (#11840)
• 97960bd Merge pull request #11835 from pytest-dev/release-8.0.0rc2
• 6be0a3c Prepare release version 8.0.0rc2
• 44ffe07 Merge pull request #11837 from pytest-dev/backport-11836-to-8.0.x
• 14ecb04 [8.0.x] testing: temporarily disable test due to hypothesis issue
• 41c8dab Merge pull request #11831 from bluetech/backport-11825-to-8.0.x
• Additional commits viewable in compare view

Updates pytest-asyncio from 0.23.2 to 0.23.5

Release notes

Sourced from pytest-asyncio's releases.

pytest-asyncio 0.23.5

0.23.5 (2024-02-09)

• Declare compatibility with pytest 8 #737
• Fix typing errors with recent versions of mypy #769
• Prevent DeprecationWarning about internal use of asyncio.get_event_loop() from affecting test cases #757

Known issues

As of v0.23, pytest-asyncio attaches an asyncio event loop to each item of the test suite (i.e. session, packages, modules, classes, functions) and allows tests to be run in those loops when marked accordingly. Pytest-asyncio currently assumes that async fixture scope is correlated with the new event loop scope. This prevents fixtures from being evaluated independently from the event loop scope and breaks some existing test suites (see #706). For example, a test suite may require all fixtures and tests to run in the same event loop, but have async fixtures that are set up and torn down for each module. If you're affected by this issue, please continue using the v0.21 release, until it is resolved.

pytest-asyncio 0.23.5a0

0.23.5 (UNRELEASED)

• Declare compatibility with pytest 8 #737
• Fix typing errors with recent versions of mypy #769

Known issues

As of v0.23, pytest-asyncio attaches an asyncio event loop to each item of the test suite (i.e. session, packages, modules, classes, functions) and allows tests to be run in those loops when marked accordingly. Pytest-asyncio currently assumes that async fixture scope is correlated with the new event loop scope. This prevents fixtures from being evaluated independently from the event loop scope and breaks some existing test suites (see #706). For example, a test suite may require all fixtures and tests to run in the same event loop, but have async fixtures that are set up and torn down for each module. If you're affected by this issue, please continue using the v0.21 release, until it is resolved.

pytest-asyncio 0.23.4

0.23.4 (2024-01-28)

• pytest-asyncio no longer imports additional, unrelated packages during test collection #729
• Addresses further issues that caused an internal pytest error during test collection
• Declares incompatibility with pytest 8 #737

pytest-asyncio 0.23.4a2

0.23.4 (UNRELEASED)

• pytest-asyncio no longer imports additional, unrelated packages during test collection #729
• Addresses further issues that caused an internal pytest error during test collection

Known issues

As of v0.23, pytest-asyncio attaches an asyncio event loop to each item of the test suite (i.e. session, packages, modules, classes, functions) and allows tests to be run in those loops when marked accordingly. Pytest-asyncio currently assumes that async fixture scope is correlated with the new event loop scope. This prevents fixtures from being evaluated independently from the event loop scope and breaks some existing test suites (see #706). For example, a test suite may require all fixtures and tests to run in the same event loop, but have async fixtures that are set up and torn down for each module. If you're affected by this issue, please continue using the v0.21 release, until it is resolved.

pytest-asyncio 0.23.4a1

0.23.4 (UNRELEASED)

• pytest-asyncio no longer imports additional, unrelated packages during test collection #729

Known issues

As of v0.23, pytest-asyncio attaches an asyncio event loop to each item of the test suite (i.e. session, packages, modules, classes, functions) and allows tests to be run in those loops when marked accordingly. Pytest-asyncio currently assumes that async fixture scope is correlated with the new event loop scope. This prevents fixtures from being evaluated independently from the event loop scope and breaks some existing test suites (see #706). For example, a test suite may require all fixtures and tests to run in the same event loop, but have async fixtures that are set up and torn down for each module. If you're affected by this issue, please continue using the v0.21 release, until it is resolved.

pytest-asyncio 0.23.4a0

0.23.4 (UNRELEASED)

• pytest-asyncio no longer imports additional, unrelated packages during test collection #729

Known issues

As of v0.23, pytest-asyncio attaches an asyncio event loop to each item of the test suite (i.e. session, packages, modules, classes, functions) and allows tests to be run in those loops when marked accordingly. Pytest-asyncio currently assumes that async fixture scope is correlated with the new event loop scope. This prevents fixtures from being evaluated independently from the event loop scope and breaks some existing test suites (see #706). For example, a test suite may require all fixtures and tests to run in the same event loop, but have async fixtures that are set up and torn down for each module. If you're affected by this issue, please continue using the v0.21 release, until it is resolved.

pytest-asyncio 0.23.3

0.23.3 (2024-01-01)

• Fixes a bug that caused event loops to be closed prematurely when using async generator fixtures with class scope or wider in a function-scoped test #706

... (truncated)

Commits

• 3aef605 [build] Update actions/upload-artifact and actions/download-artifact to v4.
• 4b1908d [fix] Prevent DeprecationWarning from bubbling to user code.
• fc6d6cf Fix typing and update to mypy 1.8.0 (#769)
• 6008cf1 Build(deps): Bump pluggy from 1.3.0 to 1.4.0 in /dependencies/default
• 712c51b Build(deps): Bump coverage from 7.4.0 to 7.4.1 in /dependencies/default
• 42fd304 Build(deps): Bump hypothesis in /dependencies/default
• a40b4f6 Build(deps): Bump urllib3 from 2.1.0 to 2.2.0 in /dependencies/docs
• 9d90f8e Build(deps): Bump certifi in /dependencies/docs
• fe5da07 Build(deps): Bump markupsafe from 2.1.4 to 2.1.5 in /dependencies/docs
• 42b140d fix compatibility with pytest ^8 (#776)
• 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 <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[codecov-commenter]

Codecov Report

Merging #123 (9b9d1a7) into main (ba0dceb) will not change coverage.
The diff coverage is n/a.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #123   +/-   ##
=======================================
  Coverage   84.28%   84.28%           
=======================================
  Files          15       15           
  Lines        1559     1559           
  Branches      256      256           
=======================================
  Hits         1314     1314           
  Misses        192      192           
  Partials       53       53           

[codspeed-hq]

CodSpeed Performance Report

Merging #123 will not alter performance

_{Comparing dependabot/pip/all-dependencies-e641f77676 (9b9d1a7) with main (ba0dceb)}

Summary

✅ 1 untouched benchmarks

[dependabot]

Superseded by #124.