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 with 10 updates #131

Closed
wants to merge 1 commit into from
Closed

build(deps): bump the patch-and-minor-updates group with 10 updates #131

wants to merge 1 commit into from

Conversation

dependabot[bot]
Copy link

@dependabot dependabot bot commented on behalf of github Apr 22, 2024 •
edited
Loading

Bumps the patch-and-minor-updates group with 10 updates:

Package From To
flask-migrate 4.0.5 4.0.7
sqlalchemy 2.0.25 2.0.29
pluggy 1.4.0 1.5.0
pytest-asyncio 0.23.4 0.23.6
aiohttp 3.9.3 3.9.5
celery 5.3.6 5.4.0
gitpython 3.1.41 3.1.43
kombu 5.3.5 5.3.7
typer 0.9.0 0.12.3
setuptools 69.0.3 69.5.1

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 sqlalchemy from 2.0.25 to 2.0.29

Release notes

Sourced from sqlalchemy's releases.

2.0.29

Released: March 23, 2024

orm

  • [orm] [usecase] Added support for the PEP 695 TypeAliasType construct as well as the python 3.12 native type keyword to work with ORM Annotated Declarative form when using these constructs to link to a PEP 593 Annotated container, allowing the resolution of the Annotated to proceed when these constructs are used in a _orm.Mapped typing container.

    References: #11130

  • [orm] [bug] Fixed Declarative issue where typing a relationship using _orm.Relationship rather than _orm.Mapped would inadvertently pull in the "dynamic" relationship loader strategy for that attribute.

    References: #10611

  • [orm] [bug] Fixed issue in ORM annotated declarative where using _orm.mapped_column() with an _orm.mapped_column.index or _orm.mapped_column.unique setting of False would be overridden by an incoming Annotated element that featured that parameter set to True, even though the immediate _orm.mapped_column() element is more specific and should take precedence. The logic to reconcile the booleans has been enhanced to accommodate a local value of False as still taking precedence over an incoming True value from the annotated element.

    References: #11091

  • [orm] [bug] [regression] Fixed regression from version 2.0.28 caused by the fix for #11085 where the newer method of adjusting post-cache bound parameter values would interefere with the implementation for the _orm.subqueryload() loader option, which has some more legacy patterns in use internally, when the additional loader criteria feature were used with this loader option.

    References: #11173

engine

  • [engine] [bug] Fixed issue in engine_insertmanyvalues feature where using a primary key column with an "inline execute" default generator such as an explicit Sequence with an explcit schema name, while at the same time using the _engine.Connection.execution_options.schema_translate_map

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

Release notes

Sourced from pytest-asyncio's releases.

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
  • c34da04 [docs] Mentioned pytest 8.2 compatibility fix in changelog.
  • 143f745 Fix compatibility with pytest 8.2 FixtureDef.unittest removal
  • 13d4b79 Remove unused function _removesuffix
  • cdd2c49 Use FixtureRequest instead of SubRequest
  • c3429fa Build(deps): Bump packaging from 23.2 to 24.0 in /dependencies/docs
  • 5f2338d Build(deps): Bump pypa/gh-action-pypi-publish from 1.8.12 to 1.8.14
  • 726c6e0 Build(deps): Bump coverage from 7.4.3 to 7.4.4 in /dependencies/default
  • 8bd8288 Build(deps): Bump pytest from 8.0.2 to 8.1.1 in /dependencies/default
  • ef3b347 Build(deps): Bump packaging from 23.2 to 24.0 in /dependencies/default
  • b22d84e [docs] Fixes the example showing how to run all tests in a session-scoped loop.
  • Additional commits viewable in compare view

Updates aiohttp from 3.9.3 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.

3.9.4

Bug fixes

  • The asynchronous internals now set the underlying causes when assigning exceptions to the future objects -- by :user:webknjaz.

    Related issues and pull requests on GitHub: #8089.

  • Treated values of Accept-Encoding header as case-insensitive when checking for gzip files -- by :user:steverep.

... (truncated)

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.

3.9.4 (2024-04-11)

Bug fixes

  • The asynchronous internals now set the underlying causes when assigning exceptions to the future objects -- by :user:webknjaz.

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

... (truncated)

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

... (truncated)

