Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

build(deps): bump the patch-and-minor-updates group across 1 directory with 13 updates #1007

Closed
wants to merge 1 commit into from
Closed

build(deps): bump the patch-and-minor-updates group across 1 directory with 13 updates #1007

wants to merge 1 commit into from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Jun 6, 2024 •
edited
Loading

Bumps the patch-and-minor-updates group with 13 updates in the / directory:

Package From To
flask-migrate 4.0.5 4.0.7
jsonschema 4.21.1 4.22.0
requests 2.31.0 2.32.3
sqlalchemy 2.0.25 2.0.30
pluggy 1.4.0 1.5.0
pytest-asyncio 0.23.4 0.23.7
aiohttp 3.9.4 3.9.5
celery 5.3.6 5.4.0
gitpython 3.1.41 3.1.43
kombu 5.3.5 5.3.7
pydantic 1.10.13 1.10.15
requests-kerberos 0.14.0 0.15.0
typer 0.9.0 0.12.3

Updates flask-migrate from 4.0.5 to 4.0.7

Release notes

Sourced from flask-migrate's releases.

Release 4.0.7

See CHANGES.md for release notes.

Release 4.0.6

See CHANGES.md for release notes.

Changelog

Sourced from flask-migrate's changelog.

Flask-Migrate Change Log

Release 4.0.7 - 2024-03-11

  • Regression from #438: check g.x_arg exists before accessing it #541 (commit) (thanks Skye Im!)

Release 4.0.6 - 2024-03-09

  • Accept -x options for all db commands #438 (commit)
  • Add --purge flag to the stamp command #540 (commit) (thanks Jono N!)

Release 4.0.5 - 2023-09-12

  • Compatiblity fixes for Flask-SQLAlchemy >= 3.1 #526 (commit) (thanks David Lord!)
  • Allow process_revision_directives option to be configurable #523 (commit) (thanks llc!)
  • Stop testing Python 3.7, as Flask-SQLAlchemy 3.1 stopped supporting it (commit)

Release 4.0.4 - 2023-02-02

  • Correctly obtain database URL with SQLAlchemy 2.0 #505 (commit)

Release 4.0.3 - 2023-01-29

  • Remove legacy future import in Alembic templates #504 (commit) (thanks Pamela Fox!)
  • Add SQLAlchemy 1.4 and 2.0 to the test matrix (commit)
  • Switch to pytest as test runner (commit)

Release 4.0.2 - 2023-01-18

  • Support "check" command #502 (commit) (thanks Masamitsu MURASE!)

Release 4.0.1 - 2023-01-05

  • Do not use deprecated functions in Flask-SQLAlchemy 3.0 (commit)
  • Stop building Python 3.6 (commit)
  • Remove tests from pypi package (commit)

Release 4.0.0 - 2022-11-13

  • Updates for Flask-SQLAlchemy 3.x compatiblity (commit)
  • Enable type comparison and batch mode by default (commit)
  • Option to rename "db" command group to a custom name (commit)
  • Better handling of MetaData instances in templates (commit)
  • Set options correctly when revision --autogenerate is used #463 (commit) (thanks Frazer McLean!)
  • Documentation section on configuring Alembic (commit)
  • Upgrade build to pypy-3.9 (commit)
  • Add Python 3.10 to build (commit)
  • Add Python 3.11 to build (commit)
  • Specify license in project metadata #489 (commit) (thanks Frazer McLean!)
  • Remove tests from pypi package (commit)

... (truncated)

Commits

Updates jsonschema from 4.21.1 to 4.22.0

Release notes

Sourced from jsonschema's releases.

v4.22.0

