Skip to content

chore(deps): update python dependencies #255

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
Closed
wants to merge 1 commit into from
Closed

chore(deps): update python dependencies #255

wants to merge 1 commit into from

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Jul 16, 2024 •
edited
Loading

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
cosl ^0.0.16 -> ^0.0.42 age adoption passing confidence
coverage 7.6.1 -> 7.6.4 age adoption passing confidence
flake8 (changelog) 7.0.0 -> 7.1.1 age adoption passing confidence
ops (changelog) ~2.15.0 -> ~2.17.0 age adoption passing confidence
ops (changelog) ==2.15.0 -> ==2.17.0 age adoption passing confidence
pep8-naming (changelog) ^0.13.3 -> ^0.14.0 age adoption passing confidence
poetry-core 1.9.0 -> 1.9.1 age adoption passing confidence
pymongo ==4.7.3 -> ==4.10.1 age adoption passing confidence
pytest-asyncio (changelog) ^0.21.1 -> ^0.24.0 age adoption passing confidence
pytest-operator ^0.36.0 -> ^0.38.0 age adoption passing confidence
tenacity ==8.2.3 -> ==8.5.0 age adoption passing confidence

Release Notes

canonical/cos-lib (cosl)

v0.0.42

Compare Source

What's Changed

Full Changelog: canonical/cos-lib@0.0.41...0.0.42

v0.0.41

Compare Source

Add LogForwarder in coordinator

v0.0.40

Compare Source

What's Changed

Full Changelog: canonical/cos-lib@0.0.39...0.0.40

v0.0.39: Push root ca cert to workload container

Compare Source

v0.0.38: bump release tag to match pyproject.toml

Compare Source

v0.0.37: s3 TLS support

Compare Source

added support for s3 TLS
minor touches to coordinator status

v0.0.36

Compare Source

What's Changed

Full Changelog: canonical/cos-lib@0.0.34...0.0.36

v0.0.34: Fixed retry logic in worker object

Compare Source

v0.0.33: refactored worker status logic

Compare Source

refactored worker status logic

v0.0.32

Compare Source

What's Changed

Full Changelog: canonical/cos-lib@0.0.31...0.0.32

v0.0.31

Compare Source

What's Changed

Full Changelog: canonical/cos-lib@0.0.30...0.0.31

v0.0.30: holistic worker logic

Compare Source

refactored Worker logic to use a stateless reconciler function to avoid some pod-churn related race conditions

v0.0.29

Compare Source

What's Changed

Full Changelog: canonical/cos-lib@0.0.28...0.0.29

v0.0.28

Compare Source

What's Changed

Full Changelog: canonical/cos-lib@0.0.27...0.0.28

v0.0.27

Compare Source

unified config accessing logic so that it can be overridden by worker subclasses if a worker charm needs to preprocess its config on a per-unit basis

v0.0.26

Compare Source

What's Changed

Full Changelog: canonical/cos-lib@0.0.25...0.0.26

v0.0.25

Compare Source

What's Changed

Full Changelog: canonical/cos-lib@0.0.24...0.0.25

v0.0.24

Compare Source

What's Changed

Full Changelog: canonical/cos-lib@0.0.23...0.0.24

v0.0.23: worker status checks TLS support

Compare Source

What's Changed

Full Changelog: canonical/cos-lib@0.0.22...0.0.23

v0.0.22: Worker service status monitoring

Compare Source

The main feature is an update to the Coordinator-Worker classes, introducing a pebble-checks-based API to monitor the health of the worker service and set application status accordingly.
This takes care of some bugs we experienced in the past where the worker would not start and the admin had no way to notice it if not to manually GET a /ready endpoint on the application IP.

What's Changed

Full Changelog: canonical/cos-lib@0.0.21...0.0.22

v0.0.21

Compare Source

What's Changed

Full Changelog: canonical/cos-lib@0.0.20...0.0.21

v0.0.20: Fix removeprefix for python3.8

Compare Source

What's Changed

Full Changelog: canonical/cos-lib@0.0.19...0.0.20

v0.0.19