Commits
  • 5364053 bump version to 3.1.43
  • 4e626bd Merge pull request #1886 from EliahKagan/deprecation-warnings
  • f6060df Add GitMeta alias
  • 8327b45 Test GitMeta alias
  • f92f4c3 Clarify security risk in USE_SHELL doc and warnings
  • c7675d2 update security policy, to use GitHub instead of email
  • cf2576e Make/use test.deprecation.lib; abandon idea to filter by module
  • 7cd3aa9 Make test.performance.lib docstring more specific
  • b51b080 Explain the approach in test.deprecation to static checking
  • bdabb21 Expand USE_SHELL docstring; clarify a test usage
  • Additional commits viewable in compare view

Updates kombu from 5.3.5 to 5.3.7

Release notes

Sourced from kombu's releases.

v5.3.7

The release of v5.3.6 was missing the bumbversion commit so v5.3.7 is only released to sync it back.

What's Changed

Full Changelog: celery/kombu@v5.3.6...v5.3.7

v5.3.6

What's Changed

New Contributors

Full Changelog: celery/kombu@v5.3.5...v5.3.6

Changelog

Sourced from kombu's changelog.

5.3.7

:release-date: 11 April, 2024 :release-by: Tomer Nosrati

The release of v5.3.6 was missing the bumbversion commit so v5.3.7 is only released to sync it back.

.. _version-5.3.6:

5.3.6

:release-date: 27 Mar, 2024 :release-by: Tomer Nosrati

  • boto3>=1.26.143 (#1890)
  • Always convert azureservicebus namespace to fully qualified (#1892)
  • Pin pytest-sugar to latest version 1.0.0 (#1912)
  • Upgrade to pytest v8 that removed nose compatibility (#1914)
  • fix warning for usage of utcfromtimestamp (#1926)
  • Update pytest to 8.0.2 (#1942)
  • Hotfix: Fix CI failures (limit redis to <5.0.2 instead of <6.0.0) (#1961)
  • Expose cancel callback from py-amqp channel.basic_consume (#1953)
  • Update mypy to 1.9.0 (#1963)
  • Update pytest to 8.1.1 (#1965)
  • Pin hypothesis to hypothesis<7 (#1966)
  • redis>=4.5.2,=4.5.2,!=5.0.2,!=4.5.5 (#1969)
  • add escape hatch for custom JSON serialization (#1955)
  • Pin pytest-cov to latest version 5.0.0 (#1972)

.. _version-5.3.5:

Commits

@dependabot dependabot bot added dependencies Pull requests that update a dependency file python Pull requests that update Python code labels Apr 22, 2024
@dependabot
build(deps): bump the patch-and-minor-updates group with 10 updates
ac4999d 
Bumps the patch-and-minor-updates group with 10 updates:

| Package | From | To |
| --- | --- | --- |
| [flask-migrate](https://github.com/miguelgrinberg/flask-migrate) | `4.0.5` | `4.0.7` |
| [sqlalchemy](https://github.com/sqlalchemy/sqlalchemy) | `2.0.25` | `2.0.29` |
| [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.6` |
| [aiohttp](https://github.com/aio-libs/aiohttp) | `3.9.3` | `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` |
| [typer](https://github.com/tiangolo/typer) | `0.9.0` | `0.12.3` |
| [setuptools](https://github.com/pypa/setuptools) | `69.0.3` | `69.5.1` |


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 `sqlalchemy` from 2.0.25 to 2.0.29
- [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.6
- [Release notes](https://github.com/pytest-dev/pytest-asyncio/releases)
- [Commits](pytest-dev/pytest-asyncio@v0.23.4...v0.23.6)

Updates `aiohttp` from 3.9.3 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.3...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 `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)

Updates `setuptools` from 69.0.3 to 69.5.1
- [Release notes](https://github.com/pypa/setuptools/releases)
- [Changelog](https://github.com/pypa/setuptools/blob/main/NEWS.rst)
- [Commits](pypa/setuptools@v69.0.3...v69.5.1)

---
updated-dependencies:
- dependency-name: flask-migrate
  dependency-type: direct:production
  update-type: version-update:semver-patch
  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: typer
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: patch-and-minor-updates
- dependency-name: setuptools
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: patch-and-minor-updates
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot force-pushed the dependabot/pip/patch-and-minor-updates-db987e6ad5 branch from 151dfde to ac4999d Compare April 29, 2024 23:46
@dependabot Dependabot
Copy link
Author

dependabot bot commented on behalf of github May 7, 2024

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

@dependabot dependabot bot closed this May 7, 2024
@dependabot dependabot bot deleted the dependabot/pip/patch-and-minor-updates-db987e6ad5 branch May 7, 2024 00:09
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