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

Bump the pip-minor-patch group across 1 directory with 11 updates #196

Closed
wants to merge 1 commit into from
Closed

Bump the pip-minor-patch group across 1 directory with 11 updates #196

wants to merge 1 commit into from

Conversation

dependabot[bot]
Copy link
Contributor

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

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

Package From To
uvicorn 0.29.0 0.30.1
sentry-sdk 2.0.1 2.6.0
email-validator 2.1.1 2.2.0
jinja2 3.1.3 3.1.4
redis 5.0.4 5.0.6
flake8 7.0.0 7.1.0
mypy 1.10.0 1.10.1
pytest 8.2.0 8.2.2
coverage 7.5.0 7.5.4
pytest-asyncio 0.23.6 0.23.7
ruff 0.4.2 0.4.10

Updates uvicorn from 0.29.0 to 0.30.1

Release notes

Sourced from uvicorn's releases.

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

Release notes

Sourced from sentry-sdk's releases.

2.6.0

2.5.1

This change fixes a regression in our cron monitoring feature, which caused cron checkins not to be sent. The regression appears to have been introduced in version 2.4.0.

We recommend that all users, who use Cron monitoring and are currently running sentry-python ≥2.4.0, upgrade to this release as soon as possible!

Other fixes & improvements

2.5.0

