Bump the allpip group across 1 directory with 5 updates

[dependabot]

Bumps the allpip group with 5 updates in the / directory:

Package	From	To
uvicorn	0.30.6	0.31.0
fastapi-csrf-protect	0.3.4	0.3.5
pytest-httpx	0.31.2	0.32.0
ruff	0.6.7	0.6.8
pyright	1.1.381	1.1.382.post1

Updates uvicorn from 0.30.6 to 0.31.0

Release notes

Sourced from uvicorn's releases.

Version 0.31.0

Added

Improve ProxyHeadersMiddleware (#2468) and (#2231):

• Fix the host for requests from clients running on the proxy server itself.
• Fallback to host that was already set for empty x-forwarded-for headers.
• Also allow specifying IP Networks as trusted hosts. This greatly simplifies deployments on docker swarm/Kubernetes, where the reverse proxy might have a dynamic IP.
  • This includes support for IPv6 Address/Networks.

---

Full Changelog: encode/uvicorn@0.30.6...0.31.0

Changelog

Sourced from uvicorn's changelog.

0.31.0 (2024-09-27)

Added

Improve ProxyHeadersMiddleware (#2468) and (#2231):

• Fix the host for requests from clients running on the proxy server itself.
• Fallback to host that was already set for empty x-forwarded-for headers.
• Also allow to specify IP Networks as trusted hosts. This greatly simplifies deployments on docker swarm/kubernetes, where the reverse proxy might have a dynamic IP.
  • This includes support for IPv6 Address/Networks.

Commits

• a507532 Version 0.31.0 (#2469)
• 84dd2c4 Improve ProxyHeadersMiddleware (#2468)
• 3d26ab4 Bump cryptography from 42.0.8 to 43.0.1 (#2453)
• 47304d9 Add tests and requirements.txt to sdist (#2438)
• 1cb0c32 Add missing init files in the test suite (#2432)
• See full diff in compare view

Updates fastapi-csrf-protect from 0.3.4 to 0.3.5

Commits

• See full diff in compare view

Updates pytest-httpx from 0.31.2 to 0.32.0

Release notes

Sourced from pytest-httpx's releases.

0.32.0 (2024-09-27)

Added

• The following option is now available:
  • can_send_already_matched_responses (boolean), defaulting to False.
• Assertion failure message in case of unmatched responses is now linking documentation on how to deactivate the check.
• Assertion failure message in case of unmatched requests is now linking documentation on how to deactivate the check.
• httpx.TimeoutException message issued in case of unmatched request is now linking documentation on how to reuse responses (in case some responses are already matched).

Fixed

• Documentation now clearly state the risks associated with changing the default options.
• Assertion failure message in case of unmatched requests at teardown is now describing requests in a more user-friendly way.
• Assertion failure message in case of unmatched requests at teardown is now prefixing requests with - to highlight the fact that this is a list, preventing misapprehension in case only one element exists.
• Assertion failure message in case of unmatched responses at teardown is now prefixing responses with - to highlight the fact that this is a list, preventing misapprehension in case only one element exists.
• httpx.TimeoutException message issued in case of unmatched request is now prefixing available responses with - to highlight the fact that this is a list, preventing misapprehension in case only one element exists.
• httpx.TimeoutException message issued in case of unmatched request is now listing unmatched responses (in registration order) before already matched one (still in registration order).
  • The incentive behind this change is to help identify a potential mismatch faster as the first unmatched response is the most likely to be the one expected to match.
• Response description in failure messages (httpx.TimeoutException message issued in case of unmatched request or assertion failure message in case of unmatched responses at teardown) is now displaying if the response was already matched or not and less misleading in it's phrasing about what it can match (a single request by default).

Changed

• Last registered matching response will not be reused by default anymore in case all matching responses have already been sent.
  • This behavior can be changed thanks to the new pytest.mark.httpx_mock(can_send_already_matched_responses=True) option.
  • The incentive behind this change is to spot regression if a request was issued more than the expected number of times.
• HTTPXMock class was only exposed for type hinting purpose. This is now explained in the class docstring.
  • As a result this is the last time a change to __init__ signature will be documented and considered a breaking change.
  • Future changes will not be documented and will be considered as internal refactoring not worth a version bump.
  • __init__ now expects one parameter, the newly introduced (since [0.31.0]) options.
• HTTPXMockOptions class was never intended to be exposed and is now marked as private.

Changelog

Sourced from pytest-httpx's changelog.

[0.32.0] - 2024-09-27

Added

• The following option is now available:
  • can_send_already_matched_responses (boolean), defaulting to False.
• Assertion failure message in case of unmatched responses is now linking documentation on how to deactivate the check.
• Assertion failure message in case of unmatched requests is now linking documentation on how to deactivate the check.
• httpx.TimeoutException message issued in case of unmatched request is now linking documentation on how to reuse responses (in case some responses are already matched).

Fixed

• Documentation now clearly state the risks associated with changing the default options.
• Assertion failure message in case of unmatched requests at teardown is now describing requests in a more user-friendly way.
• Assertion failure message in case of unmatched requests at teardown is now prefixing requests with - to highlight the fact that this is a list, preventing misapprehension in case only one element exists.
• Assertion failure message in case of unmatched responses at teardown is now prefixing responses with - to highlight the fact that this is a list, preventing misapprehension in case only one element exists.
• httpx.TimeoutException message issued in case of unmatched request is now prefixing available responses with - to highlight the fact that this is a list, preventing misapprehension in case only one element exists.
• httpx.TimeoutException message issued in case of unmatched request is now listing unmatched responses (in registration order) before already matched one (still in registration order).
  • The incentive behind this change is to help identify a potential mismatch faster as the first unmatched response is the most likely to be the one expected to match.
• Response description in failure messages (httpx.TimeoutException message issued in case of unmatched request or assertion failure message in case of unmatched responses at teardown) is now displaying if the response was already matched or not and less misleading in it's phrasing about what it can match (a single request by default).

Changed

• Last registered matching response will not be reused by default anymore in case all matching responses have already been sent.
  • This behavior can be changed thanks to the new pytest.mark.httpx_mock(can_send_already_matched_responses=True) option.
  • The incentive behind this change is to spot regression if a request was issued more than the expected number of times.
• HTTPXMock class was only exposed for type hinting purpose. This is now explained in the class docstring.
  • As a result this is the last time a change to __init__ signature will be documented and considered a breaking change.
  • Future changes will not be documented and will be considered as internal refactoring not worth a version bump.
  • __init__ now expects one parameter, the newly introduced (since [0.31.0]) options.
• HTTPXMockOptions class was never intended to be exposed and is now marked as private.

Commits

• dcc725f Merge pull request #160 from Colin-b/develop
• 2da1848 Avoid unused variables with a dedicated name
• 50bd257 Document how to use httpx.URL
• 179007e Document the new link
• 9ddead6 Link response reuse documentation
• 08b3803 Release version 0.32.0
• 853c5f7 Keep number of tests up to date
• 33cd894 Merge remote-tracking branch 'origin/develop' into feature/toggle_repeat
• d9a9b86 Cleanup failure description for can_send_already_matched_responses users as well
• 356026b Cleanup failure description
• Additional commits viewable in compare view

Updates ruff from 0.6.7 to 0.6.8

Release notes

Sourced from ruff's releases.

0.6.8

Release Notes

Preview features

• Remove unnecessary parentheses around match case clauses (#13510)
• Parenthesize overlong if guards in match..case clauses (#13513)
• Detect basic wildcard imports in ruff analyze graph (#13486)
• [pylint] Implement boolean-chained-comparison (R1716) (#13435)

Rule changes

• [lake8-simplify] Detect SIM910 when using variadic keyword arguments, i.e., **kwargs (#13503)
• [pyupgrade] Avoid false negatives with non-reference shadowed bindings of loop variables (UP028) (#13504)

Bug fixes

• Detect tuples bound to variadic positional arguments i.e. *args (#13512)
• Exit gracefully on broken pipe errors (#13485)
• Avoid panic when analyze graph hits broken pipe (#13484)

Performance

• Reuse BTreeSets in module resolver (#13440)
• Skip traversal for non-compound statements (#13441)

Contributors

• @​MichaReiser
• @​TomerBin
• @​charliermarsh
• @​diceroll123
• @​dylwil3
• @​haarisr
• @​renovate
• @​sbrugman
• @​vincevannoort
• @​zanieb

Install ruff 0.6.8

Install prebuilt binaries via shell script

curl --proto '=https' --tlsv1.2 -LsSf https://github.com/astral-sh/ruff/releases/download/0.6.8/ruff-installer.sh | sh

Install prebuilt binaries via powershell script

... (truncated)

Changelog

Sourced from ruff's changelog.

0.6.8

Preview features

• Remove unnecessary parentheses around match case clauses (#13510)
• Parenthesize overlong if guards in match..case clauses (#13513)
• Detect basic wildcard imports in ruff analyze graph (#13486)
• [pylint] Implement boolean-chained-comparison (R1716) (#13435)

Rule changes

• [lake8-simplify] Detect SIM910 when using variadic keyword arguments, i.e., **kwargs (#13503)
• [pyupgrade] Avoid false negatives with non-reference shadowed bindings of loop variables (UP028) (#13504)

Bug fixes

• Detect tuples bound to variadic positional arguments i.e. *args (#13512)
• Exit gracefully on broken pipe errors (#13485)
• Avoid panic when analyze graph hits broken pipe (#13484)

Performance

• Reuse BTreeSets in module resolver (#13440)
• Skip traversal for non-compound statements (#13441)

Commits

• ae39ce5 Bump version to 0.6.8 (#13522)
• ff2d214 Don't skip over imports and other nodes containing nested statements in impor...
• 9442cd8 Parenthesize match..case if guards (#13513)
• 8012707 Align formatting of patterns in match-cases with expression formatting in cla...
• d7ffe46 Disable the typeset plugin (#13517)
• 7c83af4 red-knot: Implement the not operator for all Type variants (#13432)
• bbb044e Detect tuples bound to variadic positional arguments i.e. *args (#13512)
• 4810652 Avoid UP028 false negatives with non-reference shadowed bindings of loop vari...
• 11f06e0 Detect SIM910 when using variadic keyword arguments, i.e., **kwargs (#13503)
• f27a8b8 [internal] ComparableExpr (f)strings and bytes made invariant under concate...
• Additional commits viewable in compare view

Updates pyright from 1.1.381 to 1.1.382.post1

Release notes

Sourced from pyright's releases.

v1.1.382.post1

No release notes provided.

v1.1.382.post0

This release fixes a regression with nodeenv support in the v1.1.382 release

v1.1.382

No release notes provided.

Commits

• 74d0088 chore: release v1.1.382.post1 (#310)
• 1ce7b23 fix: avoid warning for .post versions (#309)
• c61cac8 chore: release v1.1.382.post0 (#307)
• f8e7383 CI: correct setup for nodeenv testing (#306)
• 276e381 fix: correct nodeenv environment (#305)
• 05e4563 Pyright NPM Package update to 1.1.382 (#303)
• 0bf95f9 refactor(internal): switch to src dir (#301)
• f4beb25 feat(cli): mention nodejs extra if nodeenv install fails
• e2d0748 feat: add support for nodejs-wheel
• 9edbff0 chore(internal): fix dev requirements
• Additional commits viewable in compare view

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

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <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

[berrydenhartog]

@dependabot rebase

[berrydenhartog]

@dependabot recreate

[dependabot]

Superseded by #224.