generated from canonical/template-operator
-
Notifications
You must be signed in to change notification settings - Fork 14
Update Python dependencies (major) #424
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
Open
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/major-python-dependencies
base: main
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.
Open
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
299f50e
to
3536b0c
Compare
taurus-forever
approved these changes
Apr 3, 2024
carlcsaposs-canonical
added a commit
to canonical/data-platform-workflows
that referenced
this pull request
Apr 3, 2024
a15485a
to
89420c5
Compare
89420c5
to
bddeec4
Compare
0aaa3c1
to
6084715
Compare
6084715
to
5903427
Compare
5903427
to
b88de15
Compare
8cb7d6f
to
d39161d
Compare
d39161d
to
9fa06a8
Compare
f9b7e32
to
8f32a85
Compare
8f32a85
to
61bff6f
Compare
b501021
to
6fe0447
Compare
49116f8
to
5f9bcd6
Compare
d2208ed
to
889821c
Compare
3cf9594
to
fdb483c
Compare
8352a44
to
11cb7e7
Compare
11cb7e7
to
0289cf3
Compare
580584d
to
120a74d
Compare
0f7ad2b
to
316b390
Compare
69e932d
to
9a92d0e
Compare
84c17b8
to
16a88df
Compare
20d0969
to
4dc7cb8
Compare
4dc7cb8
to
18abbc7
Compare
5ae998a
to
0f3e366
Compare
0f3e366
to
9850b5a
Compare
9850b5a
to
e56f4ec
Compare
c32c098
to
e3477b2
Compare
33f3b0a
to
22937a5
Compare
22937a5
to
57a3626
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.54
->1.0.0
44.0.2
->45.0.4
1.7.0
->2.1.3
^7.4.0
->^8.4.1
^8.2.2
->^9.1.2
Release Notes
canonical/cos-lib (cosl)
v1.0.0
Compare Source
What's Changed
coordinated_workers
out ofcosl
by @michaeldmitry in https://github.com/canonical/cos-lib/pull/146Full Changelog: canonical/cos-lib@0.1.1...1.0.0
v0.1.1
Compare Source
What's Changed
coordinated_workers
module by @michaeldmitry in https://github.com/canonical/cos-lib/pull/148Full Changelog: canonical/cos-lib@0.1.0...0.1.1
v0.1.0
Compare Source
What's Changed
Full Changelog: canonical/cos-lib@0.0.57...0.1.0
v0.0.57
Compare Source
Surface an otherwise hard-to-spot issue, where the ingress is handing the coordinated workers an HTTPS endpoint, but the coordinator and workers themselves don't have a certificates relation.
Workers and coordinator now set blocked on TLS misconfiguration.
What's Changed
test-distributed-charms
CI workflow by @michaeldmitry in https://github.com/canonical/cos-lib/pull/134Full Changelog: canonical/cos-lib@0.0.56...0.0.57
v0.0.56
Compare Source
What's Changed
Full Changelog: canonical/cos-lib@0.0.55...0.0.56
v0.0.55
Compare Source
What's Changed
Full Changelog: canonical/cos-lib@0.0.54...0.0.55
pyca/cryptography (cryptography)
v45.0.4
Compare Source
v45.0.3
Compare Source
v45.0.2
Compare Source
v45.0.1
Compare Source
v45.0.0
Compare Source
v44.0.3
Compare Source
python-poetry/poetry-core (poetry-core)
v2.1.3
Compare Source
Changed
Fixed
project
section were treated as non-optional when a source was defined for them in thetool.poetry
section (#857).===
were not parsed correctly (#860).extra
markers with a value starting with "in" were not validated correctly (#862).WheelBuilder
was unnecessarily difficult (#855).v2.1.2
Compare Source
Changed
Fixed
#846).
extra
markers were not simplified (#842,#845,
#847).
python_version
markers was not recognized as empty (#849).python_version
markers were not simplified (#848,#851).
v2.1.1
Compare Source
Fixed
python_version
marker resulted in an invalid marker (#838).v2.1.0
Compare Source
Added
poetry
instance (#319).has_upper_bound method
toVersionConstraint
(#833).Changed
extra
markers (#818).#832).
python_version
markers (#826).Fixed
__pycache__
directory and*.pyc
files were included in sdists and wheels (#835).v2.0.1
Compare Source
Changed
Home-page
withProject-URL: Homepage
(#807).Fixed
tool.poetry.packages
without a specifiedformat
were not initialized with the default value resulting in aKeyError
(#805).project.urls
entries were not processed correctly resulting in aKeyError
(#807).project.dependencies
viatool.poetry.dependencies
were ignored ifproject.optional-dependencies
were defined (#811).v2.0.0
Compare Source
Added
project
section in thepyproject.toml
file according to PEP 621 (#708,#792).
platform_release
marker (#722).in
/not in
in generic constraints (#722).SOURCE_DATE_EPOCH
when building packages (#766,#781).
Changed
METADATA
files with version 2.3 instead of 2.2 (#707).allow-prereleases
a tri-state setting (#783).Error
suffix (#767).x
in version constraints (#770).#769).
tool.poetry.dev-dependencies
in favor oftool.poetry.group.dev.dependencies
(#754).Package.python_marker
(#446).pyproject.toml
file cannot be parsed (#734).readme
files (#752).#718,
#727,
#736,
#746,
#755,
#764,
#784,
#787,
#795).
Fixed
platlib
directory of the wrong Python was used (#726).+
was not allowed in git URL paths (#765).Vendoring
fastjsonschema==2.21.1
lark==1.2.2
packaging==24.2
tomli==2.2.1
v1.9.1
Compare Source
Added
3.13
to the list of available Python versions (#747).v1.9.0
Compare Source
Added
to
key intool.poetry.packages
to allow custom subpackage names (#672).tool.poetry.package-mode
key to support non-package mode (#661).Changed
#669,
#678,
#694).
poetry.core.masonry.builder
(#682).Fixed
Vendoring
fastjsonschema==2.19.1
lark==1.1.8
v1.8.1
Compare Source
Fixed
git+
could not be parsed anymore (#657).v1.8.0
Compare Source
Added
3.12
to the list of available Python versions (#631).Changed
extra
markers (#636).#646).
Dependency.transitive_python_versions
(#648).Dependency.transitive_python_constraint
(#649).Fixed
lib
folder was added to the wheel (#634).Vendoring
jsonschema
withfastjsonschema
.lark==1.1.8
packaging==23.2
pytest-dev/pytest (pytest)
v8.4.1
Compare Source
pytest 8.4.1 (2025-06-17)
Bug fixes
#13461: Corrected
_pytest.terminal.TerminalReporter.isatty
to supportbeing called as a method. Before it was just a boolean which could
break correct code when using
-o log_cli=true
).#13477: Reintroduced
pytest.PytestReturnNotNoneWarning
{.interpreted-text role="class"} which was removed by accident in pytest [8.4]{.title-ref}.This warning is raised when a test functions returns a value other than
None
, which is often a mistake made by beginners.See
return-not-none
{.interpreted-text role="ref"} for more information.#13497: Fixed compatibility with
Twisted 25+
.Improved documentation
faulthandler
not working on Windows.v8.4.0
Compare Source
pytest 8.4.0 (2025-06-02)
Removals and backward incompatible breaking changes
#11372: Async tests will now fail, instead of warning+skipping, if you don't have any suitable plugin installed.
#12346: Tests will now fail, instead of raising a warning, if they return any value other than None.
#12874: We dropped support for Python 3.8 following its end of life (2024-10-07).
#12960: Test functions containing a yield now cause an explicit error. They have not been run since pytest 4.0, and were previously marked as an expected failure and deprecation warning.
See
the docs <yield tests deprecated>
{.interpreted-text role="ref"} for more information.Deprecations (removal in next major release)
autouse=True
. For guidance on how to work around this warning seesync-test-async-fixture
{.interpreted-text role="ref"}.New features
#11538: Added
pytest.RaisesGroup
{.interpreted-text role="class"} as an equivalent topytest.raises
{.interpreted-text role="func"} for expectingExceptionGroup
{.interpreted-text role="exc"}. Also addspytest.RaisesExc
{.interpreted-text role="class"} which is now the logic behindpytest.raises
{.interpreted-text role="func"} and used as parameter topytest.RaisesGroup
{.interpreted-text role="class"}.RaisesGroup
includes the ability to specify multiple different expected exceptions, the structure of nested exception groups, and flags for emulatingexcept* <except_star>
{.interpreted-text role="ref"}. Seeassert-matching-exception-groups
{.interpreted-text role="ref"} and docstrings for more information.#12081: Added
capteesys
{.interpreted-text role="fixture"} to capture AND pass output to next handler set by--capture=
.#12504:
pytest.mark.xfail
{.interpreted-text role="func"} now acceptspytest.RaisesGroup
{.interpreted-text role="class"} for theraises
parameter when you expect an exception group. You can also pass apytest.RaisesExc
{.interpreted-text role="class"} if you e.g. want to make use of thecheck
parameter.#12713: New [--force-short-summary]{.title-ref} option to force condensed summary output regardless of verbosity level.
This lets users still see condensed summary output of failures for quick reference in log files from job outputs, being especially useful if non-condensed output is very verbose.
#12749: pytest traditionally collects classes/functions in the test module namespace even if they are imported from another file.
For example:
contents of src/domain.py
contents of tests/test_testament.py
#12765: Thresholds to trigger snippet truncation can now be set with
truncation_limit_lines
{.interpreted-text role="confval"} andtruncation_limit_chars
{.interpreted-text role="confval"}.See
truncation-params
{.interpreted-text role="ref"} for more information.#13125:
console_output_style
{.interpreted-text role="confval"} now supportstimes
to show execution time of each test.#13192:
pytest.raises
{.interpreted-text role="func"} will now raise a warning when passing an empty string tomatch
, as this will match against any value. Usematch="^$"
if you want to check that an exception has no message.#13192:
pytest.raises
{.interpreted-text role="func"} will now print a helpful string diff if matching fails and the match parameter has^
and$
and is otherwise escaped.#13192: You can now pass
with pytest.raises(check=fn): <pytest.raises>
{.interpreted-text role="func"}, wherefn
is a function which takes a raised exception and returns a boolean. Theraises
fails if no exception was raised (as usual), passes if an exception is raised andfn
returnsTrue
(as well asmatch
and the type matching, if specified, which are checked before), and propagates the exception iffn
returnsFalse
(which likely also fails the test).#13228:
hidden-param
{.interpreted-text role="ref"} can now be used inid
ofpytest.param
{.interpreted-text role="func"} or inids
ofMetafunc.parametrize <pytest.Metafunc.parametrize>
{.interpreted-text role="py:func"}.It hides the parameter set from the test name.
#13253: New flag:
--disable-plugin-autoload <disable_plugin_autoload>
{.interpreted-text role="ref"} which works as an alternative toPYTEST_DISABLE_PLUGIN_AUTOLOAD
{.interpreted-text role="envvar"} when setting environment variables is inconvenient; and allows setting it in config files withaddopts
{.interpreted-text role="confval"}.Improvements in existing functionality
#10224: pytest's
short
andlong
traceback styles (how-to-modifying-python-tb-printing
{.interpreted-text role="ref"})now have partial
657
{.interpreted-text role="pep"} support and will show specific code segments in thetraceback.
-- by
ammaraskar
{.interpreted-text role="user"}#11118: Now
pythonpath
{.interpreted-text role="confval"} configures [$PYTHONPATH]{.title-ref} earlier than before during the initialization process, which now also affects plugins loaded via the [-p]{.title-ref} command-line option.-- by
millerdev
{.interpreted-text role="user"}#11381: The
type
parameter of theparser.addini
method now accepts ["int"]{.title-ref} and"float"
parameters, facilitating the parsing of configuration values in the configuration file.Example:
The [pytest.ini]{.title-ref} file:
#11525: Fixtures are now clearly represented in the output as a "fixture object", not as a normal function as before, making it easy for beginners to catch mistakes such as referencing a fixture declared in the same module but not requested in the test function.
-- by
the-compiler
{.interpreted-text role="user"} andglyphack
{.interpreted-text role="user"}#12426: A warning is now issued when
pytest.mark.usefixtures ref
{.interpreted-text role="ref"} is used without specifying any fixtures. Previously, empty usefixtures markers were silently ignored.#12707: Exception chains can be navigated when dropped into Pdb in Python 3.13+.
#12736: Added a new attribute [name]{.title-ref} with the fixed value ["pytest tests"]{.title-ref} to the root tag [testsuites]{.title-ref} of the junit-xml generated by pytest.
This attribute is part of many junit-xml specifications and is even part of the [junit-10.xsd]{.title-ref} specification that pytest's implementation is based on.
#12943: If a test fails with an exceptiongroup with a single exception, the contained exception will now be displayed in the short test summary info.
#12958: A number of
unraisable <unraisable>
{.interpreted-text role="ref"} enhancements:tracemalloc
{.interpreted-text role="mod"} allocation traceback (if available).StopIteration
{.interpreted-text role="class"} in test failures.pytest.PytestUnraisableExceptionWarning
{.interpreted-text role="class"} exception if raised.repr
of the unraisable object in the unraisable hook so you get the latest information if available, and should help with resurrection of the object.#13010:
pytest.approx
{.interpreted-text role="func"} now can compare collections that contain numbers and non-numbers mixed.#13016: A number of
threadexception <unraisable>
{.interpreted-text role="ref"} enhancements:tracemalloc
{.interpreted-text role="mod"} allocation traceback (if available).StopIteration
{.interpreted-text role="class"} in test failures.pytest.PytestUnhandledThreadExceptionWarning
{.interpreted-text role="class"} exception if raised.name
of the thread object in the excepthook which should help with resurrection of the thread.#13031: An empty parameter set as in
pytest.mark.parametrize([], ids=idfunc)
will no longer trigger a call toidfunc
with internal objects.#13115: Allows supplying
ExceptionGroup[Exception]
andBaseExceptionGroup[BaseException]
topytest.raises
to keep full typing onExceptionInfo <pytest.ExceptionInfo>
{.interpreted-text role="class"}:Parametrizing with other exception types remains an error - we do not check the types of child exceptions and thus do not permit code that might look like we do.
#13122: The
--stepwise
mode received a number of improvements:It no longer forgets the last failed test in case pytest is executed later without the flag.
This enables the following workflow:
--stepwise
, pytest then stops at the first failing test;--stepwise
flag (for example in an IDE), until it is fixed.--stepwise
again and pytest will continue from the previously failed test, and if it passes, continue on to the next tests.Previously, at step 3, pytest would start from the beginning, forgetting the previously failed test.
This change however might cause issues if the
--stepwise
mode is used far apart in time, as the state might get stale, so the internal state will be reset automatically in case the test suite changes (for now only the number of tests are considered for this, we might change/improve this on the future).New
--stepwise-reset
/--sw-reset
flag, allowing the user to explicitly reset the stepwise state and restart the workflow from the beginning.#13308: Added official support for Python 3.14.
#13380: Fix
ExceptionGroup
{.interpreted-text role="class"} traceback filtering to exclude pytest internals.#13415: The author metadata of the BibTex example is now correctly formatted with last names following first names.
An example of BibLaTex has been added.
BibTex and BibLaTex examples now clearly indicate that what is cited is software.
-- by
willynilly
{.interpreted-text role="user"}#13420: Improved test collection performance by optimizing path resolution used in
FSCollector
.#13457: The error message about duplicate parametrization no longer displays an internal stack trace.
#4112: Using
pytest.mark.usefixtures <pytest.mark.usefixtures ref>
{.interpreted-text role="ref"} onpytest.param
{.interpreted-text role="func"} now produces an error instead of silently doing nothing.#5473: Replace [:]{.title-ref} with [;]{.title-ref} in the assertion rewrite warning message so it can be filtered using standard Python warning filters before calling
pytest.main
{.interpreted-text role="func"}.pygments
dependency is now required, causing output always to be source-highlighted (unless disabled via the--code-highlight=no
CLI option).Bug fixes
#10404: Apply filterwarnings from config/cli as soon as possible, and revert them as late as possible
so that warnings as errors are collected throughout the pytest run and before the
unraisable and threadexcept hooks are removed.
This allows very late warnings and unraisable/threadexcept exceptions to fail the test suite.
This also changes the warning that the lsof plugin issues from PytestWarning to the new warning PytestFDWarning so it can be more easily filtered.
#11067: The test report is now consistent regardless if the test xfailed via
pytest.mark.xfail <pytest.mark.xfail ref>
{.interpreted-text role="ref"} orpytest.fail
{.interpreted-text role="func"}.Previously, xfailed tests via the marker would have the string
"reason: "
prefixed to the message, while those xfailed via the function did not. The prefix has been removed.#12008: In
11220
{.interpreted-text role="pr"}, an unintended change in reordering was introduced by changing the way indices were assigned to direct params. More specifically, before that change, the indices of direct params to metafunc's callspecs were assigned after all parametrizations took place. Now, that change is reverted.#12863: Fix applying markers, including
pytest.mark.parametrize <pytest.mark.parametrize ref>
{.interpreted-text role="ref"} when placed above [@staticmethod]{.title-ref} or [@classmethod]{.title-ref}.#12929: Handle StopIteration from test cases, setup and teardown correctly.
#12938: Fixed
--durations-min
argument not respected if-vv
is used.#12946: Fixed missing help for
pdb
{.interpreted-text role="mod"} commands wrapped by pytest -- byadamchainz
{.interpreted-text role="user"}.#12981: Prevent exceptions in
pytest.Config.add_cleanup
{.interpreted-text role="func"} callbacks preventing further cleanups.#13047: Restore
pytest.approx
{.interpreted-text role="func"} handling of equality checks between [bool]{.title-ref} and [numpy.bool_]{.title-ref} types.Comparing [bool]{.title-ref} and [numpy.bool_]{.title-ref} using
pytest.approx
{.interpreted-text role="func"} accidentally changed in version [8.3.4]{.title-ref} and [8.3.5]{.title-ref} to no longer match:This has now been fixed:
#13119: Improved handling of invalid regex patterns for filter warnings by providing a clear error message.
#13175: The diff is now also highlighted correctly when comparing two strings.
#13248: Fixed an issue where passing a
scope
inMetafunc.parametrize <pytest.Metafunc.parametrize>
{.interpreted-text role="py:func"} withindirect=True
could result in other fixtures being unable to depend on the parametrized fixture.
#13291: Fixed
repr
ofattrs
objects in assertion failure messages when usingattrs>=25.2
.#13312: Fixed a possible
KeyError
crash on PyPy during collection of tests involving higher-scoped parameters.#13345: Fix type hints for
pytest.TestReport.when
{.interpreted-text role="attr"} andpytest.TestReport.location
{.interpreted-text role="attr"}.#13377: Fixed handling of test methods with positional-only parameter syntax.
Now, methods are supported that formally define
self
as positional-onlyand/or fixture parameters as keyword-only, e.g.:
Before, this caused an internal error in pytest.
#13384: Fixed an issue where pytest could report negative durations.
#13420: Added
lru_cache
tonodes._check_initialpaths_for_relpath
.#9037: Honor
disable_test_id_escaping_and_forfeit_all_rights_to_community_support
{.interpreted-text role="confval"} when escaping ids in parametrized tests.Improved documentation
#12535: [This
example]{.title-ref}<https://docs.pytest.org/en/latest/example/simple.html#making-test-result-information-available-in-fixtures>
showed
print
statements that do not exactly reflect what thedifferent branches actually do. The fix makes the example more precise.
#13218: Pointed out in the
pytest.approx
{.interpreted-text role="func"} documentation that it considers booleans unequal to numeric zero or one.#13221: Improved grouping of CLI options in the
--help
output.#6649: Added
~pytest.TerminalReporter
{.interpreted-text role="class"} to theapi-reference
{.interpreted-text role="ref"} documentation page.#8612: Add a recipe for handling abstract test classes in the documentation.
A new example has been added to the documentation to demonstrate how to use a mixin class to handle abstract
test classes without manually setting the
__test__
attribute for subclasses.This ensures that subclasses of abstract test classes are automatically collected by pytest.
Packaging updates and notes for downstreams
colorama
,iniconfig
,and
packaging
; and bumped the minimum allowed versionof
exceptiongroup
forpython_version<'3.11'
from a releasecandidate to a full release.
Contributor-facing changes
#12017: Mixed internal improvements:
MockTiming
into_pytest.timing
.-- by
RonnyPfannschmidt
{.interpreted-text role="user"}#12647: Fixed running the test suite with the
hypothesis
pytest plugin.Miscellaneous internal changes
~pytest.TerminalReporter
{.interpreted-text role="class"} to the public pytest API, as it is part of the signature of thepytest_terminal_summary
{.interpreted-text role="hook"} hook.v8.3.5
Compare Source
pytest 8.3.5 (2025-03-02)
Bug fixes
-vv
verbosity.libedit
build of Python, such as on macOS or with uv-managed Python binaries from thepython-build-standalone
project. This could manifest e.g. by a broken prompt when usingPdb
, or seeing empty inputs with manual usage ofinput()
and suspended capturing.AttributeError
{.interpreted-text role="class"} crash when using--import-mode=importlib
when top-level directory same name as another module of the standard library.--import-mode=importlib
, a directory containing py file with the same name would cause anImportError
Improved documentation
#12842: Added dedicated page about using types with pytest.
See
types
{.interpreted-text role="ref"} for detailed usage.Contributor-facing changes
test_terminal.py
with Pygments >= 2.19.0when building Sphinx docs -- by
webknjaz
{.interpreted-text role="user"}.v8.3.4
Compare Source
pytest 8.3.4 (2024-12-01)
Bug fixes
#12592: Fixed
KeyError
{.interpreted-text role="class"} crash when using--import-mode=importlib
in 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
--basetemp
option 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.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 `Avas
Configuration
📅 Schedule: Branch creation - Between 01:00 AM and 05:59 AM, only on Tuesday ( * 1-5 * * 2 ) 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.