search

natbat / pillarpointstewards

Website for pillarpointstewards.com
Apache License 2.0
7 stars 0 forks source link

Bump the python-packages group across 1 directory with 8 updates #360

Closed dependabot[bot] closed 1 month ago

dependabot[bot] commented 1 month ago

Bumps the python-packages group with 8 updates in the / directory:

Package From To
boto3 1.35.8 1.35.51
django-htmx 1.19.0 1.20.0
pytest-django 4.8.0 4.9.0
pytest-httpx 0.30.0 0.33.0
python-ulid 2.7.0 3.0.0
pytz 2024.1 2024.2
sentry-sdk 2.13.0 2.17.0
whitenoise 6.7.0 6.8.2

Updates boto3 from 1.35.8 to 1.35.51

Commits
  • 62dc1fd Merge branch 'release-1.35.51'
  • 174ce87 Bumping version to 1.35.51
  • 85523ea Add changelog entries from botocore
  • ab1c5a9 Merge branch 'release-1.35.50'
  • 960efc1 Merge branch 'release-1.35.50' into develop
  • 743bcbd Bumping version to 1.35.50
  • 9902766 Add changelog entries from botocore
  • 9f80f5a Merge pull request #4319 from boto/dependabot/github_actions/actions/setup-py...
  • 27def47 Merge pull request #4318 from boto/dependabot/github_actions/github/codeql-ac...
  • ad10feb Bump actions/setup-python from 5.2.0 to 5.3.0
  • Additional commits viewable in compare view


Updates django-htmx from 1.19.0 to 1.20.0

Changelog

Sourced from django-htmx's changelog.

