chore(deps): update python dependencies #255
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
|
renovate
bot
force-pushed
the
renovate/python-dependencies
branch
10 times, most recently
from
8f848c8 to
158448e
Compare
renovate
bot
force-pushed
the
renovate/python-dependencies
branch
9 times, most recently
from
97fac48 to
a2e5644
Compare
renovate
bot
force-pushed
the
renovate/python-dependencies
branch
8 times, most recently
from
b779706 to
f88db5b
Compare
renovate
bot
force-pushed
the
renovate/python-dependencies
branch
4 times, most recently
from
24484bc to
7aaf992
Compare
renovate
bot
force-pushed
the
renovate/python-dependencies
branch
8 times, most recently
from
7698692 to
04322ac
Compare
renovate
bot
force-pushed
the
renovate/python-dependencies
branch
10 times, most recently
from
f58897f to
555c89e
Compare
renovate
bot
force-pushed
the
renovate/python-dependencies
branch
5 times, most recently
from
fc89495 to
7062a60
Compare
renovate
bot
force-pushed
the
renovate/python-dependencies
branch
from
7062a60 to
4b99341
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^0.0.16->^0.0.427.6.1->7.6.47.0.0->7.1.1~2.15.0->~2.17.0==2.15.0->==2.17.0^0.13.3->^0.14.01.9.0->1.9.1==4.7.3->==4.10.1^0.21.1->^0.24.0^0.36.0->^0.38.0==8.2.3->==8.5.0Release Notes
canonical/cos-lib (cosl)
v0.0.42Compare Source
What's Changed
Full Changelog: canonical/cos-lib@0.0.41...0.0.42
v0.0.41Compare Source
Add LogForwarder in coordinator
v0.0.40Compare Source
What's Changed
Full Changelog: canonical/cos-lib@0.0.39...0.0.40
v0.0.39: Push root ca cert to workload containerCompare Source
v0.0.38: bump release tag to match pyproject.tomlCompare Source
v0.0.37: s3 TLS supportCompare Source
added support for s3 TLS
minor touches to coordinator status
v0.0.36Compare Source
What's Changed
Full Changelog: canonical/cos-lib@0.0.34...0.0.36
v0.0.34: Fixed retry logic in worker objectCompare Source
v0.0.33: refactored worker status logicCompare Source
refactored worker status logic
v0.0.32Compare Source
What's Changed
Full Changelog: canonical/cos-lib@0.0.31...0.0.32
v0.0.31Compare Source
What's Changed
Full Changelog: canonical/cos-lib@0.0.30...0.0.31
v0.0.30: holistic worker logicCompare Source
refactored Worker logic to use a stateless reconciler function to avoid some pod-churn related race conditions
v0.0.29Compare Source
What's Changed
Full Changelog: canonical/cos-lib@0.0.28...0.0.29
v0.0.28Compare Source
What's Changed
Full Changelog: canonical/cos-lib@0.0.27...0.0.28
v0.0.27Compare 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.26Compare Source
What's Changed
remote writeendpoints to relation data by @michaeldmitry in https://github.com/canonical/cos-lib/pull/64Full Changelog: canonical/cos-lib@0.0.25...0.0.26
v0.0.25Compare Source
What's Changed
Full Changelog: canonical/cos-lib@0.0.24...0.0.25
v0.0.24Compare Source
What's Changed
Full Changelog: canonical/cos-lib@0.0.23...0.0.24
v0.0.23: worker status checks TLS supportCompare Source
What's Changed
Full Changelog: canonical/cos-lib@0.0.22...0.0.23
v0.0.22: Worker service status monitoringCompare 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.21Compare Source
What's Changed
Full Changelog: canonical/cos-lib@0.0.20...0.0.21
v0.0.20: Fix removeprefix for python3.8Compare Source
What's Changed
Full Changelog: canonical/cos-lib@0.0.19...0.0.20
v0.0.19Compare Source
What's Changed
_PebbleLogClientstatic method calls by @michaeldmitry in https://github.com/canonical/cos-lib/pull/41Full Changelog: canonical/cos-lib@0.0.18...0.0.19
v0.0.18Compare Source
What's Changed
Full Changelog: canonical/cos-lib@0.0.17...0.0.18
v0.0.17Compare Source
What's Changed
Full Changelog: canonical/cos-lib@0.0.16...0.0.17
nedbat/coveragepy (coverage)
v7.6.4Compare Source
withstatements could cause contained branches to beincorrectly marked as missing (
issue 1880_). This is now fixed... _issue 1880:https://github.com/nedbat/coveragepy/issues/18800
.. _changes_7-6-3:
v7.6.3Compare 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 isnow 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.2Compare 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, thanksto
LiuYinCarl and Marco Ricci <pull 1838_>.Fix: the LCOV report now has correct line numbers (fixing
issue 1846) andbetter branch descriptions for BRDA records (fixing
issue 1850). Thereare other changes to lcov also, including a new configuration option
:ref:
line_checksums <config_lcov_line_checksums>to control whether linechecksums 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_ andpull 1851_).Fixed the docs for multi-line regex exclusions, closing
issue 1863_.Fixed a potential crash in the C tracer, closing
issue 1835, thanks toJan 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.1Compare Source
v7.1.0Compare Source
canonical/operator (ops)
v2.17.0Compare Source
Features
ops[testing]and expose the names in ops.testing (#1381)type: ignoreit (#1345)InvalidStatusErrorinstead of waiting for Juju:CollectStatusEvent.add_statuswith error or unknown (#1386)_ModelBackend.set_status(#1354)Fixes
StatusBasesubclasses by callingStatusBase.registerin__init_subclass__(#1383)Secret.set_infoandSecret.set_contentcan be called in the same hook (#1373)Documentation
config-changedis triggered by Juju trust (#1357)CharmBaseinheritance example by @theofpa (#1349)Continuous Integration
Testing
Refactoring
ops.testingtoops._private.harness(#1369)unittest.mocknames in the 'mock' namespace (#1379)StatusBase.registerdecorator (#1384)Chores
v2.16.1Compare Source
Fix
v2.16.0Compare Source
Features
Refactor
Fixes
Documentation
Tests
CI
PyCQA/pep8-naming (pep8-naming)
v0.14.1Compare Source
v0.14.0Compare Source
@typing.override.ignore-namesglobbing on all platforms.python-poetry/poetry-core (poetry-core)
v1.9.1Compare Source
Added
3.13to the list of available Python versions (#747).mongodb/mongo-python-driver (pymongo)
v4.10.1: PyMongo 4.10.1Compare Source
Community notes: https://www.mongodb.com/community/forums/t/pymongo-4-10-1-released/299573
v4.10.0: PyMongo 4.10.0Compare Source
Community notes: https://www.mongodb.com/community/forums/t/pymongo-4-10-0-released/299474
v4.9.2: PyMongo 4.9.2Compare Source
pymongo.asynchronous.mongo_client.AsyncMongoClientcould deadlock.pymongo.results.UpdateResult.did_upsertwould raise a TypeError.v4.9.1: PyMongo 4.9.1Compare Source
Community notes: https://www.mongodb.com/community/forums/t/pymongo-4-9-released/297833
v4.9Compare Source
v4.8.0: PyMongo 4.8.0Compare Source
Changes in Version 4.8.0
PyMongo 4.8 brings a number of improvements including:
bson.binary.Binaryis now redacted when the subtype is SENSITIVE_SUBTYPE(8).GitHub Releases now include a Software Bill of Materials, and signature
files corresponding to the distribution files released on PyPI.
startAtOperationTimeandresumeTokencould be added to a retry attempt, which caused the retry to fail.
sslmodule whenpyopensslimport fails with AttributeError.Unavoidable breaking changes
hatchas our build backend, we no longer have a usablesetup.pyfileand require installation using
pip. Attempts to invoke thesetup.pyfile 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.0Compare Source
0.24.0 (2024-08-22)
pytest_asyncio.fixture. Users are encouraged to use the loop_scope keyword argument, which does exactly the same.@pytest.mark.asyncio. #812v0.23.8: pytest-asyncio 0.23.8Compare Source
0.23.8 (2024-07-17)
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.7Compare Source
0.23.7 (2024-05-19)
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.6Compare Source
0.23.6 (2024-03-19)
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.5Compare Source
0.23.5 (2024-02-09)
asyncio.get_event_loop()from affecting test cases #757Known 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.4Compare Source
0.23.4 (2024-01-28)
v0.23.3: pytest-asyncio 0.23.3Compare Source
0.23.3 (2024-01-01)
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.2Compare Source
0.23.2 (2023-12-04)
v0.23.1: pytest-asyncio 0.23.1Compare Source
0.23.1 (2023-12-03)
v0.23.0: pytest-asyncio 0.23.0Compare Source
This release is backwards-compatible with v0.21. Changes are
non-breaking, unless you upgrade from v0.22.
loops with class, module, package, and session scopes can be
requested via the scope keyword argument to the asyncio
mark.
non-default or multiple event loops #662
pytest_asyncio.is_async_testwhich returns whether atest item is managed by pytest-asyncio #376
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)
via the asyncio_event_loop mark. #620
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.
charmed-kubernetes/pytest-operator (pytest-operator)
v0.37.0: 0.37.0Compare Source
jd/tenacity (tenacity)
v8.5.0Compare Source
What's Changed
Full Changelog: jd/tenacity@8.4.2...8.5.0
v8.4.2: tenacity 8.4.2Compare Source
What's Changed
Full Changelog: jd/tenacity@8.4.1...8.4.2
v8.4.1: tenacity 8.4.1Compare Source
What's Changed
tenacity.asynciosubpackage in release dist by @cdce8p in https://github.com/jd/tenacity/pull/474Full Changelog: jd/tenacity@8.4.0...8.4.1
v8.4.0: tenacity 8.4.0Compare Source
What's Changed
Full Changelog: jd/tenacity@8.3.0...8.4.0
v8.3.0Compare Source
New Features
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
Other Notes
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.
This PR was generated by Mend Renovate. View the repository job log.