This repository has been archived by the owner on Mar 1, 2022. It is now read-only.
chore(deps): update dependency pytest to v6 #839
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:
>= 5.0.1, < 6.0.0
->>=5.0.1, <6.3.0
Release Notes
pytest-dev/pytest
v6.2.2
Compare Source
pytest 6.2.2 (2021-01-25)
Bug Fixes
faulthandler
plugin for occasions when running withtwisted.logger
and usingpytest --capture=no
.v6.2.1
Compare Source
pytest 6.2.1 (2020-12-15)
Bug Fixes
#7678: Fixed bug where
ImportPathMismatchError
would be raised for files compiled inthe host and loaded later from an UNC mounted path (Windows).
#8132: Fixed regression in
approx
: in 6.2.0approx
no longer raisesTypeError
when dealing with non-numeric types, falling back to normal comparison.Before 6.2.0, array types like tf.DeviceArray fell through to the scalar case,
and happened to compare correctly to a scalar if they had only one element.
After 6.2.0, these types began failing, because they inherited neither from
standard Python number hierarchy nor from
numpy.ndarray
.approx
now converts arguments tonumpy.ndarray
if they expose the arrayprotocol and are not scalars. This treats array-like objects like numpy arrays,
regardless of size.
v6.2.0
Compare Source
pytest 6.2.0 (2020-12-12)
Breaking Changes
Deprecations
#7469: Directly constructing/calling the following classes/functions is now deprecated:
_pytest.cacheprovider.Cache
_pytest.cacheprovider.Cache.for_config()
_pytest.cacheprovider.Cache.clear_cache()
_pytest.cacheprovider.Cache.cache_dir_from_config()
_pytest.capture.CaptureFixture
_pytest.fixtures.FixtureRequest
_pytest.fixtures.SubRequest
_pytest.logging.LogCaptureFixture
_pytest.pytester.Pytester
_pytest.pytester.Testdir
_pytest.recwarn.WarningsRecorder
_pytest.recwarn.WarningsChecker
_pytest.tmpdir.TempPathFactory
_pytest.tmpdir.TempdirFactory
These have always been considered private, but now issue a deprecation warning, which may become a hard error in pytest 7.0.0.
#7530: The
--strict
command-line option has been deprecated, use--strict-markers
instead.We have plans to maybe in the future to reintroduce
--strict
and make it an encompassing flag for all strictnessrelated options (
--strict-markers
and--strict-config
at the moment, more might be introduced in the future).#7988: The
@pytest.yield_fixture
decorator/function is now deprecated. Use pytest.fixture instead.yield_fixture
has been an alias forfixture
for a very long time, so can be search/replaced safely.Features
#5299: pytest now warns about unraisable exceptions and unhandled thread exceptions that occur in tests on Python>=3.8.
See unraisable for more information.
#7425: New pytester fixture, which is identical to testdir but its methods return pathlib.Path when appropriate instead of
py.path.local
.This is part of the movement to use pathlib.Path objects internally, in order to remove the dependency to
py
in the future.Internally, the old Testdir <_pytest.pytester.Testdir> is now a thin wrapper around Pytester <_pytest.pytester.Pytester>, preserving the old interface.
#7695: A new hook was added, pytest_markeval_namespace which should return a dictionary.
This dictionary will be used to augment the "global" variables available to evaluate skipif/xfail/xpass markers.
Pseudo example
conftest.py
:test_func.py
:#8006: It is now possible to construct a ~pytest.MonkeyPatch object directly as
pytest.MonkeyPatch()
,in cases when the monkeypatch fixture cannot be used. Previously some users imported it
from the private _pytest.monkeypatch.MonkeyPatch namespace.
Additionally, MonkeyPatch.context <pytest.MonkeyPatch.context> is now a classmethod,
and can be used as
with MonkeyPatch.context() as mp: ...
. This is the recommended way to useMonkeyPatch
directly, since unlike themonkeypatch
fixture, an instance created directlyis not
undo()
-ed automatically.Improvements
#1265: Added an
__str__
implementation to the ~pytest.pytester.LineMatcher class which is returned frompytester.run_pytest().stdout
and similar. It returns the entire output, like the existingstr()
method.#2044: Verbose mode now shows the reason that a test was skipped in the test's terminal line after the "SKIPPED", "XFAIL" or "XPASS".
#7469 The types of builtin pytest fixtures are now exported so they may be used in type annotations of test functions.
The newly-exported types are:
pytest.FixtureRequest
for the request fixture.pytest.Cache
for the cache fixture.pytest.CaptureFixture[str]
for the capfd and capsys fixtures.pytest.CaptureFixture[bytes]
for the capfdbinary and capsysbinary fixtures.pytest.LogCaptureFixture
for the caplog fixture.pytest.Pytester
for the pytester fixture.pytest.Testdir
for the testdir fixture.pytest.TempdirFactory
for the tmpdir_factory fixture.pytest.TempPathFactory
for the tmp_path_factory fixture.pytest.MonkeyPatch
for the monkeypatch fixture.pytest.WarningsRecorder
for the recwarn fixture.Constructing them is not supported (except for MonkeyPatch); they are only meant for use in type annotations.
Doing so will emit a deprecation warning, and may become a hard-error in pytest 7.0.
Subclassing them is also not supported. This is not currently enforced at runtime, but is detected by type-checkers such as mypy.
#7527: When a comparison between namedtuple <collections.namedtuple> instances of the same type fails, pytest now shows the differing field names (possibly nested) instead of their indexes.
#7615: Node.warn <_pytest.nodes.Node.warn> now permits any subclass of Warning, not just PytestWarning <pytest.PytestWarning>.
#7701: Improved reporting when using
--collected-only
. It will now show the number of collected tests in the summary stats.#7710: Use strict equality comparison for non-numeric types in pytest.approx instead of
raising TypeError.
This was the undocumented behavior before 3.7, but is now officially a supported feature.
#7938: New
--sw-skip
argument which is a shorthand for--stepwise-skip
.#8023: Added
'node_modules'
to default value for norecursedirs.#8032: doClassCleanups <unittest.TestCase.doClassCleanups> (introduced in unittest in Python and 3.8) is now called appropriately.
Bug Fixes
--lf
even though they contain tests that failed. Regressed in pytest 5.4.0.pytest --doctest-modules path/to/an/__init__.py
.Improved Documentation
final class
in the API reference._pytest.config.argparsing.Parser.addini()
accepts explicitNone
and"string"
.Trivial/Internal Changes
attrs
dependency requirement is now >=19.2.0 instead of >=17.4.0.(These files are internal and only interpreted by pytest itself.)
v6.1.2
Compare Source
pytest 6.1.2 (2020-10-28)
Bug Fixes
--lf
even though they contain tests that failed. Regressed in pytest 5.4.0.Improved Documentation
pytest._fillfuncargs()
.v6.1.1
Compare Source
pytest 6.1.1 (2020-10-03)
Bug Fixes
v6.1.0
Compare Source
pytest 6.1.0 (2020-09-26)
Breaking Changes
#5585: As per our policy, the following features which have been deprecated in the 5.X series are now
removed:
funcargnames
read-only property ofFixtureRequest
,Metafunc
, andFunction
classes. Usefixturenames
attribute.@pytest.fixture
no longer supports positional arguments, pass all arguments by keyword instead.Node
subclasses now raise an error, usefrom_parent
instead.junit_family
has changed toxunit2
. If you require the old format, addjunit_family=xunit1
to your configuration file.TerminalReporter
no longer has awriter
attribute. Plugin authors may use the public functions of theTerminalReporter
instead of accessing theTerminalWriter
object directly.--result-log
option has been removed. Users are recommended to use the pytest-reportlog plugin instead.For more information consult
Deprecations and Removals in the docs.
Deprecations
#6981: The
pytest.collect
module is deprecated: all its names can be imported frompytest
directly.#7097: The
pytest._fillfuncargs
function is deprecated. This function was keptfor backward compatibility with an older plugin.
It's functionality is not meant to be used directly, but if you must replace
it, use function._request._fillfixtures() instead, though note this is not
a public API and may break in the future.
#7210: The special
-k '-expr'
syntax to-k
is deprecated. Use-k 'not expr'
instead.
The special
-k 'expr:'
syntax to-k
is deprecated. Please open an issueif you use this and want a replacement.
#7255: The pytest_warning_captured <_pytest.hookspec.pytest_warning_captured> hook is deprecated in favor
of pytest_warning_recorded <_pytest.hookspec.pytest_warning_recorded>, and will be removed in a future version.
#7648: The
gethookproxy()
andisinitpath()
methods ofFSCollector
andPackage
are deprecated;use
self.session.gethookproxy()
andself.session.isinitpath()
instead.This should work on all pytest versions.
Features
--durations-min
command-line flag controls the minimal duration for inclusion in the slowest list of tests shown by--durations
. Previously this was hard-coded to0.005s
.Improvements
#6681: Internal pytest warnings issued during the early stages of initialization are now properly handled and can filtered through filterwarnings or
--pythonwarnings/-W
.This also fixes a number of long standing issues: #2891, #7620, #7426.
#7572: When a plugin listed in
required_plugins
is missing or an unknown config key is used with--strict-config
, a simple error message is now shown instead of a stacktrace.#7685: Added two new attributes rootpath <_pytest.config.Config.rootpath> and inipath <_pytest.config.Config.inipath> to Config <_pytest.config.Config>.
These attributes are pathlib.Path versions of the existing rootdir <_pytest.config.Config.rootdir> and inifile <_pytest.config.Config.inifile> attributes,
and should be preferred over them when possible.
#7780: Public classes which are not designed to be inherited from are now marked @final.
Code which inherits from these classes will trigger a type-checking (e.g. mypy) error, but will still work in runtime.
Currently the
final
designation does not appear in the API Reference but hopefully will in the future.Bug Fixes
#1953: Fixed error when overwriting a parametrized fixture, while also reusing the super fixture value.
conftest.py
test_foo.py
IndexError: list index out of range
whencollecting a module which starts with a decorated function, the decorator
raises, and assertion rewriting is enabled.
\projects\tests\test.py
instead ofc:\projects\tests\pytest.py
).pytest-xdist
.exec
.Improved Documentation
Trivial/Internal Changes
junitxml
plugin has rewritten to usexml.etree.ElementTree
.The order of attributes in XML elements might differ. Some unneeded escaping is
no longer performed.
more-itertools
package has been removed.but should behave like one in all respects. This was done for technical reasons.
attributes of python objects (modules, classes and instances). To speed up this
process, pytest now ignores builtin attributes (like
__class__
,__delattr__
and__new__
) without consulting the python_classes andpython_functions configuration options and without passing them to plugins
using the pytest_pycollect_makeitem <_pytest.hookspec.pytest_pycollect_makeitem> hook.
v6.0.2
Compare Source
pytest 6.0.2 (2020-09-04)
Bug Fixes
--log-cli
potentially causing unrelatedprint
output to be swallowed.caplog.set_level
is called more than once.Regressed in pytest 6.0.0.
--tb=line
for example).v6.0.1
Compare Source
pytest 6.0.1 (2020-07-30)
Bug Fixes
help
value toParser.add_option
is now accepted instead of crashing when runningpytest --help
.Passing
None
raises a more informativeTypeError
.not-callable
lint onpytest.mark.parametrize()
and the other builtin marks:skip
,skipif
,xfail
,usefixtures
,filterwarnings
.TestReport.longreprtext
(such aspytest-html
) whenTestReport.longrepr
is not a string.caplog.set_level()
.v6.0.0
Compare Source
pytest 6.0.0 (2020-07-28)
(Please see the full set of changes for this release also in the 6.0.0rc1 notes below)
Breaking Changes
#5584: PytestDeprecationWarning are now errors by default.
Following our plan to remove deprecated features with as little disruption as
possible, all warnings of type
PytestDeprecationWarning
now generate errorsinstead of warning messages.
The affected features will be effectively removed in pytest 6.1, so please consult the
Deprecations and Removals
section in the docs for directions on how to update existing code.
In the pytest
6.0.X
series, it is possible to change the errors back into warnings as astopgap measure by adding this to your
pytest.ini
file:But this will stop working when pytest
6.1
is released.If you have concerns about the removal of a specific feature, please add a
comment to #5584.
#7472: The
exec_()
andis_true()
methods of_pytest._code.Frame
have been removed.Features
Improvements
--log-file
CLI option andlog_file
ini marker now create subdirectories if needed.match
equals the obtained string but is not a regex match. In this case it is suggested to escape the regex.Bug Fixes
@pytest.mark.skip
when--runxfail
is used.stale temporary directories is not accessible.
capfd
.TracebackEntry.__str__
which was changed by accident.Improved Documentation
usefixtures
mark can apply fixtures to test.-q
option used in getting started guide.Trivial/Internal Changes
package
is no longer considered experimental.pytest 6.0.0rc1 (2020-07-08)
Breaking Changes
#1316:
TestReport.longrepr
is now always an instance ofReprExceptionInfo
. Previously it was astr
when a test failed withpytest.fail(..., pytrace=False)
.#5965: symlinks are no longer resolved during collection and matching conftest.py files with test file paths.
Resolving symlinks for the current directory and during collection was introduced as a bugfix in 3.9.0, but it actually is a new feature which had unfortunate consequences in Windows and surprising results in other platforms.
The team decided to step back on resolving symlinks at all, planning to review this in the future with a more solid solution (see discussion in
#6523 for details).
This might break test suites which made use of this feature; the fix is to create a symlink
for the entire test tree, and not only to partial files/tress as it was possible previously.
#6505:
Testdir.run().parseoutcomes()
now always returns the parsed nouns in plural form.Originally
parseoutcomes()
would always returns the nouns in plural form, but a changemeant to improve the terminal summary by using singular form single items (
1 warning
or1 error
)caused an unintended regression by changing the keys returned by
parseoutcomes()
.Now the API guarantees to always return the plural form, so calls like this:
Need to be changed to:
#6903: The
os.dup()
function is now assumed to exist. We are not aware of anysupported Python 3 implementations which do not provide it.
#7040:
-k
no longer matches against the names of the directories outside the test session root.Also,
pytest.Package.name
is now just the name of the directory containing the package's__init__.py
file, instead of the full path. This is consistent with how the other nodesare named, and also one of the reasons why
-k
would match against any directory containingthe test suite.
#7122: Expressions given to the
-m
and-k
options are no longer evaluated using Python's eval.The format supports
or
,and
,not
, parenthesis and general identifiers to match against.Python constants, keywords or other operators are no longer evaluated differently.
#7135: Pytest now uses its own
TerminalWriter
class instead of using the one from thepy
library.Plugins generally access this class through
TerminalReporter.writer
,TerminalReporter.write()
(and similar methods), or
_pytest.config.create_terminal_writer()
.The following breaking changes were made:
write()
method and others) no longer flush implicitly; the flushing behaviorof the underlying file is respected. To flush explicitly (for example, if you
want output to be shown before an end-of-line is printed), use
write(flush=True)
orterminal_writer.flush()
.bytes
was removed.reline
method andchars_on_current_line
property were removed.stringio
andencoding
arguments was removed.#7224: The item.catch_log_handler and item.catch_log_handlers attributes, set by the
logging plugin and never meant to be public , are no longer available.
The deprecated
--no-print-logs
option is removed. Use--show-capture
instead.#7226: Removed the unused
args
parameter frompytest.Function.__init__
.#7418: Removed the pytest_doctest_prepare_content hook specification. This hook
hasn't been triggered by pytest for at least 10 years.
#7438: Some changes were made to the internal
_pytest._code.source
, listed herefor the benefit of plugin authors who may be using it:
deindent
argument toSource()
has been removed, now it is always true.Source()
has been removed.Source
with anstr
has been removed.Source.isparseable()
andSource.putaround()
have been removed.Source.compile()
and function_pytest._code.compile()
havebeen removed; use plain
compile()
instead._pytest._code.source.getsource()
has been removed; useSource()
directly instead.Deprecations
#7210: The special
-k '-expr'
syntax to-k
is deprecated. Use-k 'not expr'
instead.
The special
-k 'expr:'
syntax to-k
is deprecated. Please open an issueif you use this and want a replacement.
#4049:
pytest_warning_captured
is deprecated in favor of thepytest_warning_recorded
hook.Features
#1556: pytest now supports
pyproject.toml
files for configuration.The configuration options is similar to the one available in other formats, but must be defined
in a
[tool.pytest.ini_options]
table to be picked up by pytest:pyproject.toml
#3342: pytest now includes inline type annotations and exposes them to user programs.
Most of the user-facing API is covered, as well as internal code.
If you are running a type checker such as mypy on your tests, you may start
noticing type errors indicating incorrect usage. If you run into an error that
you believe to be incorrect, please let us know in an issue.
The types were developed against mypy version 0.780. Versions before 0.750
are known not to work. We recommend using the latest version. Other type
checkers may work as well, but they are not officially verified to work by
pytest yet.
#4049: Introduced a new hook named pytest_warning_recorded to convey information about warnings captured by the internal pytest warnings plugin.
This hook is meant to replace pytest_warning_captured, which is deprecated and will be removed in a future release.
#6471: New command-line flags:
#6856: A warning is now shown when an unknown key is read from a config INI file.
The --strict-config flag has been added to treat these warnings as errors.
#6906: Added --code-highlight command line option to enable/disable code highlighting in terminal output.
#7245: New
--import-mode=importlib
option that uses importlib to import test modules.Traditionally pytest used
__import__
while changingsys.path
to import test modules (whichalso changes
sys.modules
as a side-effect), which works but has a number of drawbacks, like requiring test modulesthat don't live in packages to have unique names (as they need to reside under a unique name in
sys.modules
).--import-mode=importlib
uses more fine grained import mechanisms fromimportlib
which don'trequire pytest to change
sys.path
orsys.modules
at all, eliminating much of the drawbacksof the previous mode.
We intend to make
--import-mode=importlib
the default in future versions, so users are encouragedto try the new mode and provide feedback (both positive or negative) in issue #7245.
You can read more about this option in the documentation.
#7305: New
required_plugins
configuration option allows the user to specify a list of plugins, including version information, that are required for pytest to run. An error is raised if any required plugins are not found when running pytest.Improvements
#4375: The
pytest
command now suppresses theBrokenPipeError
error message thatis printed to stderr when the output of
pytest
is piped and and the pipe isclosed by the piped-to program (common examples are
less
andhead
).#4391: Improved precision of test durations measurement.
CallInfo
items now have a new<CallInfo>.duration
attribute, created usingtime.perf_counter()
. This attribute is used to fill the<TestReport>.duration
attribute, which is more accurate than the previous<CallInfo>.stop - <CallInfo>.start
(as these are based ontime.time()
).#4675: Rich comparison for dataclasses and attrs-classes is now recursive.
#6285: Exposed the pytest.FixtureLookupError exception which is raised by request.getfixturevalue()
(where request is a FixtureRequest fixture) when a fixture with the given name cannot be returned.
#6433: If an error is encountered while formatting the message in a logging call, for
example
logging.warning("oh no!: %s: %s", "first")
(a second argument ismissing), pytest now propagates the error, likely causing the test to fail.
Previously, such a mistake would cause an error to be printed to stderr, which
is not displayed by default for passing tests. This change makes the mistake
visible during testing.
You may supress this behavior temporarily or permanently by setting
logging.raiseExceptions = False
.#6817: Explicit new-lines in help texts of command-line options are preserved, allowing plugins better control
of the help displayed to users.
#6940: When using the
--duration
option, the terminal message output is now more precise about the number and duration of hidden items.#6991: Collected files are displayed after any reports from hooks, e.g. the status from
--lf
.#7091: When
fd
capturing is used, through--capture=fd
or thecapfd
andcapfdbinary
fixtures, and the file descriptor (0, 1, 2) cannot beduplicated, FD capturing is still performed. Previously, direct writes to the
file descriptors would fail or be lost in this case.
#7119: Exit with an error if the
--basetemp
argument is empty, is the current working directory or is one of the parent directories.This is done to protect against accidental data loss, as any directory passed to this argument is cleared.
#7128: pytest --version now displays just the pytest version, while pytest --version --version displays more verbose information including plugins. This is more consistent with how other tools show --version.
#7133: caplog.set_level() <_pytest.logging.LogCaptureFixture.set_level> will now override any log_level set via the CLI or configuration file.
#7159: caplog.set_level() <_pytest.logging.LogCaptureFixture.set_level> and caplog.at_level() <_pytest.logging.LogCaptureFixture.at_level> no longer affect
the level of logs that are shown in the Captured log report report section.
#7348: Improve recursive diff report for comparison asserts on dataclasses / attrs.
#7385:
--junitxml
now includes the exception cause in themessage
XML attribute for failures during setup and teardown.Previously:
Now:
Bug Fixes
#1120: Fix issue where directories from tmpdir are not removed properly when multiple instances of pytest are running in parallel.
#4583: Prevent crashing and provide a user-friendly error when a marker expression (-m) invoking of eval raises any exception.
#4677: The path shown in the summary report for SKIPPED tests is now always relative. Previously it was sometimes absolute.
#5456: Fix a possible race condition when trying to remove lock files used to control access to folders
created by tmp_path and tmpdir.
#6240: Fixes an issue where logging during collection step caused duplication of log
messages to stderr.
#6428: Paths appearing in error messages are now correct in case the current working directory has
changed since the start of the session.
#6755: Support deleting paths longer than 260 characters on windows created inside tmpdir.
#6871: Fix crash with captured output when using capsysbinary.
#6909: Revert the change introduced by #6330, which required all arguments to
@pytest.mark.parametrize
to be explicitly defined in the function signature.The intention of the original change was to remove what was expected to be an unintended/surprising behavior, but it turns out many people relied on it, so the restriction has been reverted.
#6910: Fix crash when plugins return an unknown stats while using the
--reportlog
option.#6924: Ensure a
unittest.IsolatedAsyncioTestCase
is actually awaited.#6925: Fix TerminalRepr instances to be hashable again.
#6947: Fix regression where functions registered with unittest.TestCase.addCleanup were not being called on test failures.
#6951: Allow users to still set the deprecated
TerminalReporter.writer
attribute.#6956: Prevent pytest from printing ConftestImportFailure traceback to stdout.
#6991: Fix regressions with --lf filtering too much since pytest 5.4.
#6992: Revert "tmpdir: clean up indirection via config for factories" #6767 as it breaks pytest-xdist.
#7061: When a yielding fixture fails to yield a value, report a test setup error instead of crashing.
#7076: The path of file skipped by
@pytest.mark.skip
in the SKIPPED report is now relative to invocation directory. Previously it was relative to root directory.#7110: Fixed regression:
asyncbase.TestCase
tests are executed correctly again.#7126:
--setup-show
now doesn't raise an error when a bytes value is used as aparametrize
parameter when Python is called with the
-bb
flag.#7143: Fix pytest.File.from_parent so it forwards extra keyword arguments to the constructor.
#7145: Classes with broken
__getattribute__
methods are displayed correctly during failures.#7150: Prevent hiding the underlying exception when
ConfTestImportFailure
is raised.#7180: Fix
_is_setup_py
for files encoded differently than locale.#7215: Fix regression where running with
--pdb
would call unittest.TestCase.tearDown for skipped tests.#7253: When using
pytest.fixture
on a function directly, as inpytest.fixture(func)
,if the
autouse
orparams
arguments are also passed, the function is no longerignored, but is marked as a fixture.
#7360: Fix possibly incorrect evaluation of string expressions passed to
pytest.mark.skipif
andpytest.mark.xfail
,in rare circumstances where the exact same string is used but refers to different global values.
#7383: Fixed exception causes all over the codebase, i.e. use raise new_exception from old_exception when wrapping an exception.
Improved Documentation
--strict
and--strict-markers
and the preference for the latter one.Trivial/Internal Changes
originalname
attribute of_pytest.python.Function
now defaults toname
if notprovided explicitly, and is always set.
wcwidth
package has been removed.py.iniconfig
with iniconfig.src/_pytest/config/__init__.py
now uses thewarnings
module to report warnings instead ofsys.stderr.write
.pytest-xdist
.py
>=1.8.2 is now required.Renovate configuration
📅 Schedule: "after 9am and before 3pm" (UTC).
🚦 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.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by WhiteSource Renovate. View repository job log here.