Update Python dependencies (6/edge) (major)#303
Open
renovate[bot] wants to merge 1 commit into6/edgefrom
Open
Conversation
renovate
Bot
added
the
not bug or enhancement
renovate
Bot
requested review from
a team,
Gu1nness,
Mehdi-Bendriss,
akram09,
patriciareinoso,
reneradoi,
skourta and
smethnani
and removed request for
a team
Author
|
github-actions
Bot
added
the
Libraries: Out of sync
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
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.1.7→>=1.0.1~2.21.1→~3.7.0~=2.21.1→~=3.7.0^0.21.1→^1.3.0Release Notes
canonical/operator (ops)
v3.7.0Compare Source
Features
breakpointin testing (#2363)Fixes
Documentation
Tests
CI
v3.6.0Compare Source
Features
ops.testing.Contextto 3.6.14 (#2316)Fixes
Model.get_binding()return type (#2329)ExecError.__str__, not full command line (#2336)MISSINGsentinel inops.Relation.save(#2306)Documentation
Tests
SCENARIO_BARE_CHARM_ERRORS=truein Ops tests that care (#2314)CI
versions.mddoc (#2323)v3.5.2Compare Source
Fixes
credential-getis available on k8s in newer Juju (#2307)setuptools_scmbuild dependency (#2310)Documentation
v3.5.1Compare Source
Fixes
parse_rfc3339for datetime parsing to support Juju 4 (#2264)additional_propertiesin the action meta in Juju 4 (#2250)KeyErroronauth-typewhen creatingCloudCredentialobject (#2268)_checks_actionshould return empty list when there are no changes (#2270)Documentation
Tests
CI
v3.5.0Compare Source
Features
Documentation
Tests
CI
v3.4.0Compare Source
Breaking Changes
Features
Fixes
ops.Pebble.pullcleans up temporary files if it errors (#2087)Documentation
simpleCharmcraft profile (#2138)Tests
Refactoring
CI
v3.3.1: : fix loading the Juju machine IDCompare Source
This is a bug-fix release to fix an issue introduced in Ops 3.3.0 (in production) and Ops 3.2.0 (in testing), where loading the Juju machine ID would fail if the ID was not an integer.
The type of the machine ID (both in
ops.JujuContextandtesting.Context) is changed frominttostr, so some code or tests may need to be adjusted to use the correct type.What's Changed
Fixes
Full Changelog: canonical/operator@3.3.0...3.3.1
v3.3.0Compare Source
Features
Fixes
Documentation
CI
v3.2.0Compare Source
Features
Documentation
Layerinstead of aLayerDictin the httpbin charm (#2003)CI
v3.1.0Compare Source
Features
Fixes
Documentation
opsversion in Charmcraft profiles (#1872)Tests
CI
v3.0.0Compare Source
The minimum version of Python for Ops 3.x is 3.10.
Documentation
CI
v2.23.2: : fix testing package buildCompare Source
What's Changed
This release fixes a recent build failure for
ops[testing].Fixes
setuptools_scmbuild dependency in #2318Documentation
Full Changelog: canonical/operator@2.23.1...2.23.2
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)pytest-dev/pytest-asyncio (pytest-asyncio)
v1.3.0: pytest-asyncio 1.3.0Compare Source
1.3.0 - 2025-11-10
Removed
Added
Notes for Downstream Packagers
pytest.Pytester.runpytest_subprocess. This prevents the test suite from accidentally using a system installation of pytest-asyncio, which could result in test errors. (#1275)v1.2.0: pytest-asyncio 1.2.0Compare Source
1.2.0 - 2025-09-12
Added
--asyncio-debugCLI option andasyncio_debugconfiguration option to enable asyncio debug mode for the default event loop. (#980)pytest.UsageErrorfor invalid configuration values ofasyncio_default_fixture_loop_scopeandasyncio_default_test_loop_scope. (#1189)Fixed
RuntimeError: There is no current event loop in thread 'MainThread'when any test unsets the event loop (such as when usingasyncio.runandasyncio.Runner). (#1177)@pytest.fixturein [strict]{.title-ref} mode. The warning message now refers to the correct package. (#1198)Notes for Downstream Packagers
tox.inifile provided by pytest-asyncio to run tests.v1.1.1: pytest-asyncio 1.1.1Compare Source
v1.1.1 - 2025-09-12
Notes for Downstream Packagers
- Addresses a build problem with setuptoos-scm >= 9 caused by invalid setuptools-scm configuration in pytest-asyncio. (#1192)
v1.1.0: pytest-asyncio 1.1.0Compare Source
Added
loop_scopeends (#200)Fixed
finallyclause of a task (#878)Notes for Downstream Packagers
v1.0.0: pytest-asyncio 1.0.0Compare Source
1.0.0 - 2025-05-26
Removed
(#1106)
Added
(#1025)
Changed
than per scope (e.g. per module). This reduces the number of fixtures
and speeds up collection time, especially for large test suites.
(#1107)
pytest.mark.asynciono longer forcesthat a pytest Collector exists at the level of the specified scope.
For example, a test function marked with
pytest.mark.asyncio(loop_scope="class")no longer requires a classsurrounding the test. This is consistent with the behavior of the
scope argument to
pytest_asyncio.fixture.(#1112)
Fixed
option.
(#630)
--doctest-ignore-import-errors(#797)
(#1052)
Notes for Downstream Packagers
(#1114)
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 according
Configuration
📅 Schedule: (in timezone Etc/UTC)
* 1-7 * * 2)🚦 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.