-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Lock file maintenance Python dependencies #79
Open
renovate
wants to merge
1
commit into
2/edge
Choose a base branch
from
renovate/python-dependencies
base: 2/edge
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+18
−18
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
force-pushed
the
renovate/python-dependencies
branch
4 times, most recently
from
July 12, 2024 01:05
f008c48
to
4c461d3
Compare
renovate
bot
force-pushed
the
renovate/python-dependencies
branch
4 times, most recently
from
July 25, 2024 01:46
175104d
to
f1755e7
Compare
renovate
bot
force-pushed
the
renovate/python-dependencies
branch
3 times, most recently
from
July 30, 2024 01:39
b836e2a
to
8e33986
Compare
renovate
bot
force-pushed
the
renovate/python-dependencies
branch
4 times, most recently
from
August 12, 2024 02:07
918aff1
to
02d060e
Compare
renovate
bot
force-pushed
the
renovate/python-dependencies
branch
5 times, most recently
from
August 21, 2024 03:01
1b77c1a
to
1197eed
Compare
renovate
bot
force-pushed
the
renovate/python-dependencies
branch
3 times, most recently
from
August 29, 2024 02:46
b3ffdc6
to
2ca6213
Compare
renovate
bot
force-pushed
the
renovate/python-dependencies
branch
3 times, most recently
from
September 9, 2024 02:01
acd70c0
to
db3a645
Compare
renovate
bot
force-pushed
the
renovate/python-dependencies
branch
2 times, most recently
from
September 11, 2024 01:48
9b5ee18
to
ad1632c
Compare
renovate
bot
force-pushed
the
renovate/python-dependencies
branch
4 times, most recently
from
September 17, 2024 01:57
8c78db2
to
35df86a
Compare
renovate
bot
force-pushed
the
renovate/python-dependencies
branch
3 times, most recently
from
September 24, 2024 01:07
1af6e27
to
95b8f1c
Compare
renovate
bot
force-pushed
the
renovate/python-dependencies
branch
4 times, most recently
from
October 3, 2024 01:05
88ef484
to
b0f4abc
Compare
renovate
bot
force-pushed
the
renovate/python-dependencies
branch
3 times, most recently
from
October 10, 2024 01:35
72c261d
to
31acec1
Compare
renovate
bot
force-pushed
the
renovate/python-dependencies
branch
2 times, most recently
from
October 15, 2024 02:10
95552ba
to
c60cdc2
Compare
renovate
bot
force-pushed
the
renovate/python-dependencies
branch
from
October 18, 2024 02:03
c60cdc2
to
faf012b
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 participants
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.42
^7.5.1
->^7.6.3
^7.0.0
->^7.1.1
^2.13.0
->^2.17.0
2.15.0
->2.17.0
1.9.0
->1.9.1
1.10.17
->1.10.18
^1.10.17
->^1.10.18
^1.1.318
->^1.1.385
^8.2.2
->^8.3.3
^8.2.2
->^8.3.3
^0.21.2
->^0.24.0
^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
psf/black (black)
v24.10.0
Compare Source
Highlights
mypyc-compiled wheels. (#4436) (#4449)
safety issue in Python 3.12.5 that can cause Black's AST safety checks to fail. Please
use Python 3.12.6 or Python 3.12.4 instead. (#4447)
Stable style
X | Y
style unions.(#4453)
%%
magic (#4462)Preview style
def fn(*args: *tuple[*Ts, T]) -> None: pass
) (#4440)Caching
--unstable
(#4466)Packaging
blackd
now requires a newer version of aiohttp. (#4451)Output
canonical/cos-lib (cosl)
v0.0.42
Compare Source
What's Changed
Full Changelog: canonical/cos-lib@0.0.41...0.0.42
v0.0.41
Compare Source
Add LogForwarder in coordinator
v0.0.40
Compare 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.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
v0.0.16
Compare Source
What's Changed
Full Changelog: canonical/cos-lib@0.0.14...0.0.16
v0.0.15
Compare Source
What's Changed
New Contributors
Full Changelog: canonical/cos-lib@0.0.13...0.0.15
v0.0.14
Compare Source
v0.0.13
Compare Source
What's Changed
Full Changelog: canonical/cos-lib@0.0.12...0.0.13
nedbat/coveragepy (coverage)
v7.6.3
Compare 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.2
Compare 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:
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
v2.16.1
Compare Source
Fix
v2.16.0
Compare Source
Features
Refactor
Fixes
Documentation
Tests
CI
python-poetry/poetry-core (poetry-core)
v1.9.1
Compare Source
Added
3.13
to the list of available Python versions (#747).pydantic/pydantic (pydantic)
v1.10.18
Compare Source
to_lower_camel
to__all__
inutils.py
by @sydney-runkle (direct commit)mypy
v1 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/10146RobertCraigie/pyright-python (pyright)
v1.1.385
Compare Source
v1.1.384
Compare Source
v1.1.383
Compare Source
v1.1.382
Compare Source
v1.1.381
Compare Source
v1.1.380
Compare Source
v1.1.379
Compare Source
v1.1.378
Compare Source
v1.1.377
Compare Source
v1.1.376
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.2[Comp
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.