Compare Source

What's Changed

Full Changelog: canonical/cos-lib@0.0.18...0.0.19

v0.0.18

Compare Source

What's Changed

Full Changelog: canonical/cos-lib@0.0.17...0.0.18

v0.0.17

Compare Source

What's Changed

Full Changelog: canonical/cos-lib@0.0.16...0.0.17

nedbat/coveragepy (coverage)

v7.6.4

Compare Source

  • fix: multi-line with statements could cause contained branches to be
    incorrectly marked as missing (issue 1880_). This is now fixed.

.. _issue 1880:https://github.com/nedbat/coveragepy/issues/18800

.. _changes_7-6-3:

v7.6.3

Compare Source

  • Fix: nested context managers could incorrectly be analyzed to flag a missing
    branch on the last context manager, as described in issue 1876_. This is
    now fixed.

  • Fix: the missing branch message about not exiting a module had an extra
    "didn't," as described in issue 1873_. This is now fixed.

.. _issue 1873:https://github.com/nedbat/coveragepy/issues/18733
.. _issue 1876https://github.com/nedbat/coveragepy/issues/187676

.. _changes_7-6-2:

v7.6.2

Compare Source

  • Dropped support for Python 3.8 and PyPy 3.8.

  • Fix: a final wildcard match/case clause assigning to a name (case _ as value) was incorrectly marked as a missing branch. This is now fixed,
    closing issue 1860_.

  • Fewer things are considered branches now. Lambdas, comprehensions, and
    generator expressions are no longer marked as missing branches if they don't
    complete execution. Closes issue 1852_.

  • Fix: the HTML report didn't properly show multi-line f-strings that end with
    a backslash continuation. This is now fixed, closing issue 1836, thanks
    to LiuYinCarl and Marco Ricci <pull 1838_>    .

  • Fix: the LCOV report now has correct line numbers (fixing issue 1846) and
    better branch descriptions for BRDA records (fixing issue 1850    ). There
    are other changes to lcov also, including a new configuration option
    :ref:line_checksums <config_lcov_line_checksums> to control whether line
    checksums are included in the lcov report. The default is false. To keep
    checksums set it to true. All this work is thanks to Zack Weinberg
    (pull 1849_ and pull 1851_).

  • Fixed the docs for multi-line regex exclusions, closing issue 1863_.

  • Fixed a potential crash in the C tracer, closing issue 1835, thanks to
    Jan Kühle <pull 1843_>    .

.. _issue 1835:https://github.com/nedbat/coveragepy/issues/18355
.. _issue 1836https://github.com/nedbat/coveragepy/issues/183636
.. _pull 183https://github.com/nedbat/coveragepy/pull/1838838
.. _pull 18https://github.com/nedbat/coveragepy/pull/18431843
.. _issue 1https://github.com/nedbat/coveragepy/issues/1846/1846
.. _pull https://github.com/nedbat/coveragepy/pull/1849l/1849
.. _issuehttps://github.com/nedbat/coveragepy/issues/1850es/1850
.. _pulhttps://github.com/nedbat/coveragepy/pull/1851ull/1851
.. _isshttps://github.com/nedbat/coveragepy/issues/1852sues/1852
.. _ishttps://github.com/nedbat/coveragepy/issues/1860ssues/1860
.. _ihttps://github.com/nedbat/coveragepy/issues/1863issues/1863

.. _changes_7-6-1:

pycqa/flake8 (flake8)

v7.1.1

Compare Source

v7.1.0

Compare Source

canonical/operator (ops)

v2.17.0

Compare Source