1.20.0 (2024-10-25)

  • Drop Python 3.8 support.

  • Support Python 3.13.

  • Updated :ref:the partial rendering tip <partial-rendering> to cover using django-template-partials.

    Thanks to Carlton Gibson in PR [#413](https://github.com/adamchainz/django-htmx/issues/413) <https://github.com/adamchainz/django-htmx/pull/413>__.

Commits


Updates pytest-django from 4.8.0 to 4.9.0

Release notes

Sourced from pytest-django's releases.

v4.9.0

https://github.com/pytest-dev/pytest-django/blob/main/docs/changelog.rst#v490-2024-09-02

Changelog

Sourced from pytest-django's changelog.

v4.9.0 (2024-09-02)

Compatibility ^^^^^^^^^^^^^

  • Added official support for Django 5.1.
  • Dropped support for Django 3.2 and 4.1.

Improvements ^^^^^^^^^^^^

  • Respect the string_if_invalid template setting when --fail-on-template-vars is active and :func:@pytest.mark.ignore_template_errors <pytest.mark.ignore_template_errors> is used.

  • Avoid running database migrations for :class:~django.test.SimpleTestCase unittest tests.

  • Added docstrings to public fixtures.

Bugfixes ^^^^^^^^

  • Fix type hints for pytest_django.asserts.assertFormError() and pytest_django.asserts.assertForSetError().
Commits
  • 1157a7c Release 4.9.0
  • 089843c Add a few type annotations
  • d878d56 Add a missing type annotation
  • 19605d7 fail-on-template-vars: modernize stack inspection code (#1129)
  • c746a46 Avoid running database migrations for SimpleTestCase (#1120)
  • 8502a12 Replace psycopg2, psycopg2cffi -> psycopg in testing and docs
  • 52b2205 Drop support for EOL Django 3.2, 4.1, add support for 5.1
  • c66f9d3 ci: use trusted publishing for release
  • 30602a2 tox: update ruff, mypy
  • a39b910 Bump pypa/gh-action-pypi-publish from 1.8.10 to 1.10.0
  • Additional commits viewable in compare view


Updates pytest-httpx from 0.30.0 to 0.33.0

Release notes

Sourced from pytest-httpx's releases.

0.33.0 (2024-10-28)

Added

  • Explicit support for python 3.13.
  • should_mock option (callable returning a boolean) is now available, defaulting to always returning True. Refer to documentation for more details.
  • Matching on the full multipart body can now be performed using match_files and match_data parameters. Refer to documentation for more details.
  • Matching on extensions (including timeout) can now be performed using match_extensions parameter. Refer to documentation for more details.

Removed

  • non_mocked_hosts option is not available anymore. Use should_mock instead as in the following sample: 
    import pytest

    @​pytest.mark.httpx_mock(non_mocked_hosts=["my_local_test_host"])
def test_previous_behavior(httpx_mock):
...
    

    @​pytest.mark.httpx_mock(should_mock=lambda request: request.url.host not in ["my_local_test_host"])
def test_new_behavior(httpx_mock):
...
    Please note that your hosts might need to be prefixed with www. depending on your usage.

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.

... (truncated)

Changelog

Sourced from pytest-httpx's changelog.

[0.33.0] - 2024-10-28

Added

  • Explicit support for python 3.13.
  • should_mock option (callable returning a boolean) is now available, defaulting to always returning True. Refer to documentation for more details.
  • Matching on the full multipart body can now be performed using match_files and match_data parameters. Refer to documentation for more details.
  • Matching on extensions (including timeout) can now be performed using match_extensions parameter. Refer to documentation for more details.

Removed

  • non_mocked_hosts option is not available anymore. Use should_mock instead as in the following sample: 
    import pytest

    @​pytest.mark.httpx_mock(non_mocked_hosts=["my_local_test_host"])
def test_previous_behavior(httpx_mock):
...
    

    @​pytest.mark.httpx_mock(should_mock=lambda request: request.url.host not in ["my_local_test_host"])
def test_new_behavior(httpx_mock):
...
    Please note that your hosts might need to be prefixed with www. depending on your usage.

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

... (truncated)

Commits


Updates python-ulid from 2.7.0 to 3.0.0

Release notes

Sourced from python-ulid's releases.

3.0.0

Changed

  • Raise TypeError instead of ValueError if constructor is called with value of wrong type.
  • Update ruff linter rules and switch to hatch fmt.

Added

Fixed

Changelog

Sourced from python-ulid's changelog.

3.0.0_ - 2024-10-11

Changed

* Raise `TypeError` instead of `ValueError` if constructor is called with value of wrong type.
* Update ``ruff`` linter rules and switch to ``hatch fmt``.

Added


* Added :meth:`.ULID.parse`-method, which allows to create a :class:`.ULID`-instance from an
  arbitrary supported input value. `@perrotuerto &lt;https://github.com/perrotuerto&gt;`_.

Fixed



    

  • Documentation bug in the example of :meth:.ULID.milliseconds @tsugumi-sys &lt;https://github.com/tsugumi-sys&gt;_.
Commits
  • 1f1a9e1 feat: Use from_hex for strings of length 32
  • bd08a09 chore: Fix pipeline dependency
  • 70742fb feat(coverage): Combine coverge from matrix runs
  • 99b64a9 chore: Brainfart
  • fc02f34 feat(cli): Fix CLI entrypoint
  • c60e7f2 feat(ci): Use pypi/hatch install action
  • 85835a6 feat(ruff): Update linter, rules and fix code accordingly
  • a8108b7 feat(devbox): Add Devbox for general Python setup
  • 7d6d38e fix invalid parameter reference: milliseconds (#30)
  • ca8857c Implement ULID.parse() (#29)
  • See full diff in compare view


Updates pytz from 2024.1 to 2024.2

Commits
  • 3944f75 Bump version numbers to 2024.2 / 2024b
  • 640c9bd IANA 2024b
  • 382ca0c Squashed 'tz/' changes from 380c07cef..923e54bae
  • 96a1e88 Stop testing unavailable and EOL Python 3.5
  • 68186b6 Add support for Python 3.13
  • e994058 Run other jobs if one fails
  • 2326f9f Bump GitHub Actions
  • See full diff in compare view


Updates sentry-sdk from 2.13.0 to 2.17.0

Release notes

Sourced from sentry-sdk's releases.

2.17.0

Various fixes & improvements

2.16.0

Integrations

  • Bottle: Add failed_request_status_codes (#3618) by @​szokeasaurusrex

    You can now define a set of integers that will determine which status codes should be reported to Sentry.

    sentry_sdk.init(
    integrations=[
        BottleIntegration(
            failed_request_status_codes={403, *range(500, 600)},
        )
    ]
)

    Examples of valid failed_request_status_codes:

    • {500} will only send events on HTTP 500.
    • {400, *range(500, 600)} will send events on HTTP 400 as well as the 5xx range.
    • {500, 503} will send events on HTTP 500 and 503.
    • set() (the empty set) will not send events for any HTTP status code.

    The default is {*range(500, 600)}, meaning that all 5xx status codes are reported to Sentry.

  • Bottle: Delete never-reached code (#3605) by @​szokeasaurusrex

  • Redis: Remove flaky test (#3626) by @​sentrivana

  • Django: Improve getting psycopg3 connection info (#3580) by @​nijel

  • Django: Add SpotlightMiddleware when Spotlight is enabled (#3600) by @​BYK

  • Django: Open relevant error when SpotlightMiddleware is on (#3614) by @​BYK

  • Django: Support http_methods_to_capture in ASGI Django (#3607) by @​sentrivana

    ASGI Django now also supports the http_methods_to_capture integration option. This is a configurable tuple of HTTP method verbs that should create a transaction in Sentry. The default is ("CONNECT", "DELETE", "GET", "PATCH", "POST", "PUT", "TRACE",). OPTIONS and HEAD are not included by default.

... (truncated)

Changelog

Sourced from sentry-sdk's changelog.

2.17.0

Various fixes & improvements

2.16.0

Integrations

  • Bottle: Add failed_request_status_codes (#3618) by @​szokeasaurusrex

    You can now define a set of integers that will determine which status codes should be reported to Sentry.

    sentry_sdk.init(
    integrations=[
        BottleIntegration(
            failed_request_status_codes={403, *range(500, 600)},
        )
    ]
)

    Examples of valid failed_request_status_codes:

    • {500} will only send events on HTTP 500.
    • {400, *range(500, 600)} will send events on HTTP 400 as well as the 5xx range.
    • {500, 503} will send events on HTTP 500 and 503.
    • set() (the empty set) will not send events for any HTTP status code.

    The default is {*range(500, 600)}, meaning that all 5xx status codes are reported to Sentry.

  • Bottle: Delete never-reached code (#3605) by @​szokeasaurusrex

  • Redis: Remove flaky test (#3626) by @​sentrivana

  • Django: Improve getting psycopg3 connection info (#3580) by @​nijel

  • Django: Add SpotlightMiddleware when Spotlight is enabled (#3600) by @​BYK

  • Django: Open relevant error when SpotlightMiddleware is on (#3614) by @​BYK

  • Django: Support http_methods_to_capture in ASGI Django (#3607) by @​sentrivana

... (truncated)

Commits


Updates whitenoise from 6.7.0 to 6.8.2

Changelog

Sourced from whitenoise's changelog.

6.8.2 (2024-10-29)

  • Fix compression speed gains for the thread pool when running Django’s collectstatic. The thread pool had no effect due to use of a generator for the results, a refactoring introduced when reviewing the initial PR.

    Thanks to Petr Přikryl for the investigation and fix in PR [#616](https://github.com/evansd/whitenoise/issues/616) <https://github.com/evansd/whitenoise/pull/616>__.

6.8.1 (2024-10-28)

  • Raise any errors from threads in the whitenoise.compress command.

    Regression in 6.8.0. Thanks to Tom Grainger for the spotting this with a comment on PR [#484](https://github.com/evansd/whitenoise/issues/484) <https://github.com/evansd/whitenoise/pull/484#discussion_r1818989096>__.

6.8.0 (2024-10-28)

  • Drop Django 3.2 to 4.1 support.

  • Drop Python 3.8 support.

  • Support Python 3.13.

  • Fix a bug introduced in version 6.0.0 where Range requests could lead to database connection errors in other requests.

    Thanks to Per Myren for the detailed investigation and fix in PR [#612](https://github.com/evansd/whitenoise/issues/612) <https://github.com/evansd/whitenoise/pull/612>__.

  • Use Django’s |FORCE_SCRIPT_NAME|__ setting correctly. This reverts a change from version 5.3.0 that added a call to Django’s |get_script_prefix() method|__ outside of the request-response cycle.

    .. |FORCE_SCRIPT_NAME| replace:: FORCE_SCRIPT_NAME __ https://docs.djangoproject.com/en/stable/ref/settings/#std:setting-FORCE_SCRIPT_NAME

    .. |get_script_prefix() method| replace:: get_script_prefix() method __ https://docs.djangoproject.com/en/stable/ref/urlresolvers/#django.urls.get_script_prefix

    Thanks to Sarah Boyce in PR [#486](https://github.com/evansd/whitenoise/issues/486) <https://github.com/evansd/whitenoise/pull/486>__.

  • Compress files using a thread pool. This speeds up the compression step up to four times in benchmarks.

    Thanks to Anthony Ricaud in PR [#484](https://github.com/evansd/whitenoise/issues/484) <https://github.com/evansd/whitenoise/pull/484>__.

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 ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore 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 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 ` 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 ` will remove all of the ignore conditions of the specified dependency - `@dependabot unignore ` will remove the ignore condition of the specified dependency and ignore conditions
dependabot[bot] commented 1 month ago

Superseded by #361.