strawberry-graphql / strawberry-sqlalchemy

A SQLAlchemy Integration for strawberry-graphql
MIT License
93 stars 27 forks source link

Bump the all-dependencies group with 3 updates #109

Closed dependabot[bot] closed 10 months ago

dependabot[bot] commented 10 months ago

Bumps the all-dependencies group with 3 updates: sqlalchemy, pytest and pytest-asyncio.

Updates sqlalchemy from 2.0.23 to 2.0.25

Release notes

Sourced from sqlalchemy's releases.

2.0.25

Released: January 2, 2024

orm

  • [orm] [usecase] Added preliminary support for Python 3.12 pep-695 type alias structures, when resolving custom type maps for ORM Annotated Declarative mappings.

    References: #10807

  • [orm] [bug] Fixed issue where when making use of the _orm.relationship.post_update feature at the same time as using a mapper version_id_col could lead to a situation where the second UPDATE statement emitted by the post-update feature would fail to make use of the correct version identifier, assuming an UPDATE was already emitted in that flush which had already bumped the version counter.

    References: #10800

  • [orm] [bug] Fixed issue where ORM Annotated Declarative would mis-interpret the left hand side of a relationship without any collection specified as uselist=True if the left type were given as a class and not a string, without using future-style annotations.

    References: #10815

sql

  • [sql] [bug] Improved compilation of _sql.any_() / _sql.all_() in the context of a negation of boolean comparison, will now render NOT (expr) rather than reversing the equality operator to not equals, allowing finer-grained control of negations for these non-typical operators.

    References: #10817

typing

  • [typing] [bug] Fixed regressions caused by typing added to the sqlalchemy.sql.functions module in version 2.0.24, as part of #6810:

    -   Further enhancements to pep-484 typing to allow SQL functions from
        `_sql.func` derived elements to work more effectively with ORM-mapped
        attributes ([#10801](https://www.sqlalchemy.org/trac/ticket/10801))
    
    • Fixed the argument types passed to functions so that literal expressions

... (truncated)

Commits


Updates pytest from 7.4.3 to 7.4.4

Release notes

Sourced from pytest's releases.

pytest 7.4.4 (2023-12-31)

Bug Fixes

  • #11140: Fix non-string constants at the top of file being detected as docstrings on Python>=3.8.
  • #11572: Handle an edge case where sys.stderr{.interpreted-text role="data"} and sys.__stderr__{.interpreted-text role="data"} might already be closed when faulthandler{.interpreted-text role="ref"} is tearing down.
  • #11710: Fixed tracebacks from collection errors not getting pruned.
  • #7966: Removed unhelpful error message from assertion rewrite mechanism when exceptions are raised in __iter__ methods. Now they are treated un-iterable instead.

Improved Documentation

  • #11091: Updated documentation to refer to hyphenated options: replaced --junitxml with --junit-xml and --collectonly with --collect-only.
Commits
  • 33f694f Prepare release version 7.4.4
  • 76c107c Merge pull request #11751 from bluetech/backport-11143-to-7.4.x
  • 531d76d [7.4.x] Improve reporting from iter exceptions (#11749)
  • a0f58fa Merge pull request #11143 from tushar-deepsource/patch-1
  • b1f3387 [7.4.x] #11091: documentation should use hypthonated properties (#11750)
  • 2cdd619 Merge pull request #11747 from pytest-dev/backport-11711-to-7.4.x
  • d06c05b [7.4.x] nodes: fix tracebacks from collection errors are not getting pruned
  • 5582bfc [7.4.x] Improves clarity in Sphinx documentation for function signature. (#11...
  • 13024ef [7.4.x] Fix for operation on closed file in faulthandler teardown (#11631)
  • a40dacf [7.4.x] XFAIL TestLocalPath.test_make_numbered_dir_multiprocess_safe (#11616)
  • Additional commits viewable in compare view


Updates pytest-asyncio from 0.23.2 to 0.23.3

Release notes

Sourced from pytest-asyncio's releases.

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
  • Fixes various bugs that caused an internal pytest error during test collection #711 #713 #719

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.3a0

0.23.3 (UNRELEASED)

  • 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 #708
  • Fixes a bug that caused an internal pytest error when using unittest.SkipTest in a module #711
Commits
  • 260b791 [docs] Prepare release of v0.23.3.
  • 6a253e2 [docs] Shorten changelog by combining multiple issues.
  • e2cbb90 [docs] Mention correct issue in changelog.
  • 0c522bf [fix] Fixes a bug that caused an internal pytest error when using ImportWarni...
  • 31c7e6f Build(deps): Bump coverage from 7.3.3 to 7.3.4 in /dependencies/default
  • 38d5c7e Build(deps): Bump sphinx-rtd-theme in /dependencies/docs
  • 650ec58 Build(deps): Bump babel from 2.13.1 to 2.14.0 in /dependencies/docs
  • 0166a7e Build(deps): Bump typing-extensions in /dependencies/default
  • 3a15f30 Build(deps): Bump coverage from 7.3.2 to 7.3.3 in /dependencies/default
  • 28e91f0 Build(deps): Bump hypothesis in /dependencies/default
  • 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 ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore 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 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 ` 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 ` will remove all of the ignore conditions of the specified dependency - `@dependabot unignore ` will remove the ignore condition of the specified dependency and ignore conditions
codspeed-hq[bot] commented 10 months ago

CodSpeed Performance Report

Merging #109 will not alter performance

Comparing dependabot/pip/all-dependencies-04a59da9f8 (16ebaf0) with main (ba0dceb)

Summary

✅ 1 untouched benchmarks

dependabot[bot] commented 10 months ago

Looks like these dependencies are updatable in another way, so this is no longer needed.