Features

  • Optionally install Scenario with ops[testing] and expose the names in ops.testing (#​1381)
  • Change ops.main() so that you don't need to type: ignore it (#​1345)
  • Expand the secret ID out to the full URI when only given the ID (#​1358)
  • Add a JujuVersion property for Pebble log forwarding to Loki (#​1370)
  • Pre-emptively raise InvalidStatusError instead of waiting for Juju:
    • Make it an error to call CollectStatusEvent.add_status with error or unknown (#​1386)
    • Document and validate settable status values in _ModelBackend.set_status (#​1354)

Fixes

  • Fix type of StatusBase subclasses by calling StatusBase.register in __init_subclass__ (#​1383)
  • Secret.set_info and Secret.set_content can be called in the same hook (#​1373)

Documentation

  • Add top-level intro and module-level intros (#​1320)
  • Update the links to the Pebble docs (#​1362)
  • Note about repeatedly setting secret value in Juju 3.6 (#​1366)
  • config-changed is triggered by Juju trust (#​1357)
  • Typo on CharmBase inheritance example by @​theofpa (#​1349)
  • Docs: move Pebble to a separate page (#​1392)

Continuous Integration

  • Periodically run the unit tests of all GitHub-hosted published charms (#​1365)
  • Update the TIOBE reporting for the changes in coverage calculation (#​1367)
  • Spell-check the code as part of linting (#​1388)
  • Run the smoke tests on a schedule (#​1387)

Testing

  • Fix tests that leaked environment variables (#​1385)

Refactoring

  • Move the content of ops.testing to ops._private.harness (#​1369)
  • Keep the unittest.mock names in the 'mock' namespace (#​1379)
  • Deprecate StatusBase.register decorator (#​1384)

Chores

  • Note Juju version on legacy workaround (#​1355)
  • Re-enable test now that Pebble directory permissions are fixed (#​1363)
  • Generate warnings for events that will be removed in Juju 4.0 (#​1374)

v2.16.1

Compare Source

Fix

  • Don't alter os.environ when creating a Harness (#​1359)

v2.16.0

Compare Source

Features

  • Add the description field to SecretInfo in (#​1338)

Refactor

  • Parse JUJU_* environment variables in one place in (#​1313)

Fixes

  • Fix reading Juju secret expiry dates in (#​1317)
  • Correct the signature of .events() in (#​1342)

Documentation

  • Security policy change to only support each active major release in (#​1297)
  • Add Juju version markers in (#​1311)
  • Use Sphinx 8 in (#​1303)
  • Live reload documentation with sphinx-autobuild in (#​1323)

Tests

  • Update the smoke test series/bases in (#​1318)
  • Run pytest in parallel with pytest xdist in (#​1319)
  • Bump Pyright to 1.1.377 in (#​1332)
  • Run tests on Python 3.12 and the install test on Python 3.13 in (#​1315)

CI

  • Add a workflow that runs the TIOBE quality checks in (#​1301)
  • Allow executing the TIOBE workflow manually in (#​1321)
  • Make Pyright report unnecessary type ignore comments in (#​1333)
  • Enable linting of docs/custom_conf.py in (#​1330)
PyCQA/pep8-naming (pep8-naming)

v0.14.1

Compare Source

  • Require Python 3.8 or later.

v0.14.0

Compare Source

  • Drop support for Python 3.7.
  • Add support for Python 3.12.
  • Ignore methods decorated by @typing.override.
  • Perform case-sensitive ignore-names globbing on all platforms.
python-poetry/poetry-core (poetry-core)

v1.9.1

Compare Source

Added
  • Add 3.13 to the list of available Python versions (#​747).
mongodb/mongo-python-driver (pymongo)

v4.10.1: PyMongo 4.10.1

Compare Source

Community notes: https://www.mongodb.com/community/forums/t/pymongo-4-10-1-released/299573

v4.10.0: PyMongo 4.10.0

Compare Source

Community notes: https://www.mongodb.com/community/forums/t/pymongo-4-10-0-released/299474

v4.9.2: PyMongo 4.9.2

Compare Source

  • Fixed a bug where pymongo.asynchronous.mongo_client.AsyncMongoClient could deadlock.
  • Fixed a bug where PyMongo could fail to import on Windows if asyncio is misconfigured.
  • Fixed a bug where pymongo.results.UpdateResult.did_upsert would raise a TypeError.

v4.9.1: PyMongo 4.9.1

Compare Source

Community notes: https://www.mongodb.com/community/forums/t/pymongo-4-9-released/297833

v4.9

Compare Source

v4.8.0: PyMongo 4.8.0

Compare Source

Changes in Version 4.8.0

PyMongo 4.8 brings a number of improvements including:

  • The handshake metadata for "os.name" on Windows has been simplified to "Windows" to improve import time.
  • The repr of bson.binary.Binary is now redacted when the subtype is SENSITIVE_SUBTYPE(8).
  • Secure Software Development Life Cycle automation for release process.
    GitHub Releases now include a Software Bill of Materials, and signature
    files corresponding to the distribution files released on PyPI.
  • Fixed a bug in change streams where both startAtOperationTime and resumeToken
    could be added to a retry attempt, which caused the retry to fail.
  • Fallback to stdlib ssl module when pyopenssl import fails with AttributeError.
  • Improved performance of MongoClient operations, especially when many operations are being run concurrently.

Unavoidable breaking changes

  • Since we are now using hatch as our build backend, we no longer have a usable setup.py file
    and require installation using pip. Attempts to invoke the setup.py file will raise an exception.
    Additionally, pip >= 21.3 is now required for editable installs.

Issues Resolved

See the PyMongo 4.8 release notes in JIRA for the list of resolved issues in this release.

Full Changelog: mongodb/mongo-python-driver@4.7.1...4.8.0

pytest-dev/pytest-asyncio (pytest-asyncio)

v0.24.0: pytest-asyncio 0.24.0

Compare Source

0.24.0 (2024-08-22)
  • BREAKING: Updated minimum supported pytest version to v8.2.0
  • Adds an optional loop_scope keyword argument to pytest.mark.asyncio. This argument controls which event loop is used to run the marked async test. #​706, #​871
  • Deprecates the optional scope keyword argument to pytest.mark.asyncio for API consistency with pytest_asyncio.fixture. Users are encouraged to use the loop_scope keyword argument, which does exactly the same.
  • Raises an error when passing scope or loop_scope as a positional argument to @pytest.mark.asyncio. #​812
  • Fixes a bug that caused module-scoped async fixtures to fail when reused in other modules #​862 #​668

v0.23.8: pytest-asyncio 0.23.8

Compare Source

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.

v0.23.7: pytest-asyncio 0.23.7

Compare Source

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.

v0.23.6: pytest-asyncio 0.23.6

Compare Source

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.

v0.23.5: pytest-asyncio 0.23.5

Compare Source

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.

v0.23.4: pytest-asyncio 0.23.4

Compare Source

0.23.4 (2024-01-28)
  • pytest-asyncio no longer imports additional, unrelated packages during test collection #​729
  • Addresses further issues that caused an internal pytest error during test collection
  • Declares incompatibility with pytest 8 #​737

v0.23.3: pytest-asyncio 0.23.3

Compare Source

0.23.3 (2024-01-01)
  • Fixes a bug that caused event loops to be closed prematurely when using async generator fixtures with class scope or wider in a function-scoped test #​706
  • Fixes various bugs that caused an internal pytest error during test collection #​711 #​713 #​719
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.

v0.23.2: pytest-asyncio 0.23.2

Compare Source

0.23.2 (2023-12-04)
  • Fixes a bug that caused an internal pytest error when collecting .txt files #​703

v0.23.1: pytest-asyncio 0.23.1

Compare Source

0.23.1 (2023-12-03)
  • Fixes a bug that caused an internal pytest error when using module-level skips #​701

v0.23.0: pytest-asyncio 0.23.0

Compare Source

This release is backwards-compatible with v0.21. Changes are
non-breaking, unless you upgrade from v0.22.

  • BREAKING: The asyncio_event_loop mark has been removed. Event
    loops with class, module, package, and session scopes can be
    requested via the scope keyword argument to the asyncio
    mark.
  • Introduces the event_loop_policy fixture which allows testing with
    non-default or multiple event loops #​662
  • Introduces pytest_asyncio.is_async_test which returns whether a
    test item is managed by pytest-asyncio #​376
  • Removes and pytest-trio, mypy, and flaky from the test
    dependencies #​620, #​674, #​678

v0.22.0: pytest-asyncio 0.22.0 (yanked)

Compare Source

This release deprecated event loop overrides, but didn't provide adequate replacement functionality for all relevant use cases. As such, the release was yanked from PyPI.

0.22.0 (2023-10-31)
  • Class-scoped and module-scoped event loops can be requested
    via the asyncio_event_loop mark. #​620
  • Deprecate redefinition of the event_loop fixture. #​587
    Users requiring a class-scoped or module-scoped asyncio event loop for their tests
    should mark the corresponding class or module with asyncio_event_loop.
  • Test items based on asynchronous generators always exit with xfail status and emit a warning during the collection phase. This behavior is consistent with synchronous yield tests. #​642
  • Remove support for Python 3.7
  • Declare support for Python 3.12
charmed-kubernetes/pytest-operator (pytest-operator)

v0.37.0: 0.37.0

Compare Source

jd/tenacity (tenacity)

v8.5.0

Compare Source

What's Changed

Full Changelog: jd/tenacity@8.4.2...8.5.0

v8.4.2: tenacity 8.4.2

Compare Source

What's Changed

Full Changelog: jd/tenacity@8.4.1...8.4.2

v8.4.1: tenacity 8.4.1

Compare Source

What's Changed

Full Changelog: jd/tenacity@8.4.0...8.4.1

v8.4.0: tenacity 8.4.0

Compare Source

What's Changed

Full Changelog: jd/tenacity@8.3.0...8.4.0

v8.3.0

Compare Source

New Features

  • Added a new stop function: stop_before_delay, which will stop execution if the next sleep time would cause overall delay to exceed the specified delay. Useful for use cases where you have some upper bound on retry times that you must not exceed, so returning before that timeout is preferable than returning after that timeout.

Bug Fixes

  • Preserve defaults and kwdefaults through retry decorator

Other Notes

  • Add a "test" extra

Configuration

📅 Schedule: Branch creation - "after 1am and before 2am every weekday" in timezone Etc/UTC, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot requested review from MiaAltieri and delgod July 16, 2024 01:45
@renovate
Copy link
Contributor Author

renovate bot commented Jul 16, 2024 •
edited
Loading

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: poetry.lock
Updating dependencies
Resolving dependencies...


Because pytest-operator (0.38.0) depends on pytest-asyncio (<0.23)
 and no versions of pytest-operator match >0.38.0,<0.39.0, pytest-operator (>=0.38.0,<0.39.0) requires pytest-asyncio (<0.23).
So, because mongodb-k8s depends on both pytest-asyncio (^0.24.0) and pytest-operator (^0.38.0), version solving failed.

@renovate renovate bot force-pushed the renovate/python-dependencies branch 10 times, most recently from 8f848c8 to 158448e Compare July 23, 2024 07:34
@renovate renovate bot force-pushed the renovate/python-dependencies branch 9 times, most recently from 97fac48 to a2e5644 Compare July 31, 2024 07:08
@renovate renovate bot force-pushed the renovate/python-dependencies branch 8 times, most recently from b779706 to f88db5b Compare August 4, 2024 19:57
@renovate renovate bot force-pushed the renovate/python-dependencies branch 4 times, most recently from 24484bc to 7aaf992 Compare October 1, 2024 03:44
@renovate renovate bot force-pushed the renovate/python-dependencies branch 8 times, most recently from 7698692 to 04322ac Compare October 8, 2024 14:55
@renovate renovate bot force-pushed the renovate/python-dependencies branch 10 times, most recently from f58897f to 555c89e Compare October 15, 2024 12:16
@renovate renovate bot force-pushed the renovate/python-dependencies branch 5 times, most recently from fc89495 to 7062a60 Compare October 21, 2024 01:48
@renovate renovate bot force-pushed the renovate/python-dependencies branch from 7062a60 to 4b99341 Compare October 21, 2024 16:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@delgod delgod Awaiting requested review from delgod

@MiaAltieri MiaAltieri Awaiting requested review from MiaAltieri

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@Mehdi-Bendriss