fix(deps): update python dependencies #359
Open
+8
−8
Conversation
This file contains hidden or 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
Contributor
Author
|
renovate
bot
force-pushed
the
renovate/python-dependencies
branch
2 times, most recently
from
1e91c4d to
b639588
Compare
renovate
bot
force-pushed
the
renovate/python-dependencies
branch
3 times, most recently
from
61bb785 to
77a1c39
Compare
renovate
bot
force-pushed
the
renovate/python-dependencies
branch
5 times, most recently
from
1559bc6 to
524ae17
Compare
renovate
bot
force-pushed
the
renovate/python-dependencies
branch
4 times, most recently
from
f2c5747 to
9c1742c
Compare
renovate
bot
force-pushed
the
renovate/python-dependencies
branch
4 times, most recently
from
89e55e2 to
c9d6b83
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/python-dependencies
branch
6 times, most recently
from
3e548ab to
e24e488
Compare
renovate
bot
force-pushed
the
renovate/python-dependencies
branch
2 times, most recently
from
5d28f46 to
f794aae
Compare
renovate
bot
force-pushed
the
renovate/python-dependencies
branch
5 times, most recently
from
2368cc5 to
51d7bf2
Compare
renovate
bot
force-pushed
the
renovate/python-dependencies
branch
5 times, most recently
from
a7143f1 to
7a478ab
Compare
renovate
bot
force-pushed
the
renovate/python-dependencies
branch
2 times, most recently
from
dbd813b to
d97b727
Compare
renovate
bot
force-pushed
the
renovate/python-dependencies
branch
from
d97b727 to
cd6aa8a
Compare
renovate
bot
force-pushed
the
renovate/python-dependencies
branch
2 times, most recently
from
00b702f to
4483ece
Compare
renovate
bot
force-pushed
the
renovate/python-dependencies
branch
5 times, most recently
from
f333b54 to
6787090
Compare
renovate
bot
force-pushed
the
renovate/python-dependencies
branch
7 times, most recently
from
4404fe8 to
cc1dee3
Compare
renovate
bot
force-pushed
the
renovate/python-dependencies
branch
from
cc1dee3 to
fac9cd0
Compare
renovate
bot
force-pushed
the
renovate/python-dependencies
branch
from
fac9cd0 to
0751f18
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:
1.3.0->1.3.17.0.0->7.3.04.24.1->4.25.1^0.15.3->^0.18.01.6.11->1.8.112.21.1->2.23.1^0.13.3->^0.15.04.15.2->4.15.4^0.21.1->^0.26.0^0.36.0->^0.43.00.18.0->0.29.0Release Notes
canonical/cos-lib (cosl)
v1.3.1Compare Source
What's Changed
New Contributors
Full Changelog: canonical/cos-lib@1.3.0...1.3.1
pycqa/flake8 (flake8)
v7.3.0Compare Source
v7.2.0Compare Source
v7.1.2Compare Source
v7.1.1Compare Source
v7.1.0Compare Source
python-jsonschema/jsonschema (jsonschema)
v4.25.1Compare Source
=======
Validatorprotocol's type annotations (#1396).v4.25.0Compare Source
=======
iriandiri-referenceformats to theformat-nongplextra via the MIT-licensedrfc3987-syntax.They were alread supported by the
formatextra. (#1388).gtsystem/lightkube (lightkube)
v0.18.0Compare Source
What's Changed
Bug fix
Typing improvements
ruffformatting, broaderrufflinting rule set and fix corresponding errors by @jonded94 in #122New Contributors
Full Changelog: gtsystem/lightkube@v0.17.2...v0.18.0
v0.17.2Compare Source
What's Changed
apiVersionandkindautomatically set as post init.List(Async)IteratortoList(Async)Iterableto reflect the corr… by @gtsystem in #89proxyconfiguration by @Akustav in #96New Contributors
Full Changelog: gtsystem/lightkube@v0.17.0...v0.17.2
v0.17.1Compare Source
v0.17.0Compare Source
New features
client.list()now returns an iterable with a special propertyresourceVersionto implement list + watch pattern by @XeCycle in #88Bug fixes
Breaking changes
client.list()now returns an Iteratable instead of an Iterator. If you are consuming the list usingnext()you will need to get an iterator first callingiter(list). No changes are needed If you are consuming the returned data via a for loop.Full Changelog: gtsystem/lightkube@v0.16.0...v0.17.0
v0.16.2Compare Source
v0.16.1Compare Source
v0.16.0Compare Source
What's Changed
Bug fixes
ExecCredential, lightkube now accepts theenvparameter when set to null explicitly (Azure kubelogin compatiblity) by @raminqaf in #80New Contributors
Full Changelog: gtsystem/lightkube@v0.15.4...v0.16.0
canonical/mongo-single-kernel-library (mongo-charms-single-kernel)
v1.8.11Compare Source
What's Changed
Full Changelog: canonical/mongo-single-kernel-library@v1.8.10...v1.8.11
v1.8.10Compare Source
What's Changed
charmed-prefix) by @patriciareinoso in #119Full Changelog: canonical/mongo-single-kernel-library@v1.8.9...v1.8.10
v1.8.9Compare Source
What's Changed
Full Changelog: canonical/mongo-single-kernel-library@v1.8.8...v1.8.9
v1.8.8Compare Source
What's Changed
Full Changelog: canonical/mongo-single-kernel-library@v1.8.7...v1.8.8
v1.8.7Compare Source
What's Changed
Full Changelog: canonical/mongo-single-kernel-library@v1.8.6...v1.8.7
v1.8.6Compare Source
What's Changed
Full Changelog: canonical/mongo-single-kernel-library@v1.8.5...v1.8.6
v1.8.5Compare Source
What's Changed
Full Changelog: canonical/mongo-single-kernel-library@v1.8.4...v1.8.5
v1.8.4Compare Source
What's Changed
Full Changelog: canonical/mongo-single-kernel-library@v1.8.3...v1.8.4
v1.8.3Compare Source
What's Changed
Full Changelog: canonical/mongo-single-kernel-library@v1.8.2...v1.8.3
v1.8.2Compare Source
What's Changed
Full Changelog: canonical/mongo-single-kernel-library@v1.8.1...v1.8.2
v1.8.1Compare Source
What's Changed
Full Changelog: canonical/mongo-single-kernel-library@v1.8.0...v1.8.1
v1.7.7Compare Source
What's Changed
Full Changelog: canonical/mongo-single-kernel-library@v1.7.6...v1.7.7
v1.7.6Compare Source
What's Changed
Full Changelog: canonical/mongo-single-kernel-library@v1.7.5...v1.7.6
v1.7.5Compare Source
What's Changed
Full Changelog: canonical/mongo-single-kernel-library@v1.7.4...v1.7.5
v1.7.3Compare Source
What's Changed
Full Changelog: canonical/mongo-single-kernel-library@v1.7.2...v1.7.3
v1.7.2Compare Source
What's Changed
Full Changelog: canonical/mongo-single-kernel-library@v1.7.1...v1.7.2
v1.7.1Compare Source
What's Changed
Full Changelog: canonical/mongo-single-kernel-library@v1.7.0...v1.7.1
canonical/operator (ops)
v2.23.1: : Add the remote unit to Relation.data, but not Relation.unitsCompare Source
This is a small bug-fix release for the 2.x series that addresses issues with the recent feature making relation data available in relation-departed events. Rather than inserting the remote unit into
Relation.units, the data is available fromRelation.data, without changingRelation.units.What's Changed
Fixes
Relation.databut notRelation.unitsin #1928Documentation
self.appandself.unitin #1856CI
Full Changelog: canonical/operator@2.23.0...2.23.1
v2.23.0Compare Source
Features
Fixes
Documentation
CI
v2.22.0Compare Source
Features
Fixes
__init__(#1737)ops.testing(#1754)Documentation
CI
ops[tracing]integration tests (#1686)alertmanager-k8s-operatorin observability charm tests (#1753)ops[tracing]addition (#1755)PyCQA/pep8-naming (pep8-naming)
v0.15.1Compare Source
v0.15.0Compare Source
v0.14.1Compare Source
v0.14.0Compare Source
@typing.override.ignore-namesglobbing on all platforms.mongodb/mongo-python-driver (pymongo)
v4.15.4: PyMongo 4.15.4Compare Source
Community notes: https://www.mongodb.com/community/forums/t/pymongo-4-15-4-released/331292
v4.15.3: PyMongo 4.15.3Compare Source
Community notes: https://www.mongodb.com/community/forums/t/pymongo-4-15-3-released/329778
pytest-dev/pytest-asyncio (pytest-asyncio)
v0.26.0: pytest-asyncio 0.26.0Compare Source
pytest_asyncio.fixture#1045typing-extensionsas additional dependency for Python<3.10#1045v0.25.3: pytest-asyncio 0.25.3Compare Source
v0.25.2: pytest-asyncio 0.25.2Compare Source
loop.shutdown_asyncgens()before closing the event loop to ensure async generators are closed in the same manner asasyncio.rundoes #1034v0.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.
charmed-kubernetes/pytest-operator (pytest-operator)
v0.43.2[Compare Source](https://redirect.github.com/charmed-kubernetes/pytest-operator/com
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.