Various fixes & improvements

  • Allow to configure status codes to report to Sentry in Starlette and FastAPI (#3008) by @​sentrivana

    By passing a new option to the FastAPI and Starlette integrations, you're now able to configure what status codes should be sent as events to Sentry. Here's how it works:

    from sentry_sdk.integrations.starlette import StarletteIntegration
from sentry_sdk.integrations.fastapi import FastApiIntegration
sentry_sdk.init(
# ...
integrations=[
StarletteIntegration(
failed_request_status_codes=[403, range(500, 599)],
),
FastApiIntegration(
failed_request_status_codes=[403, range(500, 599)],
),
]
)

... (truncated)

Changelog

Sourced from sentry-sdk's changelog.

2.6.0

2.5.1

This change fixes a regression in our cron monitoring feature, which caused cron checkins not to be sent. The regression appears to have been introduced in version 2.4.0.

We recommend that all users, who use Cron monitoring and are currently running sentry-python ≥2.4.0, upgrade to this release as soon as possible!

Other fixes & improvements

2.5.0

Various fixes & improvements

  • Allow to configure status codes to report to Sentry in Starlette and FastAPI (#3008) by @​sentrivana

    By passing a new option to the FastAPI and Starlette integrations, you're now able to configure what status codes should be sent as events to Sentry. Here's how it works:

    from sentry_sdk.integrations.starlette import StarletteIntegration
from sentry_sdk.integrations.fastapi import FastApiIntegration
sentry_sdk.init(
# ...
integrations=[
StarletteIntegration(
failed_request_status_codes=[403, range(500, 599)],
),
FastApiIntegration(
failed_request_status_codes=[403, range(500, 599)],
),

... (truncated)

Commits

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 [email protected] 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.6

Release notes

Sourced from redis's releases.

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

Changelog

Sourced from mypy's changelog.

Mypy 1.10.1

  • Fix error reporting on cached run after uninstallation of third party library (Shantanu, PR 17420)

Acknowledgements

Thanks to all mypy contributors who contributed to this release:

  • Alex Waygood
  • Ali Hamdan
  • Edward Paget
  • Evgeniy Slobodkin
  • Hashem
  • hesam
  • Hugo van Kemenade
  • Ihor
  • James Braza
  • Jelle Zijlstra
  • jhance
  • Jukka Lehtosalo
  • Loïc Simon
  • Marc Mueller
  • Matthieu Devlin
  • Michael R. Crusoe
  • Nikita Sobolev
  • Oskari Lehto
  • Riccardo Di Maio
  • Richard Si
  • roberfi
  • Roman Solomatin
  • Sam Xifaras
  • Shantanu
  • Spencer Brown
  • Srinivas Lade
  • Tamir Duberstein
  • youkaichao

I’d also like to thank my employer, Dropbox, for supporting mypy development.

Mypy 1.9

We’ve just uploaded mypy 1.9 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.

Breaking Changes

Because the version of typeshed we use in mypy 1.9 doesn't support 3.7, neither does mypy 1.9. (Jared Hance, PR 16883)

... (truncated)

Commits
  • c28b525 [1.10 backport] Fix error reporting on cached run after uninstallation of thi...
  • See full diff in compare view

Updates pytest from 8.2.0 to 8.2.2

Release notes

Sourced from pytest's releases.

8.2.2

pytest 8.2.2 (2024-06-04)

Bug Fixes

  • #12355: Fix possible catastrophic performance slowdown on a certain parametrization pattern involving many higher-scoped parameters.
  • #12367: Fix a regression in pytest 8.2.0 where unittest class instances (a fresh one is created for each test) were not released promptly on test teardown but only on session teardown.
  • #12381: Fix possible "Directory not empty" crashes arising from concurent cache dir (.pytest_cache) creation. Regressed in pytest 8.2.0.

Improved Documentation

  • #12290: Updated Sphinx theme to use Furo instead of Flask, enabling Dark mode theme.
  • #12356: Added a subsection to the documentation for debugging flaky tests to mention lack of thread safety in pytest as a possible source of flakyness.
  • #12363: The documentation webpages now links to a canonical version to reduce outdated documentation in search engine results.

8.2.1

pytest 8.2.1 (2024-05-19)

Improvements

  • #12334: Support for Python 3.13 (beta1 at the time of writing).

Bug Fixes

  • #12120: Fix [PermissionError]{.title-ref} crashes arising from directories which are not selected on the command-line.
  • #12191: Keyboard interrupts and system exits are now properly handled during the test collection.
  • #12300: Fixed handling of 'Function not implemented' error under squashfuse_ll, which is a different way to say that the mountpoint is read-only.
  • #12308: Fix a regression in pytest 8.2.0 where the permissions of automatically-created .pytest_cache directories became rwx------ instead of the expected rwxr-xr-x.

Trivial/Internal Changes

  • #12333: pytest releases are now attested using the recent Artifact Attestation support from GitHub, allowing users to verify the provenance of pytest's sdist and wheel artifacts.
Commits
  • 329d371 Prepare release version 8.2.2
  • 214d098 Merge pull request #12414 from bluetech/backport-12409
  • 153a436 [8.2.x] fixtures: fix catastrophic performance problem in reorder_items
  • b41d5a5 Merge pull request #12412 from pytest-dev/backport-12408-to-8.2.x
  • 9bb73d7 [8.2.x] cacheprovider: fix "Directory not empty" crash from cache directory c...
  • 4569a01 [8.2.x] doc: Update trainings/events (#12402)
  • 1d103e5 [8.2.x] Clarify pytest_ignore_collect docs (#12386)
  • 240a252 [8.2.x] Add html_baseurl to sphinx conf.py (#12372)
  • a5ee3c4 Merge pull request #12370 from pytest-dev/backport-12368-to-8.2.x
  • f7358ae [8.2.x] unittest: fix class instances no longer released on test teardown sin...
  • Additional commits viewable in compare view

Updates coverage from 7.5.0 to 7.5.4

Changelog

Sourced from coverage's changelog.

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

.. _changes_7-5-3:

Version 7.5.3 — 2024-05-28

  • Performance improvements for combining data files, especially when measuring line coverage. A few different quadratic behaviors were eliminated. In one extreme case of combining 700+ data files, the time dropped from more than three hours to seven minutes. Thanks for Kraken Tech for funding the fix.

  • Performance improvements for generating HTML reports, with a side benefit of reducing memory use, closing issue 1791_. Thanks to Daniel Diniz for helping to diagnose the problem.

.. _issue 1791: nedbat/coveragepy#1791

.. _changes_7-5-2:

Version 7.5.2 — 2024-05-24

  • Fix: nested matches of exclude patterns could exclude too much code, as reported in issue 1779_. This is now fixed.

  • Changed: previously, coverage.py would consider a module docstring to be an executable statement if it appeared after line 1 in the file, but not executable if it was the first line. Now module docstrings are never counted as executable statements. This can change coverage.py's count of the number of statements in a file, which can slightly change the coverage percentage reported.

... (truncated)

Commits
  • 22c09c6 docs: sample HTML for 7.5.4
  • 9e16381 docs: prep for 7.5.4
  • fba9b9e docs: link issue 1799 from the changelog
  • f124de8 build: no longer download kits to upload them
  • 9516cf6 build: hash-pin all actions
  • c6e0985 build: finish up the publish action
  • 4a49458 build: get the latest dist run id for publishing
  • fb15efa build: pin hashes for publishing actions
  • c20af95 build: use the correct item: github.event.action
  • ccbab15 build: dump all the github actions data
  • Additional commits viewable in compare view

Updates pytest-asyncio from 0.23.6 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.

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 ruff from 0.4.2 to 0.4.10

Release notes

Sourced from ruff's releases.

v0.4.10

Changes

Parser

  • Implement re-lexing logic for better error recovery (#11845)

Rule changes

  • [flake8-copyright] Update CPY001 to check the first 4096 bytes instead of 1024 (#11927)
  • [pycodestyle] Update E999 to show all syntax errors instead of just the first one (#11900)

Server

  • Add tracing setup guide to Helix documentation (#11883)
  • Add tracing setup guide to Neovim documentation (#11884)
  • Defer notebook cell deletion to avoid an error message (#11864)

Security

  • Guard against malicious ecosystem comment artifacts (#11879)

Contributors

v0.4.9

Changes

Preview features

  • [pylint] Implement consider-dict-items (C0206) (#11688)
  • [refurb] Implement repeated-global (FURB154) (#11187)

Rule changes

  • [pycodestyle] Adapt fix for E203 to work identical to ruff format (#10999)

Formatter

  • Fix formatter instability for lines only consisting of zero-width characters (#11748)

Server

... (truncated)

Changelog

Sourced from ruff's changelog.

0.4.10

Parser

  • Implement re-lexing logic for better error recovery (#11845)

Rule changes

  • [flake8-copyright] Update CPY001 to check the first 4096 bytes instead of 1024 (#11927)
  • [pycodestyle] Update E999 to show all syntax errors instead of just the first one (#11900)

Server

  • Add tracing setup guide to Helix documentation (#11883)
  • Add tracing setup guide to Neovim documentation (#11884)
  • Defer notebook cell deletion to avoid an error message (#11864)

Security

  • Guard against malicious ecosystem comment artifacts (#11879)

0.4.9

Preview features

  • [pylint] Implement consider-dict-items (C0206) (#11688)
  • [refurb] Implement repeated-global (FURB154) (#11187)

Rule changes

  • [pycodestyle] Adapt fix for E203 to work identical to ruff format (#10999)

Formatter

  • Fix formatter instability for lines only consisting of zero-width characters (#11748)

Server

  • Add supported commands in server capabilities (#11850)
  • Use real file path when available in ruff server (#11800)
  • Improve error message when a command is run on an unavailable document (#11823)
  • Introduce the ruff.printDebugInformation command (#11831)
  • Tracing system now respects log level and trace level, with options to log to a file (#11747)

CLI

  • Handle non-printable characters in diff view (#11687)

Bug fixes

... (truncated)

Commits

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

@dependabot
Bump the pip-minor-patch group across 1 directory with 11 updates
47ce6de 
Bumps the pip-minor-patch group with 11 updates in the / directory:

| Package | From | To |
| --- | --- | --- |
| [uvicorn](https://github.com/encode/uvicorn) | `0.29.0` | `0.30.1` |
| [sentry-sdk](https://github.com/getsentry/sentry-python) | `2.0.1` | `2.6.0` |
| [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.6` |
| [flake8](https://github.com/pycqa/flake8) | `7.0.0` | `7.1.0` |
| [mypy](https://github.com/python/mypy) | `1.10.0` | `1.10.1` |
| [pytest](https://github.com/pytest-dev/pytest) | `8.2.0` | `8.2.2` |
| [coverage](https://github.com/nedbat/coveragepy) | `7.5.0` | `7.5.4` |
| [pytest-asyncio](https://github.com/pytest-dev/pytest-asyncio) | `0.23.6` | `0.23.7` |
| [ruff](https://github.com/astral-sh/ruff) | `0.4.2` | `0.4.10` |



Updates `uvicorn` from 0.29.0 to 0.30.1
- [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.1)

Updates `sentry-sdk` from 2.0.1 to 2.6.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.6.0)

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

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.10.1
- [Changelog](https://github.com/python/mypy/blob/master/CHANGELOG.md)
- [Commits](python/mypy@v1.10.0...v1.10.1)

Updates `pytest` from 8.2.0 to 8.2.2
- [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.2.2)

Updates `coverage` from 7.5.0 to 7.5.4
- [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.5.4)

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

Updates `ruff` from 0.4.2 to 0.4.10
- [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...v0.4.10)

---
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: 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-patch
  dependency-group: pip-minor-patch
- dependency-name: pytest
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: pip-minor-patch
- dependency-name: coverage
  dependency-type: direct:development
  update-type: version-update:semver-patch
  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-patch
  dependency-group: pip-minor-patch
...

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 25, 2024
@dependabot Dependabot
Copy link
Contributor Author

dependabot bot commented on behalf of github Jun 26, 2024

Superseded by #197.

@dependabot dependabot bot closed this Jun 26, 2024
@dependabot dependabot bot deleted the dependabot/pip/pip-minor-patch-5a37cb5e40 branch June 26, 2024 12:15
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