Lock file maintenance Python dependencies #5
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
from
f931de8 to
54d666f
Compare
renovate
bot
force-pushed
the
renovate/python-dependencies
branch
2 times, most recently
from
1c1f65d to
1be83c7
Compare
renovate
bot
force-pushed
the
renovate/python-dependencies
branch
from
1be83c7 to
8b7060b
Compare
renovate
bot
force-pushed
the
renovate/python-dependencies
branch
from
8b7060b to
003feeb
Compare
|
renovate
bot
force-pushed
the
renovate/python-dependencies
branch
3 times, most recently
from
3b2a9b7 to
51b8989
Compare
renovate
bot
force-pushed
the
renovate/python-dependencies
branch
from
51b8989 to
83d72b5
Compare
renovate
bot
force-pushed
the
renovate/python-dependencies
branch
from
83d72b5 to
1cea321
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.21->0.0.47^0.0.21->^0.0.47^7.6.1->^7.6.9^43.0.0->^43.0.3<=3.5.2.0-><=3.6.0.0^0.15.3->^0.15.72.15.0->2.17.1^2.15.0->^2.17.11.9.0->1.9.1^1.9.0->^1.9.1^3.2.1->^3.2.3^2.9.9->^2.9.10^2.9.9->^2.9.101.10.17->1.10.19^1.10.17->^1.10.19^8.3.2->^8.3.4^8.3.2->^8.3.4^0.36.0->^0.39.0^0.6.1->^0.8.3🔧 This Pull Request updates lock files to use the latest dependency versions.
Release Notes
canonical/cos-lib (cosl)
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
nedbat/coveragepy (coverage)
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:
v7.6.8Compare Source
Fix: the LCOV report code assumed that a branch line that took no branches
meant that the entire line was unexecuted. This isn't true in a few cases:
the line might always raise an exception, or might have been optimized away.
Fixes
issue 1896_.Fix: similarly, the HTML report will now explain that a line that jumps to
none of its expected destinations must have always raised an exception.
Previously, it would say something nonsensical like, "line 4 didn't jump to
line 5 because line 4 was never true, and it didn't jump to line 7 because
line 4 was always true." This was also shown in
issue 1896_... _issue 1896:https://github.com/nedbat/coveragepy/issues/18966
.. _changes_7-6-7:
v7.6.7Compare Source
so it's been restored to a conditional. Sorry for the churn.
.. _changes_7-6-6:
v7.6.6Compare Source
reported in
issue 1891_. The assert has been removed... _issue 1891:https://github.com/nedbat/coveragepy/issues/18911
.. _changes_7-6-5:
v7.6.5Compare Source
fix: fine-tuned the exact Python version (3.12.6) when exiting from
withstatements changed how they traced. This affected whether people saw the
fix for
issue 1880_.fix: isolate our code more from mocking in the os module that in rare cases
can cause
bizarre behavior <pytest-cov-666_>_.refactor: some code unreachable code paths in parser.py were changed to
asserts. If you encounter any of these, please let me know!
.. _pytest-cov-666:https://github.com/pytest-dev/pytest-cov/issues/6666
.. _changes_7-6-4:
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:
pyca/cryptography (cryptography)
v43.0.3Compare Source
v43.0.1Compare Source
juju/python-libjuju (juju)
v3.6.0.0Compare Source
What's Changed
Highlights
correct parsing of storage constraints, can be specified as strings or dicts
enable attachment of binary files as charm resources
allow newest websockets
better type hints, should be visible through pytest-operator in your integration tests
Full list
New Contributors
Full Changelog: juju/python-libjuju@3.5.2.0...3.6.0.0
v3.5.2.1Compare Source
3.5.2.1 is a hot-fix release to unblock your integration tests.
websockets==14.0was released recently, which broke your integration tests, unless you’ve manually put version specifiers on this library or locked your dependencies, because:_ws.openin python-libjuju got brokenThe hot-fix version restricts websockets to <14.0,>=8.1, so that you don’t have to.
Full Changelog: juju/python-libjuju@3.5.2.0...3.5.2.1
gtsystem/lightkube (lightkube)
v0.15.7Compare Source
v0.15.6Compare Source
v0.15.5Compare Source
v0.15.4What's Changed
__all__in__init__.pyby @max-muoto in https://github.com/gtsystem/lightkube/pull/70New Contributors
Full Changelog: gtsystem/lightkube@v0.15.2...v0.15.4
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
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
python-poetry/poetry-core (poetry-core)
v1.9.1Compare Source
Added
3.13to the list of available Python versions (#747).psycopg/psycopg (psycopg)
v3.2.3Compare Source
v3.2.2Compare Source
psycopg/psycopg2 (psycopg2)
v2.9.10Compare Source
pydantic/pydantic (pydantic)
v1.10.19Compare Source
isinstancecheck by @alicederyn in https://github.com/pydantic/pydantic/pull/10645v1.10.18Compare Source
to_lower_camelto__all__inutils.pyby @sydney-runkle (direct commit)mypyv1 plugin for mypy 1.11 release by @flaeppe in https://github.com/pydantic/pydantic/pull/10139.schema(by_alias=False)by @exs-dwoodward in https://github.com/pydantic/pydantic/pull/10146pytest-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
v8.3.3Compare Source
pytest 8.3.3 (2024-09-09)
Bug fixes
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 becomes conflicted, 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.