What's Changed

  • Improve best_match (and thereby error messages from jsonschema.validate) in cases where there are multiple sibling errors from applying anyOf / allOf -- i.e. when multiple elements of a JSON array have errors, we now do prefer showing errors from earlier elements rather than simply showing an error for the full array (#1250).
  • (Micro-)optimize equality checks when comparing for JSON Schema equality by first checking for object identity, as == would.

New Contributors

Full Changelog: python-jsonschema/jsonschema@v4.21.1...v4.22.0

Changelog

Sourced from jsonschema's changelog.

v4.22.0

  • Improve best_match (and thereby error messages from jsonschema.validate) in cases where there are multiple sibling errors from applying anyOf / allOf -- i.e. when multiple elements of a JSON array have errors, we now do prefer showing errors from earlier elements rather than simply showing an error for the full array (#1250).
  • (Micro-)optimize equality checks when comparing for JSON Schema equality by first checking for object identity, as == would.
Commits
  • 9882dbe Add / ignore the new specification test suite property.
  • ebc90bb Merge commit '8fcfc3a674a7188a4fcc822b7a91efb3e0422a20'
  • 8fcfc3a Squashed 'json/' changes from b41167c74..54f3784a8
  • 30b7537 Pin pyenchant to pre from below until pyenchant/pyenchant#302 is released.
  • c3729db Enable doctests for the rest of the referencing page.
  • 70a994c Remove a now-unneeded noqa since apparently this is fixed in new ruff.
  • e6d0ef1 Fix a minor typo in the referencing example docs.
  • bceaf41 Another placeholder benchmark for future optimization.
  • b20234e Consider errors from earlier indices (in instances) to be better matches
  • 41b49c6 Minor improvement to test failure message when a best match test fails.
  • Additional commits viewable in compare view

Updates requests from 2.31.0 to 2.32.3

Release notes

Sourced from requests's releases.

v2.32.3

2.32.3 (2024-05-29)

Bugfixes

  • Fixed bug breaking the ability to specify custom SSLContexts in sub-classes of HTTPAdapter. (#6716)
  • Fixed issue where Requests started failing to run on Python versions compiled without the ssl module. (#6724)

v2.32.2

2.32.2 (2024-05-21)

Deprecations

  • To provide a more stable migration for custom HTTPAdapters impacted by the CVE changes in 2.32.0, we've renamed _get_connection to a new public API, get_connection_with_tls_context. Existing custom HTTPAdapters will need to migrate their code to use this new API. get_connection is considered deprecated in all versions of Requests>=2.32.0.

    A minimal (2-line) example has been provided in the linked PR to ease migration, but we strongly urge users to evaluate if their custom adapter is subject to the same issue described in CVE-2024-35195. (#6710)

v2.32.1

2.32.1 (2024-05-20)

Bugfixes

  • Add missing test certs to the sdist distributed on PyPI.

v2.32.0

2.32.0 (2024-05-20)

🐍 PYCON US 2024 EDITION 🐍

Security

  • Fixed an issue where setting verify=False on the first request from a Session will cause subsequent requests to the same origin to also ignore cert verification, regardless of the value of verify. (GHSA-9wx4-h78v-vm56)

Improvements

  • verify=True now reuses a global SSLContext which should improve request time variance between first and subsequent requests. It should also minimize certificate load time on Windows systems when using a Python version built with OpenSSL 3.x. (#6667)
  • Requests now supports optional use of character detection (chardet or charset_normalizer) when repackaged or vendored.

... (truncated)

Changelog

Sourced from requests's changelog.

2.32.3 (2024-05-29)

Bugfixes

  • Fixed bug breaking the ability to specify custom SSLContexts in sub-classes of HTTPAdapter. (#6716)
  • Fixed issue where Requests started failing to run on Python versions compiled without the ssl module. (#6724)

2.32.2 (2024-05-21)

Deprecations

  • To provide a more stable migration for custom HTTPAdapters impacted by the CVE changes in 2.32.0, we've renamed _get_connection to a new public API, get_connection_with_tls_context. Existing custom HTTPAdapters will need to migrate their code to use this new API. get_connection is considered deprecated in all versions of Requests>=2.32.0.

    A minimal (2-line) example has been provided in the linked PR to ease migration, but we strongly urge users to evaluate if their custom adapter is subject to the same issue described in CVE-2024-35195. (#6710)

2.32.1 (2024-05-20)

Bugfixes

  • Add missing test certs to the sdist distributed on PyPI.

2.32.0 (2024-05-20)

Security

  • Fixed an issue where setting verify=False on the first request from a Session will cause subsequent requests to the same origin to also ignore cert verification, regardless of the value of verify. (GHSA-9wx4-h78v-vm56)

Improvements

  • verify=True now reuses a global SSLContext which should improve request time variance between first and subsequent requests. It should also minimize certificate load time on Windows systems when using a Python version built with OpenSSL 3.x. (#6667)
  • Requests now supports optional use of character detection (chardet or charset_normalizer) when repackaged or vendored. This enables pip and other projects to minimize their vendoring surface area. The Response.text() and apparent_encoding APIs will default to utf-8 if neither library is present. (#6702)

... (truncated)

Commits
  • 0e322af v2.32.3
  • e188799 Don't create default SSLContext if ssl module isn't present (#6724)
  • 145b539 Merge pull request #6716 from sigmavirus24/bug/6715
  • b1d73dd Don't use default SSLContext with custom poolmanager kwargs
  • 6badbac Update HISTORY.md
  • a62a2d3 Allow for overriding of specific pool key params
  • 88dce9d v2.32.2
  • c98e4d1 Merge pull request #6710 from nateprewitt/api_rename
  • 92075b3 Add deprecation warning
  • aa1461b Move _get_connection to get_connection_with_tls_context
  • Additional commits viewable in compare view

Updates sqlalchemy from 2.0.25 to 2.0.30

Release notes

Sourced from sqlalchemy's releases.

2.0.30

Released: May 5, 2024

orm

  • [orm] [bug] Added new attribute _orm.ORMExecuteState.is_from_statement to detect statements created using _sql.Select.from_statement(), and enhanced FromStatement to set _orm.ORMExecuteState.is_select, _orm.ORMExecuteState.is_insert, _orm.ORMExecuteState.is_update, and _orm.ORMExecuteState.is_delete according to the element that is sent to the _sql.Select.from_statement() method itself.

    References: #11220

  • [orm] [bug] Fixed issue in _orm.selectin_polymorphic() loader option where attributes defined with _orm.composite() on a superclass would cause an internal exception on load.

    References: #11291

  • [orm] [bug] [regression] Fixed regression from 1.4 where using _orm.defaultload() in conjunction with a non-propagating loader like _orm.contains_eager() would nonetheless propagate the _orm.contains_eager() to a lazy load operation, causing incorrect queries as this option is only intended to come from an original load.

    References: #11292

  • [orm] [bug] Fixed issue in ORM Annotated Declarative where typing issue where literals defined using PEP 695 type aliases would not work with inference of Enum datatypes. Pull request courtesy of Alc-Alc.

    References: #11305

  • [orm] [bug] Fixed issue in _orm.selectin_polymorphic() loader option where the SELECT emitted would only accommodate for the child-most class among the result rows that were returned, leading intermediary-class attributes to be unloaded if there were no concrete instances of that intermediary-class present in the result. This issue only presented itself for multi-level inheritance hierarchies.

    References: #11327

  • [orm] [bug] Fixed issue in _orm.Session.bulk_save_objects() where the form of the identity key produced when using return_defaults=True would be incorrect. This could lead to an errors during pickling as well as identity map mismatches.

... (truncated)

Commits

Updates pluggy from 1.4.0 to 1.5.0

Changelog

Sourced from pluggy's changelog.

pluggy 1.5.0 (2024-04-19)

Features

  • [#178](https://github.com/pytest-dev/pluggy/issues/178) <https://github.com/pytest-dev/pluggy/issues/178>_: Add support for deprecating specific hook parameters, or more generally, for issuing a warning whenever a hook implementation requests certain parameters.

    See :ref:warn_on_impl for details.

Bug Fixes

  • [#481](https://github.com/pytest-dev/pluggy/issues/481) <https://github.com/pytest-dev/pluggy/issues/481>_: PluginManager.get_plugins() no longer returns None for blocked plugins.
Commits
  • f8aa4a0 Preparing release 1.5.0
  • b4a8c92 Merge pull request #495 from bluetech/warn-on-impl-args
  • 6f6ea68 Add support deprecating hook parameters
  • 91f88d2 Merge pull request #496 from bluetech/codecov-action
  • 89ce829 ci: replace upload-coverage script with codecov github action
  • 29f104d Lift pluggy (#493)
  • c2b36b4 Merge pull request #491 from pytest-dev/pre-commit-ci-update-config
  • 2b533c9 [pre-commit.ci] pre-commit autoupdate
  • 04d1bcd [pre-commit.ci] pre-commit autoupdate (#490)
  • f74e94b [pre-commit.ci] pre-commit autoupdate (#489)
  • Additional commits viewable in compare view

Updates pytest-asyncio from 0.23.4 to 0.23.7

Release notes

Sourced from pytest-asyncio's releases.

pytest-asyncio 0.23.7

0.23.7 (2024-05-19)

  • Silence deprecation warnings about unclosed event loops that occurred with certain CPython patch releases #817

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.6

0.23.6 (2024-03-19)

  • Fix compatibility with pytest 8.2 #800

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.5.post1

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

Commits
  • eb63d5a docs: Prepared for release of v0.23.7.
  • da04a7a Build(deps): Bump exceptiongroup in /dependencies/default
  • 00c667a Build(deps): Bump pytest from 8.1.1 to 8.2.0 in /dependencies/default
  • 3bd9cd8 [docs] Add changelog entry.
  • 15544f0 Revert GitHub Actions and Tox changes.
  • 6316b28 Deduplicate simplefilter snippet.
  • 3ffdfc5 asyncio.run(port_afinalizer())
  • 0107fd7 Remove extra space.
  • 3bf700a Fix GH Action mapping.
  • d15dc31 Fix 3109/3108 typo.
  • Additional commits viewable in compare view

Updates aiohttp from 3.9.4 to 3.9.5

Release notes

Sourced from aiohttp's releases.

3.9.5

Bug fixes

  • Fixed "Unclosed client session" when initialization of :py:class:~aiohttp.ClientSession fails -- by :user:NewGlad.

    Related issues and pull requests on GitHub: #8253.

  • Fixed regression (from :pr:8280) with adding Content-Disposition to the form-data part after appending to writer -- by :user:Dreamsorcerer/:user:Olegt0rr.

    Related issues and pull requests on GitHub: #8332.

  • Added default Content-Disposition in multipart/form-data responses to avoid broken form-data responses -- by :user:Dreamsorcerer.

    Related issues and pull requests on GitHub: #8335.

Changelog

Sourced from aiohttp's changelog.

3.9.5 (2024-04-16)

Bug fixes

  • Fixed "Unclosed client session" when initialization of :py:class:~aiohttp.ClientSession fails -- by :user:NewGlad.

    Related issues and pull requests on GitHub: :issue:8253.

  • Fixed regression (from :pr:8280) with adding Content-Disposition to the form-data part after appending to writer -- by :user:Dreamsorcerer/:user:Olegt0rr.

    Related issues and pull requests on GitHub: :issue:8332.

  • Added default Content-Disposition in multipart/form-data responses to avoid broken form-data responses -- by :user:Dreamsorcerer.

    Related issues and pull requests on GitHub: :issue:8335.

Commits

Updates celery from 5.3.6 to 5.4.0

Release notes

Sourced from celery's releases.

v5.4.0

Celery v5.4.0 and v5.3.x have consistently focused on enhancing the overall QA, both internally and externally. This effort led to the new pytest-celery v1.0.0 release, developed concurrently with v5.3.0 & v5.4.0.

This release introduces two significant QA enhancements:

  • Smoke Tests: A new layer of automatic tests has been added to Celery's standard CI. These tests are designed to handle production scenarios and complex conditions efficiently. While new contributions will not be halted due to the lack of smoke tests, we will request smoke tests for advanced changes where appropriate.
  • Standalone Bug Report Script: The new pytest-celery plugin now allows for encapsulating a complete Celery dockerized setup within a single pytest script. Incorporating these into new bug reports will enable us to reproduce reported bugs deterministically, potentially speeding up the resolution process.

Contrary to the positive developments above, there have been numerous reports about issues with the Redis broker malfunctioning upon restarts and disconnections. Our initial attempts to resolve this were not successful (#8796). With our enhanced QA capabilities, we are now prepared to address the core issue with Redis (as a broker) again.

The rest of the changes for this release are grouped below, with the changes from the latest release candidate listed at the end.

What's Changed

  • Add a Task class specialised for Django (#8491)
  • Add Google Cloud Storage (GCS) backend (#8868)
  • Added documentation to the smoke tests infra (#8970)
  • Added a checklist item for using pytest-celery in a bug report (#8971)
  • Bugfix: Missing id on chain (#8798)
  • Bugfix: Worker not consuming tasks after Redis broker restart (#8796)
  • Catch UnicodeDecodeError when opening corrupt beat-schedule.db (#8806)
  • chore(ci): Enhance CI with workflow_dispatch for targeted debugging and testing (#8826)
  • Doc: Enhance "Testing with Celery" section (#8955)
  • Docfix: pip install celery[sqs] -> pip install "celery[sqs]" (#8829)
  • Enable efficient chord when using dynamicdb as backend store (#8783)
  • feat(daemon): allows daemonization options to be fetched from app settings (#8553)
  • Fix DeprecationWarning: datetime.datetime.utcnow() (#8726)
  • Fix recursive result parents on group in middle of chain (#8903)
  • Fix typos and grammar (#8915)
  • Fixed version documentation tag from #8553 in configuration.rst (#8802)
  • Hotfix: Smoke tests didn't allow customizing the worker's command arguments, now it does (#8937)
  • Make custom remote control commands available in CLI (#8489)
  • Print safe_say() to stdout for non-error flows (#8919)
  • Support moto 5.0 (#8838)
  • Update contributing guide to use ssh upstream url (#8881)
  • Update optimizing.rst (#8945)
  • Updated concurrency docs page. (#8753)

Dependencies Updates

  • Bump actions/setup-python from 4 to 5 (#8701)
  • Bump codecov/codecov-action from 3 to 4 (#8831)
  • Bump isort from 5.12.0 to 5.13.2 (#8772)
  • Bump msgpack from 1.0.7 to 1.0.8 (#8885)
  • Bump mypy from 1.8.0 to 1.9.0 (#8898)
  • Bump pre-commit to 3.6.1 (#8839)
  • Bump pre-commit/action from 3.0.0 to 3.0.1 (#8835)
  • Bump pytest from 8.0.2 to 8.1.1 (#8901)
  • Bump pytest-celery to v1.0.0 (#8962)
  • Bump pytest-cov to 5.0.0 (#8924)

... (truncated)

Changelog

Sourced from celery's changelog.

5.4.0

:release-date: 2024-04-17 :release-by: Tomer Nosrati

Celery v5.4.0 and v5.3.x have consistently focused on enhancing the overall QA, both internally and externally. This effort led to the new pytest-celery v1.0.0 release, developed concurrently with v5.3.0 & v5.4.0.

This release introduces two significant QA enhancements:

  • Smoke Tests: A new layer of automatic tests has been added to Celery's standard CI. These tests are designed to handle production scenarios and complex conditions efficiently. While new contributions will not be halted due to the lack of smoke tests, we will request smoke tests for advanced changes where appropriate.
  • Standalone Bug Report Script <https://docs.celeryq.dev/projects/pytest-celery/en/latest/userguide/celery-bug-report.html>_: The new pytest-celery plugin now allows for encapsulating a complete Celery dockerized setup within a single pytest script. Incorporating these into new bug reports will enable us to reproduce reported bugs deterministically, potentially speeding up the resolution process.

Contrary to the positive developments above, there have been numerous reports about issues with the Redis broker malfunctioning upon restarts and disconnections. Our initial attempts to resolve this were not successful (#8796). With our enhanced QA capabilities, we are now prepared to address the core issue with Redis (as a broker) again.

The rest of the changes for this release are grouped below, with the changes from the latest release candidate listed at the end.

Changes

  • Add a Task class specialised for Django (#8491)
  • Add Google Cloud Storage (GCS) backend (#8868)
  • Added documentation to the smoke tests infra (#8970)
  • Added a checklist item for using pytest-celery in a bug report (#8971)
  • Bugfix: Missing id on chain (#8798)
  • Bugfix: Worker not consuming tasks after Redis broker restart (#8796)
  • Catch UnicodeDecodeError when opening corrupt beat-schedule.db (#8806)
  • chore(ci): Enhance CI with workflow_dispatch for targeted debugging and testing (#8826)
  • Doc: Enhance "Testing with Celery" section (#8955)
  • Docfix: pip install celery[sqs] -> pip install "celery[sqs]" (#8829)
  • Enable efficient chord when using dynamicdb as backend store (#8783)
  • feat(daemon): allows daemonization options to be fetched from app settings (#8553)
  • Fix DeprecationWarning: datetime.datetime.utcnow() (#8726)
  • Fix recursive result parents on group in middle of chain (#8903)
  • Fix typos and grammar (#8915)
  • Fixed version documentation tag from #8553 in configuration.rst (#8802)
  • Hotfix: Smoke tests didn't allow customizing the worker's command arguments, now it does (#8937)
  • Make custom remote control commands available in CLI (#8489)
  • Print safe_say() to stdout for non-error flows (#8919)
  • Support moto 5.0 (#8838)
  • Update contributing guide to use ssh upstream url (#8881)
  • Update optimizing.rst (#8945)
  • Updated concurrency docs page. (#8753)

Dependencies Updates

  • Bump actions/setup-python from 4 to 5 (#8701)
  • Bump codecov/codecov-action from 3 to 4 (#8831)

... (truncated)

Commits

Updates gitpython from 3.1.41 to 3.1.43

Release notes

Sourced from gitpython's releases.

3.1.43

Particularly Important Changes

These are likely to affect you, please do take a careful look.

Other Changes

New Contributors

Full Changelog: gitpython-developers/GitPython@3.1.42...3.1.43

3.1.42

What's Changed

@dependabot
build(deps): bump the patch-and-minor-updates group across 1 director…
45c4928 
…y with 13 updates

Bumps the patch-and-minor-updates group with 13 updates in the / directory:

| Package | From | To |
| --- | --- | --- |
| [flask-migrate](https://github.com/miguelgrinberg/flask-migrate) | `4.0.5` | `4.0.7` |
| [jsonschema](https://github.com/python-jsonschema/jsonschema) | `4.21.1` | `4.22.0` |
| [requests](https://github.com/psf/requests) | `2.31.0` | `2.32.3` |
| [sqlalchemy](https://github.com/sqlalchemy/sqlalchemy) | `2.0.25` | `2.0.30` |
| [pluggy](https://github.com/pytest-dev/pluggy) | `1.4.0` | `1.5.0` |
| [pytest-asyncio](https://github.com/pytest-dev/pytest-asyncio) | `0.23.4` | `0.23.7` |
| [aiohttp](https://github.com/aio-libs/aiohttp) | `3.9.4` | `3.9.5` |
| [celery](https://github.com/celery/celery) | `5.3.6` | `5.4.0` |
| [gitpython](https://github.com/gitpython-developers/GitPython) | `3.1.41` | `3.1.43` |
| [kombu](https://github.com/celery/kombu) | `5.3.5` | `5.3.7` |
| [pydantic](https://github.com/pydantic/pydantic) | `1.10.13` | `1.10.15` |
| [requests-kerberos](https://github.com/requests/requests-kerberos) | `0.14.0` | `0.15.0` |
| [typer](https://github.com/tiangolo/typer) | `0.9.0` | `0.12.3` |



Updates `flask-migrate` from 4.0.5 to 4.0.7
- [Release notes](https://github.com/miguelgrinberg/flask-migrate/releases)
- [Changelog](https://github.com/miguelgrinberg/Flask-Migrate/blob/main/CHANGES.md)
- [Commits](miguelgrinberg/Flask-Migrate@v4.0.5...v4.0.7)

Updates `jsonschema` from 4.21.1 to 4.22.0
- [Release notes](https://github.com/python-jsonschema/jsonschema/releases)
- [Changelog](https://github.com/python-jsonschema/jsonschema/blob/main/CHANGELOG.rst)
- [Commits](python-jsonschema/jsonschema@v4.21.1...v4.22.0)

Updates `requests` from 2.31.0 to 2.32.3
- [Release notes](https://github.com/psf/requests/releases)
- [Changelog](https://github.com/psf/requests/blob/main/HISTORY.md)
- [Commits](psf/requests@v2.31.0...v2.32.3)

Updates `sqlalchemy` from 2.0.25 to 2.0.30
- [Release notes](https://github.com/sqlalchemy/sqlalchemy/releases)
- [Changelog](https://github.com/sqlalchemy/sqlalchemy/blob/main/CHANGES.rst)
- [Commits](https://github.com/sqlalchemy/sqlalchemy/commits)

Updates `pluggy` from 1.4.0 to 1.5.0
- [Changelog](https://github.com/pytest-dev/pluggy/blob/main/CHANGELOG.rst)
- [Commits](pytest-dev/pluggy@1.4.0...1.5.0)

Updates `pytest-asyncio` from 0.23.4 to 0.23.7
- [Release notes](https://github.com/pytest-dev/pytest-asyncio/releases)
- [Commits](pytest-dev/pytest-asyncio@v0.23.4...v0.23.7)

Updates `aiohttp` from 3.9.4 to 3.9.5
- [Release notes](https://github.com/aio-libs/aiohttp/releases)
- [Changelog](https://github.com/aio-libs/aiohttp/blob/master/CHANGES.rst)
- [Commits](aio-libs/aiohttp@v3.9.4...v3.9.5)

Updates `celery` from 5.3.6 to 5.4.0
- [Release notes](https://github.com/celery/celery/releases)
- [Changelog](https://github.com/celery/celery/blob/main/Changelog.rst)
- [Commits](celery/celery@v5.3.6...v5.4.0)

Updates `gitpython` from 3.1.41 to 3.1.43
- [Release notes](https://github.com/gitpython-developers/GitPython/releases)
- [Changelog](https://github.com/gitpython-developers/GitPython/blob/main/CHANGES)
- [Commits](gitpython-developers/GitPython@3.1.41...3.1.43)

Updates `kombu` from 5.3.5 to 5.3.7
- [Release notes](https://github.com/celery/kombu/releases)
- [Changelog](https://github.com/celery/kombu/blob/main/Changelog.rst)
- [Commits](celery/kombu@v5.3.5...v5.3.7)

Updates `pydantic` from 1.10.13 to 1.10.15
- [Release notes](https://github.com/pydantic/pydantic/releases)
- [Changelog](https://github.com/pydantic/pydantic/blob/main/HISTORY.md)
- [Commits](pydantic/pydantic@v1.10.13...v1.10.15)

Updates `requests-kerberos` from 0.14.0 to 0.15.0
- [Release notes](https://github.com/requests/requests-kerberos/releases)
- [Changelog](https://github.com/requests/requests-kerberos/blob/master/HISTORY.rst)
- [Commits](requests/requests-kerberos@v0.14.0...v0.15.0)

Updates `typer` from 0.9.0 to 0.12.3
- [Release notes](https://github.com/tiangolo/typer/releases)
- [Changelog](https://github.com/tiangolo/typer/blob/master/docs/release-notes.md)
- [Commits](fastapi/typer@0.9.0...0.12.3)

---
updated-dependencies:
- dependency-name: flask-migrate
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: patch-and-minor-updates
- dependency-name: jsonschema
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: patch-and-minor-updates
- dependency-name: requests
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: patch-and-minor-updates
- dependency-name: sqlalchemy
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: patch-and-minor-updates
- dependency-name: pluggy
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: patch-and-minor-updates
- dependency-name: pytest-asyncio
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: patch-and-minor-updates
- dependency-name: aiohttp
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: patch-and-minor-updates
- dependency-name: celery
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: patch-and-minor-updates
- dependency-name: gitpython
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: patch-and-minor-updates
- dependency-name: kombu
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: patch-and-minor-updates
- dependency-name: pydantic
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: patch-and-minor-updates
- dependency-name: requests-kerberos
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: patch-and-minor-updates
- dependency-name: typer
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: patch-and-minor-updates
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file python Pull requests that update Python code labels Jun 6, 2024
@dependabot Dependabot
Copy link
Contributor Author

dependabot bot commented on behalf of github Jun 10, 2024

Dependabot tried to update this pull request, but something went wrong. We're looking into it, but in the meantime you can retry the update by commenting @dependabot rebase.

@dependabot Dependabot
Copy link
Contributor Author

dependabot bot commented on behalf of github Jun 17, 2024

Superseded by #1008.

@dependabot dependabot bot closed this Jun 17, 2024
@dependabot dependabot bot deleted the dependabot/pip/patch-and-minor-updates-997d193415 branch June 17, 2024 21:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
dependencies Pull requests that update a dependency file python Pull requests that update Python code
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants