chore(deps): update python dependencies #255
Open
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.39
7.0.0
->7.1.1
2.16.1
->2.17.0
==2.15.0
->==2.17.0
^0.13.3
->^0.14.0
4.8.0
->4.10.1
==4.7.3
->==4.10.1
8.3.2
->8.3.3
^0.21.1
->^0.24.0
^0.36.0
->^0.37.0
==8.2.3
->==8.5.0
Release Notes
canonical/cos-lib (cosl)
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.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 objectCompare Source
v0.0.33
: refactored worker status logicCompare 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 logicCompare 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
remote write
endpoints 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.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 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.21
Compare 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.19
Compare Source
What's Changed
_PebbleLogClient
static 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.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
pycqa/flake8 (flake8)
v7.1.1
Compare Source
v7.1.0
Compare Source
canonical/operator (ops)
v2.17.0
Compare Source
Features
ops[testing]
and expose the names in ops.testing (#1381)type: ignore
it (#1345)InvalidStatusError
instead of waiting for Juju:CollectStatusEvent.add_status
with error or unknown (#1386)_ModelBackend.set_status
(#1354)Fixes
StatusBase
subclasses by callingStatusBase.register
in__init_subclass__
(#1383)Secret.set_info
andSecret.set_content
can be called in the same hook (#1373)Documentation
config-changed
is triggered by Juju trust (#1357)CharmBase
inheritance example by @theofpa (#1349)Continuous Integration
Testing
Refactoring
ops.testing
toops._private.harness
(#1369)unittest.mock
names in the 'mock' namespace (#1379)StatusBase.register
decorator (#1384)Chores
PyCQA/pep8-naming (pep8-naming)
v0.14.1
Compare Source
v0.14.0
Compare Source
@typing.override
.ignore-names
globbing on all platforms.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.AsyncMongoClient
could deadlock.pymongo.results.UpdateResult.did_upsert
would 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.9
Compare Source
pytest-dev/pytest (pytest)
v8.3.3
Compare Source
pytest 8.3.3 (2024-09-09)
Bug fixes
#12446: Avoid calling
@property
(and other instance descriptors) during fixture discovery -- byasottile
{.interpreted-text role="user"}#12659: Fixed the issue of not displaying assertion failure differences when using the parameter
--import-mode=importlib
in pytest>=8.1.#12667: Fixed a regression where type change in [ExceptionInfo.errisinstance]{.title-ref} caused [mypy]{.title-ref} to fail.
#12744: Fixed typing compatibility with Python 3.9 or less -- replaced [typing.Self]{.title-ref} with [typing_extensions.Self]{.title-ref} -- by
Avasam
{.interpreted-text role="user"}#12745: Fixed an issue with backslashes being incorrectly converted in nodeid paths on Windows, ensuring consistent path handling across environments.
#6682: Fixed bug where the verbosity levels where not being respected when printing the "msg" part of failed assertion (as in
assert condition, msg
).#9422: Fix bug where disabling the terminal plugin via
-p no:terminal
would cause crashes related to missing theverbose
option.-- by
GTowers1
{.interpreted-text role="user"}Improved documentation
Miscellaneous internal changes
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_test
which 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.0
Compare 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.asyncio
subpackage 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.0
Compare 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.