Lock file maintenance Python dependencies #79
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
4 times, most recently
from
f008c48 to
4c461d3
Compare
renovate
bot
force-pushed
the
renovate/python-dependencies
branch
4 times, most recently
from
175104d to
f1755e7
Compare
renovate
bot
force-pushed
the
renovate/python-dependencies
branch
3 times, most recently
from
b836e2a to
8e33986
Compare
renovate
bot
force-pushed
the
renovate/python-dependencies
branch
4 times, most recently
from
918aff1 to
02d060e
Compare
renovate
bot
force-pushed
the
renovate/python-dependencies
branch
5 times, most recently
from
1b77c1a to
1197eed
Compare
renovate
bot
force-pushed
the
renovate/python-dependencies
branch
3 times, most recently
from
b3ffdc6 to
2ca6213
Compare
renovate
bot
force-pushed
the
renovate/python-dependencies
branch
3 times, most recently
from
acd70c0 to
db3a645
Compare
renovate
bot
force-pushed
the
renovate/python-dependencies
branch
2 times, most recently
from
9b5ee18 to
ad1632c
Compare
renovate
bot
force-pushed
the
renovate/python-dependencies
branch
4 times, most recently
from
95552ba to
c60cdc2
Compare
renovate
bot
force-pushed
the
renovate/python-dependencies
branch
4 times, most recently
from
b0e39fd to
6f5edb8
Compare
renovate
bot
force-pushed
the
renovate/python-dependencies
branch
2 times, most recently
from
b09c20f to
ce394f8
Compare
renovate
bot
force-pushed
the
renovate/python-dependencies
branch
4 times, most recently
from
2049525 to
420c2f4
Compare
renovate
bot
force-pushed
the
renovate/python-dependencies
branch
3 times, most recently
from
40f8ac2 to
91169a0
Compare
renovate
bot
force-pushed
the
renovate/python-dependencies
branch
3 times, most recently
from
8ca8847 to
1c39027
Compare
renovate
bot
force-pushed
the
renovate/python-dependencies
branch
4 times, most recently
from
383a3b3 to
63b5240
Compare
renovate
bot
force-pushed
the
renovate/python-dependencies
branch
2 times, most recently
from
720921a to
65b6cd5
Compare
renovate
bot
force-pushed
the
renovate/python-dependencies
branch
2 times, most recently
from
ce53898 to
5d7de07
Compare
renovate
bot
force-pushed
the
renovate/python-dependencies
branch
from
5d7de07 to
6166f0c
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:
^24.4.2->^24.10.0^24.4.2->^24.10.0^2.2.6->^2.3.0^0.0.12->^0.0.50^7.5.1->^7.6.10^7.0.0->^7.1.1^2.13.0->^2.17.12.17.0->2.17.11.10.19->1.10.20^1.10.17->^1.10.20^1.1.318->^1.1.391^8.2.2->^8.3.4^8.2.2->^8.3.4^0.21.2->^0.25.1^3.11.1->^3.14.0^6.0.1->^6.0.2^6.0.1->^6.0.2^8.4.2->^8.5.0^8.4.2->^8.5.0^4.9.0->^4.12.2🔧 This Pull Request updates lock files to use the latest dependency versions.
Release Notes
canonical/cos-lib (cosl)
v0.0.50Compare Source
What's Changed
Full Changelog: canonical/cos-lib@0.0.49...0.0.50
v0.0.49Compare Source
What's Changed
Full Changelog: canonical/cos-lib@0.0.48...0.0.49
v0.0.48Compare Source
What's Changed
cataloguerelation by @michaeldmitry in https://github.com/canonical/cos-lib/pull/113New Contributors
Full Changelog: canonical/cos-lib@0.0.47...0.0.48
v0.0.47Compare Source
v0.0.46: DS ExchangeCompare Source
What's Changed
New Contributors
Full Changelog: canonical/cos-lib@0.0.45...0.0.46
v0.0.45Compare Source
What's Changed
Full Changelog: canonical/cos-lib@0.0.44...0.0.45
v0.0.43Compare Source
What's Changed
workload_tracing_protocolsas an arg by @michaeldmitry in https://github.com/canonical/cos-lib/pull/95New Contributors
Full Changelog: canonical/cos-lib@0.0.42...0.0.43
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
v0.0.16Compare Source
What's Changed
Full Changelog: canonical/cos-lib@0.0.14...0.0.16
v0.0.15Compare Source
What's Changed
New Contributors
Full Changelog: canonical/cos-lib@0.0.13...0.0.15
v0.0.14Compare Source
v0.0.13Compare Source
What's Changed
Full Changelog: canonical/cos-lib@0.0.12...0.0.13
nedbat/coveragepy (coverage)
v7.6.10Compare Source
Fix: some descriptions of missing branches in HTML and LCOV reports were
incorrect when multi-line statements were involved (
issue 1874_ andissue 1875_). These are now fixed.Fix: Python 3.14
defers evaluation of annotations <pep649_>_ by moving theminto separate code objects. That code is rarely executed, so coverage.py
would mark them as missing, as reported in
issue 1908_. Now they areignored by coverage automatically.
Fixed an obscure and mysterious problem on PyPy 3.10 seemingly involving
mocks, imports, and trace functions:
issue 1902_. To be honest, I don'tunderstand the problem or the solution, but
git bisecthelped find it,and now it's fixed.
Docs: re-wrote the :ref:
subprocesspage to put multiprocessing first and tohighlight the correct use of :class:
multiprocessing.Pool <python:multiprocessing.pool.Pool>... _issue 1874:https://github.com/nedbat/coveragepy/issues/18744
.. _issue 1875https://github.com/nedbat/coveragepy/issues/187575
.. _issue 190https://github.com/nedbat/coveragepy/issues/1902902
.. _issue 19https://github.com/nedbat/coveragepy/issues/19081908
.. _pep649: https://docs.python.org/3.14/whatsnew/3.14.html#pep-649-deferred-evaluation-of-annotations
.. _changes_7-6-9:
v7.6.9Compare Source
Tomas Uribe fixed <pull 1901_>_ a performance problem in the XMLreport. Large code bases should produce XML reports much faster now.
.. _pull 1901:https://github.com/nedbat/coveragepy/pull/19011
.. _changes_7-6-8:
pycqa/flake8 (flake8)
v7.1.1Compare Source
v7.1.0Compare Source
canonical/operator (ops)
v2.17.1Compare Source
Fixes
push_pathopen in binary mode so it works on non-text files (#1458)Documentation
MaintenanceStatusfor local issues (#1397)collect-statusis is run on every hook (#1399)ogp:urlproperties Sphinx generates (#1411)READTHEDOCScontext variable (#1410)StoredStateis stored, and the upgrade behaviour (#1416)stop_servicesdocstring (#1457)Continuous Integration
Refactoring
pydantic/pydantic (pydantic)
v1.10.20Compare Source
RobertCraigie/pyright-python (pyright)
v1.1.391Compare Source
v1.1.390Compare Source
pytest-dev/pytest (pytest)
v8.3.4Compare Source
pytest 8.3.4 (2024-12-01)
Bug fixes
#12592: Fixed
KeyError{.interpreted-text role="class"} crash when using--import-mode=importlibin a directory layout where a directory contains a child directory with the same name.#12818: Assertion rewriting now preserves the source ranges of the original instructions, making it play well with tools that deal with the
AST, like executing.#12849: ANSI escape codes for colored output now handled correctly in
pytest.fail{.interpreted-text role="func"} with [pytrace=False]{.title-ref}.#9353:
pytest.approx{.interpreted-text role="func"} now uses strict equality when given booleans.Improved documentation
#10558: Fix ambiguous docstring of
pytest.Config.getoption{.interpreted-text role="func"}.#10829: Improve documentation on the current handling of the
--basetempoption and its lack of retention functionality (temporary directory location and retention{.interpreted-text role="ref"}).#12866: Improved cross-references concerning the
recwarn{.interpreted-text role="fixture"} fixture.#12966: Clarify
filterwarnings{.interpreted-text role="ref"} docs on filter precedence/order when using multiple@pytest.mark.filterwarnings <pytest.mark.filterwarnings ref>{.interpreted-text role="ref"} marks.Contributor-facing changes
pytest-dev/pytest-asyncio (pytest-asyncio)
v0.25.1: pytest-asyncio 0.25.1Compare Source
v0.25.0: pytest-asyncio 0.25.0Compare Source
0.25.0 (2024-12-13)
@pytest.fixturein strict mode. This will become an error in a future version of flake8-asyncio. #979v0.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.
Configuration
📅 Schedule: Branch creation - "after 1am and before 3am 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.