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.

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

Bump the pip-minor-patch group across 1 directory with 13 updates #189

Closed

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Jul 24, 2024

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

Package From To
uvicorn 0.29.0 0.30.3
sentry-sdk 2.0.1 2.11.0
alembic 1.13.1 1.13.2
icalendar 5.0.12 5.0.13
email-validator 2.1.1 2.2.0
jinja2 3.1.3 3.1.4
redis 5.0.4 5.0.7
flake8 7.0.0 7.1.0
mypy 1.10.0 1.11.0
pytest 8.2.0 8.3.1
coverage 7.5.0 7.6.0
pytest-asyncio 0.23.6 0.23.8
ruff 0.4.2 0.5.4

Updates uvicorn from 0.29.0 to 0.30.3

Release notes

Sourced from uvicorn's releases.

Version 0.30.3

Fixed

  • Suppress KeyboardInterrupt from CLI and programmatic usage (#2384)
  • ClientDisconnect inherits from OSError instead of IOError (#2393)

Full Changelog: encode/uvicorn@0.30.2...0.30.3

0.30.2

Added

Fixed

  • Iterate subprocesses in-place on the process manager (#2373)

Full Changelog: encode/uvicorn@0.30.1...0.30.2

Version 0.30.1

Fixed

  • Allow horizontal tabs \t in response header values (#2345)

Full Changelog: encode/uvicorn@0.30.0...0.30.1

Version 0.30.0

Added

  • New multiprocess manager (#2183)
  • Allow ConfigParser or a io.IO[Any] on log_config (#1976)

Fixed

  • Suppress side effects of signal propagation (#2317)
  • Send content-length header on 5xx (#2304)

Deprecated

  • Deprecate the uvicorn.workers module (#2302)

Full Changelog: encode/uvicorn@0.29.0...0.30.0

Changelog

Sourced from uvicorn's changelog.

0.30.3 (2024-07-20)

Fixed

  • Suppress KeyboardInterrupt from CLI and programmatic usage (#2384)
  • ClientDisconnect inherits from OSError instead of IOError (#2393)

0.30.2 (2024-07-20)

Added

Fixed

  • Iterate subprocesses in-place on the process manager (#2373)

0.30.1 (2024-06-02)

Fixed

  • Allow horizontal tabs \t in response header values (#2345)

0.30.0 (2024-05-28)

Added

  • New multiprocess manager (#2183)
  • Allow ConfigParser or a io.IO[Any] on log_config (#1976)

Fixed

  • Suppress side-effects of signal propagation (#2317)
  • Send content-length header on 5xx (#2304)

Deprecated

  • Deprecate the uvicorn.workers module (#2302)
Commits

Updates sentry-sdk from 2.0.1 to 2.11.0

Release notes

Sourced from sentry-sdk's releases.

2.11.0

Various fixes & improvements

2.10.0

Various fixes & improvements

  • Add client cert and key support to HttpTransport (#3258) by @​grammy-jiang

    Add cert_file and key_file to your sentry_sdk.init to use a custom client cert and key. Alternatively, the environment variables CLIENT_CERT_FILE and CLIENT_KEY_FILE can be used as well.

  • OpenAI: Lazy initialize tiktoken to avoid http at import time (#3287) by @​colin-sentry

  • OpenAI, Langchain: Make tiktoken encoding name configurable + tiktoken usage opt-in (#3289) by @​colin-sentry

... (truncated)

Changelog

Sourced from sentry-sdk's changelog.

2.11.0

Various fixes & improvements

2.10.0

Various fixes & improvements

... (truncated)

Commits

Updates alembic from 1.13.1 to 1.13.2

Release notes

Sourced from alembic's releases.

1.13.2

Released: June 26, 2024

usecase

  • [usecase] [autogenerate] Improve computed column compare function to support multi-line expressions. Pull request courtesy of Georg Wicke-Arndt.

    References: #1391

bug

  • [bug] [commands] Fixed bug in alembic command stdout where long messages were not properly wrapping at the terminal width. Pull request courtesy Saif Hakim.

    References: #1384

  • [bug] [execution] Fixed internal issue where Alembic would call connection.execute() sending an empty tuple to indicate "no params". In SQLAlchemy 2.1 this case will be deprecated as "empty sequence" is ambiguous as to its intent.

    References: #1394

  • [bug] [tests] Fixes to support pytest 8.1 for the test suite.

    References: #1435

  • [bug] [autogenerate] [postgresql] Fixed the detection of serial column in autogenerate with tables not under default schema on PostgreSQL

    References: #1479

Commits

Updates icalendar from 5.0.12 to 5.0.13

Changelog

Sourced from icalendar's changelog.

5.0.13 (2024-06-20)

Minor changes:

  • Guide to delete the build folder before running tests
  • Add funding information
  • Make documentation build with Python 3.12
  • Update windows to olson conversion for Greenland Standard Time
  • Extend examples in Usage with alarm and recurrence
  • Document how to serve the built documentation to view with the browser
  • Improve test coverage

New features:

  • Create GitHub releases for each tag.

Bug fixes:

  • Parse calendars with X-COMMENT properties at the end the file by ignoring these properites
Commits
  • f97722e Merge pull request #632 from niccokunzmann/release
  • 39b0494 version 5.0.13
  • e7ec88d Merge pull request #622 from niccokunzmann/docs-error
  • 4484608 Merge pull request #621 from niccokunzmann/docs-py-12
  • 9862fd1 Merge pull request #628 from raffifu/test/unit_prop
  • d3e432d add test case for unit prop
  • 3a54fe7 Merge pull request #625 from niccokunzmann/docs-http-server
  • f9dad10 log changes
  • 95ccf64 Document how to access the documentation in the browser
  • 4b5cb00 Guide to delete the build folder before testing
  • Additional commits viewable in compare view

Updates email-validator from 2.1.1 to 2.2.0

Release notes

Sourced from email-validator's releases.

2.2.0 (June 20, 2024)

  • Email addresses with internationalized local parts could, with rare Unicode characters, be returned as valid but actually be invalid in their normalized form (returned in the normalized field). Local parts now re-validated after Unicode NFC normalization to ensure that invalid characters cannot be injected into the normalized address and that characters with length-increasing NFC normalizations cannot cause a local part to exceed the maximum length after normalization.
  • The length check for email addresses with internationalized local parts is now also applied to the original address string prior to Unicode NFC normalization, which may be longer and could exceed the maximum email address length, to protect callers who do not use the returned normalized address.
  • Improved error message for IDNA domains that are too long or have invalid characters after Unicode normalization.
  • A new option to parse My Name <address@domain> strings, i.e. a display name plus an email address in angle brackets, is now available. It is off by default.
  • Improvements to Python typing.
  • Some additional tests added.

v2.1.2

2.1.2 (June 16, 2024)

  • The domain name length limit is corrected from 255 to 253 IDNA ASCII characters. I misread the RFCs.
  • When a domain name has no MX record but does have an A or AAAA record, if none of the IP addresses in the response are globally reachable (i.e. not Private-Use, Loopback, etc.), the response is treated as if there was no A/AAAA response and the email address will fail the deliverability check.
  • When a domain name has no MX record but does have an A or AAAA record, the mx field in the object returned by validate_email incorrectly held the IP addresses rather than the domain itself.
  • Fixes in tests.
Changelog

Sourced from email-validator's changelog.

2.2.0 (June 20, 2024)

  • Email addresses with internationalized local parts could, with rare Unicode characters, be returned as valid but actually be invalid in their normalized form (returned in the normalized field). In particular, it is possible to get a normalized address with a ";" character, which is not valid and could change the interpretation of the address. Local parts now re-validated after Unicode NFC normalization to ensure that invalid characters cannot be injected into the normalized address and that characters with length-increasing NFC normalizations cannot cause a local part to exceed the maximum length after normalization. Thanks to khanh@calif.io from https://calif.io for reporting the issue.
  • The length check for email addresses with internationalized local parts is now also applied to the original address string prior to Unicode NFC normalization, which may be longer and could exceed the maximum email address length, to protect callers who do not use the returned normalized address.
  • Improved error message for IDNA domains that are too long or have invalid characters after Unicode normalization.
  • A new option to parse My Name <address@domain> strings, i.e. a display name plus an email address in angle brackets, is now available. It is off by default.
  • Improvements to Python typing.
  • Some additional tests added.

2.1.2 (June 16, 2024)

  • The domain name length limit is corrected from 255 to 253 IDNA ASCII characters. I misread the RFCs.
  • When a domain name has no MX record but does have an A or AAAA record, if none of the IP addresses in the response are globally reachable (i.e. not Private-Use, Loopback, etc.), the response is treated as if there was no A/AAAA response and the email address will fail the deliverability check.
  • When a domain name has no MX record but does have an A or AAAA record, the mx field in the object returned by validate_email incorrectly held the IP addresses rather than the domain itself.
  • Fixes in tests.
Commits
  • 6589b1e Version 2.2.0
  • 8051347 Improve the error message for invalid characters in domain names after Unicod...
  • 7f1f281 Check domain syntax after normalization to internationalized characters as a ...
  • c23c0d6 Improve the error message for IDNA domains being too long by handling the len...
  • 452e0ca Add tests for domain label length
  • f8709e8 Check that email address length is valid on the original email address string...
  • 9ef1f82 Check that the local part is valid after Unicode NFC normalization to prevent...
  • 1fb55d4 Add a test that shows that the local part is returned with Unicode NFC normal...
  • 3426885 Several fixes for parsing display names
  • 0b22c13 Merge point release branch for version 2.1.2
  • Additional commits viewable in compare view

Updates jinja2 from 3.1.3 to 3.1.4

Release notes

Sourced from jinja2's releases.

3.1.4

This is the Jinja 3.1.4 security release, which fixes security issues and bugs but does not otherwise change behavior and should not result in breaking changes.

PyPI: https://pypi.org/project/Jinja2/3.1.4/ Changes: https://jinja.palletsprojects.com/en/3.1.x/changes/#version-3-1-4

  • The xmlattr filter does not allow keys with / solidus, > greater-than sign, or = equals sign, in addition to disallowing spaces. Regardless of any validation done by Jinja, user input should never be used as keys to this filter, or must be separately validated first. GHSA-h75v-3vvj-5mfj
Changelog

Sourced from jinja2's changelog.

Version 3.1.4

Released 2024-05-05

  • The xmlattr filter does not allow keys with / solidus, > greater-than sign, or = equals sign, in addition to disallowing spaces. Regardless of any validation done by Jinja, user input should never be used as keys to this filter, or must be separately validated first. :ghsa:h75v-3vvj-5mfj
Commits

Updates redis from 5.0.4 to 5.0.7

Release notes

Sourced from redis's releases.

5.0.7

Changes

🐛 Bug Fixes

  • None UnixDomainSocket timeout (#3293)

🧰 Maintenance

  • Updated redis version to represent latest available build (#3296)

Contributors

We'd like to thank all the contributors who worked on this release!

@​vladvildanov @​dmaier-redislabs

5.0.6

Changes

🐛 Bug Fixes

  • Handle lists in the response of INFO

5.0.5

Changes

🐛 Bug Fixes

  • Fix parsing of INFO response (#3265)
Commits

Updates flake8 from 7.0.0 to 7.1.0

Commits

Updates mypy from 1.10.0 to 1.11.0

Changelog

Sourced from mypy's changelog.

Mypy Release Notes

Next release

Mypy 1.11

We’ve just uploaded mypy 1.11 to the Python Package Index (PyPI). Mypy is a static type checker for Python. This release includes new features, performance improvements and bug fixes. You can install it as follows:

python3 -m pip install -U mypy

You can read the full documentation for this release on Read the Docs.

Support Python 3.12 Syntax for Generics (PEP 695)

Mypy now supports the new type parameter syntax introduced in Python 3.12 (PEP 695). This feature is still experimental and must be enabled with the --enable-incomplete-feature=NewGenericSyntax flag, or with enable_incomplete_feature = NewGenericSyntax in the mypy configuration file. We plan to enable this by default in the next mypy feature release.

This example demonstrates the new syntax:

# Generic function
def f[T](https://github.com/python/mypy/blob/master/x: T) -> T: ...
reveal_type(f(1))  # Revealed type is 'int'
Generic class
class C[T]:
def init(self, x: T) -> None:
self.x = x
c = C('a')
reveal_type(c.x)  # Revealed type is 'str'
Type alias
type A[T] = C[list[T]]

This feature was contributed by Jukka Lehtosalo.

Support for functools.partial

Mypy now type checks uses of functools.partial. Previously mypy would accept arbitrary arguments.

This example will now produce an error:

from functools import partial
</tr></table> 

... (truncated)

Commits

Updates pytest from 8.2.0 to 8.3.1

Release notes

Sourced from pytest's releases.

8.3.1

pytest 8.3.1 (2024-07-20)

The 8.3.0 release failed to include the change notes and docs for the release. This patch release remedies this. There are no other changes.

8.3.0

pytest 8.3.0 (2024-07-20)

New features

  • #12231: Added [--xfail-tb]{.title-ref} flag, which turns on traceback output for XFAIL results.

    • If the [--xfail-tb]{.title-ref} flag is not given, tracebacks for XFAIL results are NOT shown.
    • The style of traceback for XFAIL is set with [--tb]{.title-ref}, and can be [auto|long|short|line|native|no]{.title-ref}.
    • Note: Even if you have [--xfail-tb]{.title-ref} set, you won't see them if [--tb=no]{.title-ref}.

    Some history:

    With pytest 8.0, [-rx]{.title-ref} or [-ra]{.title-ref} would not only turn on summary reports for xfail, but also report the tracebacks for xfail results. This caused issues with some projects that utilize xfail, but don't want to see all of the xfail tracebacks.

    This change detaches xfail tracebacks from [-rx]{.title-ref}, and now we turn on xfail tracebacks with [--xfail-tb]{.title-ref}. With this, the default [-rx]{.title-ref}/ [-ra]{.title-ref} behavior is identical to pre-8.0 with respect to xfail tracebacks. While this is a behavior change, it brings default behavior back to pre-8.0.0 behavior, which ultimately was considered the better course of action.

  • #12281: Added support for keyword matching in marker expressions.

    Now tests can be selected by marker keyword arguments. Supported values are int{.interpreted-text role="class"}, (unescaped) str{.interpreted-text role="class"}, bool{.interpreted-text role="class"} & None{.interpreted-text role="data"}.

    See marker examples <marker_keyword_expression_example>{.interpreted-text role="ref"} for more information.

    -- by lovetheguitar{.interpreted-text role="user"}

  • #12567: Added --no-fold-skipped command line option.

    If this option is set, then skipped tests in short summary are no longer grouped by reason but all tests are printed individually with their nodeid in the same way as other statuses.

    -- by pbrezina{.interpreted-text role="user"}

Improvements in existing functionality

  • #12469: The console output now uses the "third-party plugins" terminology, replacing the previously established but confusing and outdated reference to setuptools <setuptools:index>{.interpreted-text role="std:doc"} -- by webknjaz{.interpreted-text role="user"}.

  • #12544, #12545: Python virtual environment detection was improved by checking for a pyvenv.cfg{.interpreted-text role="file"} file, ensuring reliable detection on various platforms -- by zachsnickers{.interpreted-text role="user"}.

... (truncated)

Commits
  • de98446 Prepare release version 8.3.1
  • bd0a042 Merge pull request #12636 from pytest-dev/update-release-notes
  • 664325b doc/changelog: update 8.3.0 notes
  • 19d225d Merge pull request #12635 from pytest-dev/release-8.3.0
  • bc33028 Prepare release version 8.3.0
  • a7d5a8e Merge pull request #12557 from x612skm/maintainence/11771-pypy-3.9-bump
  • ced7072 Add a change note for PR #11771
  • d42b76d Adjust test_errors_in_xfail_skip_expressions for PyPy
  • 9eee45a Bump PyPy runtime to v3.9 @ GHA
  • d489247 Fix caching of parameterized fixtures (#12600)
  • Additional commits viewable in compare view

Updates coverage from 7.5.0 to 7.6.0

Changelog

Sourced from coverage's changelog.

Version 7.6.0 — 2024-07-11

  • Exclusion patterns can now be multi-line, thanks to Daniel Diniz <pull 1807_>. This enables many interesting exclusion use-cases, including those requested in issues 118 <issue 118_> (entire files), 996 <issue 996_>_ (multiple lines only when appearing together), 1741 <issue 1741_>_ (remainder of a function), and 1803 <issue 1803_>_ (arbitrary sequence of marked lines). See the :ref:multi_line_exclude section of the docs for more details and examples.

  • The JSON report now includes per-function and per-class coverage information. Thanks to Daniel Diniz <pull 1809_>_ for getting the work started. This closes issue 1793_ and issue 1532_.

  • Fixed an incorrect calculation of "(no class)" lines in the HTML classes report.

  • Python 3.13.0b3 is supported.

.. _issue 118: nedbat/coveragepy#118 .. _issue 996: nedbat/coveragepy#996 .. _issue 1532: nedbat/coveragepy#1532 .. _issue 1741: nedbat/coveragepy#1741 .. _issue 1793: nedbat/coveragepy#1793 .. _issue 1803: nedbat/coveragepy#1803 .. _pull 1807: nedbat/coveragepy#1807 .. _pull 1809: nedbat/coveragepy#1809

.. _changes_7-5-4:

Version 7.5.4 — 2024-06-22

  • If you attempt to combine statement coverage data with branch coverage data, coverage.py used to fail with the message "Can't combine arc data with line data" or its reverse, "Can't combine line data with arc data." These messages used internal terminology, making it hard for people to understand the problem. They are now changed to mention "branch coverage data" and "statement coverage data."

  • Fixed a minor branch coverage problem with wildcard match/case cases using names or guard clauses.

  • Started testing on 3.13 free-threading (nogil) builds of Python. I'm not claiming full support yet. Closes issue 1799_.

.. _issue 1799: nedbat/coveragepy#1799

... (truncated)

Commits
  • 59a3cd7 docs: sample HTML for 7.6.0
  • 7f27fa7 docs: prep for 7.6.0
  • 6a268b0 docs: issues closed by the json region reporting
  • 5bfe9e7 chore: bump actions/setup-python from 5.1.0 to 5.1.1 (#1814)
  • ab609ef docs: mention json region reporting in the changes
  • 92d96b9 fix: json report needs 'no class' and 'no function' also
  • e47e7e7 refactor: move duplicate code into methods
  • 3d6be2b fix: json format should bump for regions
  • a9992d2 test: add a test of json regions with branches
  • 8b89764 test: json expectations should have explicit format number
  • Additional commits viewable in compare view

Updates pytest-asyncio from 0.23.6 to 0.23.8

Release notes

Sourced from pytest-asyncio's releases.

pytest-asyncio 0.23.8

0.23.8 (2024-07-17)

  • Fixes a bug that caused duplicate markers in async tests #813

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

Commits
  • 4be86a5 docs: Prepare release of v0.23.8.
  • 74b3a0a Build(deps): Bump exceptiongroup in /dependencies/default
  • b0009ca [build] Declare support for Python 3.13.
  • c747c7d Build(deps): Bump coverage from 7.5.4 to 7.6.0 in /dependencies/default
  • 5c40a1c Build(deps): Bump hypothesis in /dependencies/default
  • b735e8a build: Remove development dependency on Docker.
  • 91171b4 ci: Test with CPython 3.13.
  • d572138 Build(deps): Bump hypothesis in /dependencies/default
  • a89e4d7 Build(deps): Bump certifi in /dependencies/docs
  • b646cc1 [fix] Fixed a bug that causes markers to be duplicated for async test functions.
  • Additional commits viewable in compare view

Updates ruff from 0.4.2 to 0.5.4

Release notes

Sourced from ruff's releases.

0.5.4

Release Notes

Rule changes

  • [ruff] Rename RUF007 to zip-instead-of-pairwise (#12399)

Bug fixes

  • [flake8-builtins] Avoid shadowing diagnostics for @override methods (

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

| Package | From | To |
| --- | --- | --- |
| [uvicorn](https://github.com/encode/uvicorn) | `0.29.0` | `0.30.3` |
| [sentry-sdk](https://github.com/getsentry/sentry-python) | `2.0.1` | `2.11.0` |
| [alembic](https://github.com/sqlalchemy/alembic) | `1.13.1` | `1.13.2` |
| [icalendar](https://github.com/collective/icalendar) | `5.0.12` | `5.0.13` |
| [email-validator](https://github.com/JoshData/python-email-validator) | `2.1.1` | `2.2.0` |
| [jinja2](https://github.com/pallets/jinja) | `3.1.3` | `3.1.4` |
| [redis](https://github.com/redis/redis-py) | `5.0.4` | `5.0.7` |
| [flake8](https://github.com/pycqa/flake8) | `7.0.0` | `7.1.0` |
| [mypy](https://github.com/python/mypy) | `1.10.0` | `1.11.0` |
| [pytest](https://github.com/pytest-dev/pytest) | `8.2.0` | `8.3.1` |
| [coverage](https://github.com/nedbat/coveragepy) | `7.5.0` | `7.6.0` |
| [pytest-asyncio](https://github.com/pytest-dev/pytest-asyncio) | `0.23.6` | `0.23.8` |
| [ruff](https://github.com/astral-sh/ruff) | `0.4.2` | `0.5.4` |



Updates `uvicorn` from 0.29.0 to 0.30.3
- [Release notes](https://github.com/encode/uvicorn/releases)
- [Changelog](https://github.com/encode/uvicorn/blob/master/CHANGELOG.md)
- [Commits](encode/uvicorn@0.29.0...0.30.3)

Updates `sentry-sdk` from 2.0.1 to 2.11.0
- [Release notes](https://github.com/getsentry/sentry-python/releases)
- [Changelog](https://github.com/getsentry/sentry-python/blob/master/CHANGELOG.md)
- [Commits](getsentry/sentry-python@2.0.1...2.11.0)

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

Updates `icalendar` from 5.0.12 to 5.0.13
- [Release notes](https://github.com/collective/icalendar/releases)
- [Changelog](https://github.com/collective/icalendar/blob/main/CHANGES.rst)
- [Commits](collective/icalendar@v5.0.12...v5.0.13)

Updates `email-validator` from 2.1.1 to 2.2.0
- [Release notes](https://github.com/JoshData/python-email-validator/releases)
- [Changelog](https://github.com/JoshData/python-email-validator/blob/main/CHANGELOG.md)
- [Commits](JoshData/python-email-validator@v2.1.1...v2.2.0)

Updates `jinja2` from 3.1.3 to 3.1.4
- [Release notes](https://github.com/pallets/jinja/releases)
- [Changelog](https://github.com/pallets/jinja/blob/main/CHANGES.rst)
- [Commits](pallets/jinja@3.1.3...3.1.4)

Updates `redis` from 5.0.4 to 5.0.7
- [Release notes](https://github.com/redis/redis-py/releases)
- [Changelog](https://github.com/redis/redis-py/blob/master/CHANGES)
- [Commits](redis/redis-py@v5.0.4...v5.0.7)

Updates `flake8` from 7.0.0 to 7.1.0
- [Commits](PyCQA/flake8@7.0.0...7.1.0)

Updates `mypy` from 1.10.0 to 1.11.0
- [Changelog](https://github.com/python/mypy/blob/master/CHANGELOG.md)
- [Commits](python/mypy@v1.10.0...v1.11)

Updates `pytest` from 8.2.0 to 8.3.1
- [Release notes](https://github.com/pytest-dev/pytest/releases)
- [Changelog](https://github.com/pytest-dev/pytest/blob/main/CHANGELOG.rst)
- [Commits](pytest-dev/pytest@8.2.0...8.3.1)

Updates `coverage` from 7.5.0 to 7.6.0
- [Release notes](https://github.com/nedbat/coveragepy/releases)
- [Changelog](https://github.com/nedbat/coveragepy/blob/master/CHANGES.rst)
- [Commits](nedbat/coveragepy@7.5.0...7.6.0)

Updates `pytest-asyncio` from 0.23.6 to 0.23.8
- [Release notes](https://github.com/pytest-dev/pytest-asyncio/releases)
- [Commits](pytest-dev/pytest-asyncio@v0.23.6...v0.23.8)

Updates `ruff` from 0.4.2 to 0.5.4
- [Release notes](https://github.com/astral-sh/ruff/releases)
- [Changelog](https://github.com/astral-sh/ruff/blob/main/CHANGELOG.md)
- [Commits](astral-sh/ruff@v0.4.2...0.5.4)

---
updated-dependencies:
- dependency-name: uvicorn
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: pip-minor-patch
- dependency-name: sentry-sdk
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: pip-minor-patch
- dependency-name: alembic
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: pip-minor-patch
- dependency-name: icalendar
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: pip-minor-patch
- dependency-name: email-validator
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: pip-minor-patch
- dependency-name: jinja2
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: pip-minor-patch
- dependency-name: redis
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: pip-minor-patch
- dependency-name: flake8
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: pip-minor-patch
- dependency-name: mypy
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: pip-minor-patch
- dependency-name: pytest
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: pip-minor-patch
- dependency-name: coverage
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: pip-minor-patch
- dependency-name: pytest-asyncio
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: pip-minor-patch
- dependency-name: ruff
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: pip-minor-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file python Pull requests that update Python code labels Jul 24, 2024
Copy link
Contributor Author

dependabot bot commented on behalf of github Jul 25, 2024

Superseded by #190.

@dependabot dependabot bot closed this Jul 25, 2024
@dependabot dependabot bot deleted the dependabot/pip/pip-minor-patch-40538b658a branch July 25, 2024 15:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file python Pull requests that update Python code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants