splunk / addonfactory-ucc-library

UCC Helper Library used by Splunk Add-ons
Apache License 2.0
15 stars 10 forks source link

chore(deps): update all dependencies #324

Open renovate[bot] opened 6 days ago

renovate[bot] commented 6 days ago

This PR contains the following updates:

Package Change Age Adoption Passing Confidence Type Update
pytest (changelog) 7.4.4 -> 8.3.3 age adoption passing confidence dev major
solnlib 5.4.0 -> 6.0.1 age adoption passing confidence dependencies major
splunk-add-on-ucc-framework 5.52.0 -> 5.54.0 age adoption passing confidence dev minor
splunk/addonfactory-github-workflows v1.6 -> v1.7 age adoption passing confidence action minor
ubuntu 22.04 -> 24.04 age adoption passing confidence github-runner major

Release Notes

pytest-dev/pytest (pytest) ### [`v8.3.3`](https://redirect.github.com/pytest-dev/pytest/releases/tag/8.3.3) [Compare Source](https://redirect.github.com/pytest-dev/pytest/compare/8.3.2...8.3.3) # pytest 8.3.3 (2024-09-09) ## Bug fixes - [#​12446](https://redirect.github.com/pytest-dev/pytest/issues/12446): Avoid calling `@property` (and other instance descriptors) during fixture discovery -- by `asottile`{.interpreted-text role="user"} - [#​12659](https://redirect.github.com/pytest-dev/pytest/issues/12659): Fixed the issue of not displaying assertion failure differences when using the parameter `--import-mode=importlib` in pytest>=8.1. - [#​12667](https://redirect.github.com/pytest-dev/pytest/issues/12667): Fixed a regression where type change in \[ExceptionInfo.errisinstance]{.title-ref} caused \[mypy]{.title-ref} to fail. - [#​12744](https://redirect.github.com/pytest-dev/pytest/issues/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](https://redirect.github.com/pytest-dev/pytest/issues/12745): Fixed an issue with backslashes being incorrectly converted in nodeid paths on Windows, ensuring consistent path handling across environments. - [#​6682](https://redirect.github.com/pytest-dev/pytest/issues/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](https://redirect.github.com/pytest-dev/pytest/issues/9422): Fix bug where disabling the terminal plugin via `-p no:terminal` would cause crashes related to missing the `verbose` option. \-- by `GTowers1`{.interpreted-text role="user"} ## Improved documentation - [#​12663](https://redirect.github.com/pytest-dev/pytest/issues/12663): Clarify that the \[pytest_deselected]{.title-ref} hook should be called from \[pytest_collection_modifyitems]{.title-ref} hook implementations when items are deselected. - [#​12678](https://redirect.github.com/pytest-dev/pytest/issues/12678): Remove erroneous quotes from \[tmp_path_retention_policy]{.title-ref} example in docs. ## Miscellaneous internal changes - [#​12769](https://redirect.github.com/pytest-dev/pytest/issues/12769): Fix typos discovered by codespell and add codespell to pre-commit hooks. ### [`v8.3.2`](https://redirect.github.com/pytest-dev/pytest/releases/tag/8.3.2) [Compare Source](https://redirect.github.com/pytest-dev/pytest/compare/8.3.1...8.3.2) # pytest 8.3.2 (2024-07-24) ## Bug fixes - [#​12652](https://redirect.github.com/pytest-dev/pytest/issues/12652): Resolve regression \[conda]{.title-ref} environments where no longer being automatically detected. \-- by `RonnyPfannschmidt`{.interpreted-text role="user"} ### [`v8.3.1`](https://redirect.github.com/pytest-dev/pytest/releases/tag/8.3.1) [Compare Source](https://redirect.github.com/pytest-dev/pytest/compare/8.3.0...8.3.1) # pytest 8.3.1 (2024-07-20) The 8.3.0 release failed to include the change notes and docs for the release. This patch release remedies this. There are no other changes. ### [`v8.3.0`](https://redirect.github.com/pytest-dev/pytest/releases/tag/8.3.0) [Compare Source](https://redirect.github.com/pytest-dev/pytest/compare/8.2.2...8.3.0) ### pytest 8.3.0 (2024-07-20) #### New features - [#​12231](https://redirect.github.com/pytest-dev/pytest/issues/12231): Added \[--xfail-tb]{.title-ref} flag, which turns on traceback output for XFAIL results. - If the \[--xfail-tb]{.title-ref} flag is not given, tracebacks for XFAIL results are NOT shown. - The style of traceback for XFAIL is set with \[--tb]{.title-ref}, and can be \[auto|long|short|line|native|no]{.title-ref}. - Note: Even if you have \[--xfail-tb]{.title-ref} set, you won't see them if \[--tb=no]{.title-ref}. Some history: With pytest 8.0, \[-rx]{.title-ref} or \[-ra]{.title-ref} would not only turn on summary reports for xfail, but also report the tracebacks for xfail results. This caused issues with some projects that utilize xfail, but don't want to see all of the xfail tracebacks. This change detaches xfail tracebacks from \[-rx]{.title-ref}, and now we turn on xfail tracebacks with \[--xfail-tb]{.title-ref}. With this, the default \[-rx]{.title-ref}/ \[-ra]{.title-ref} behavior is identical to pre-8.0 with respect to xfail tracebacks. While this is a behavior change, it brings default behavior back to pre-8.0.0 behavior, which ultimately was considered the better course of action. - [#​12281](https://redirect.github.com/pytest-dev/pytest/issues/12281): Added support for keyword matching in marker expressions. Now tests can be selected by marker keyword arguments. Supported values are `int`{.interpreted-text role="class"}, (unescaped) `str`{.interpreted-text role="class"}, `bool`{.interpreted-text role="class"} & `None`{.interpreted-text role="data"}. See `marker examples `{.interpreted-text role="ref"} for more information. \-- by `lovetheguitar`{.interpreted-text role="user"} - [#​12567](https://redirect.github.com/pytest-dev/pytest/issues/12567): Added `--no-fold-skipped` command line option. If this option is set, then skipped tests in short summary are no longer grouped by reason but all tests are printed individually with their nodeid in the same way as other statuses. \-- by `pbrezina`{.interpreted-text role="user"} #### Improvements in existing functionality - [#​12469](https://redirect.github.com/pytest-dev/pytest/issues/12469): The console output now uses the "third-party plugins" terminology, replacing the previously established but confusing and outdated reference to `setuptools `{.interpreted-text role="std:doc"} \-- by `webknjaz`{.interpreted-text role="user"}. - [#​12544](https://redirect.github.com/pytest-dev/pytest/issues/12544), [#​12545](https://redirect.github.com/pytest-dev/pytest/issues/12545): Python virtual environment detection was improved by checking for a `pyvenv.cfg`{.interpreted-text role="file"} file, ensuring reliable detection on various platforms -- by `zachsnickers`{.interpreted-text role="user"}. - [#​2871](https://redirect.github.com/pytest-dev/pytest/issues/2871): Do not truncate arguments to functions in output when running with \[-vvv]{.title-ref}. - [#​389](https://redirect.github.com/pytest-dev/pytest/issues/389): The readability of assertion introspection of bound methods has been enhanced \-- by `farbodahm`{.interpreted-text role="user"}, `webknjaz`{.interpreted-text role="user"}, `obestwalter`{.interpreted-text role="user"}, `flub`{.interpreted-text role="user"} and `glyphack`{.interpreted-text role="user"}. Earlier, it was like: ```console =================================== FAILURES =================================== _____________________________________ test _____________________________________ def test(): > assert Help().fun() == 2 E assert 1 == 2 E + where 1 = >() E + where > = .fun E + where = Help() example.py:7: AssertionError =========================== 1 failed in 0.03 seconds =========================== ``` And now it's like: ```console =================================== FAILURES =================================== _____________________________________ test _____________________________________ def test(): > assert Help().fun() == 2 E assert 1 == 2 E + where 1 = fun() E + where fun = .fun E + where = Help() test_local.py:13: AssertionError =========================== 1 failed in 0.03 seconds =========================== ``` - [#​7662](https://redirect.github.com/pytest-dev/pytest/issues/7662): Added timezone information to the testsuite timestamp in the JUnit XML report. #### Bug fixes - [#​11706](https://redirect.github.com/pytest-dev/pytest/issues/11706): Fixed reporting of teardown errors in higher-scoped fixtures when using \[--maxfail]{.title-ref} or \[--stepwise]{.title-ref}. Originally added in pytest 8.0.0, but reverted in 8.0.2 due to a regression in pytest-xdist. This regression was fixed in pytest-xdist 3.6.1. - [#​11797](https://redirect.github.com/pytest-dev/pytest/issues/11797): `pytest.approx`{.interpreted-text role="func"} now correctly handles `Sequence `{.interpreted-text role="class"}-like objects. - [#​12204](https://redirect.github.com/pytest-dev/pytest/issues/12204), [#​12264](https://redirect.github.com/pytest-dev/pytest/issues/12264): Fixed a regression in pytest 8.0 where tracebacks get longer and longer when multiple tests fail due to a shared higher-scope fixture which raised -- by `bluetech`{.interpreted-text role="user"}. Also fixed a similar regression in pytest 5.4 for collectors which raise during setup. The fix necessitated internal changes which may affect some plugins: - `FixtureDef.cached_result[2]` is now a tuple `(exc, tb)` instead of `exc`. - `SetupState.stack` failures are now a tuple `(exc, tb)` instead of `exc`. - [#​12275](https://redirect.github.com/pytest-dev/pytest/issues/12275): Fixed collection error upon encountering an `abstract `{.interpreted-text role="mod"} class, including abstract \[unittest.TestCase]{.title-ref} subclasses. - [#​12328](https://redirect.github.com/pytest-dev/pytest/issues/12328): Fixed a regression in pytest 8.0.0 where package-scoped parameterized items were not correctly reordered to minimize setups/teardowns in some cases. - [#​12424](https://redirect.github.com/pytest-dev/pytest/issues/12424): Fixed crash with \[assert testcase is not None]{.title-ref} assertion failure when re-running unittest tests using plugins like pytest-rerunfailures. Regressed in 8.2.2. - [#​12472](https://redirect.github.com/pytest-dev/pytest/issues/12472): Fixed a crash when returning category `"error"` or `"failed"` with a custom test status from `pytest_report_teststatus`{.interpreted-text role="hook"} hook -- `pbrezina`{.interpreted-text role="user"}. - [#​12505](https://redirect.github.com/pytest-dev/pytest/issues/12505): Improved handling of invalid regex patterns in `pytest.raises(match=r'...') `{.interpreted-text role="func"} by providing a clear error message. - [#​12580](https://redirect.github.com/pytest-dev/pytest/issues/12580): Fixed a crash when using the cache class on Windows and the cache directory was created concurrently. - [#​6962](https://redirect.github.com/pytest-dev/pytest/issues/6962): Parametrization parameters are now compared using \[==]{.title-ref} instead of \[is]{.title-ref} (\[is]{.title-ref} is still used as a fallback if the parameter does not support \[==]{.title-ref}). This fixes use of parameters such as lists, which have a different \[id]{.title-ref} but compare equal, causing fixtures to be re-computed instead of being cached. - [#​7166](https://redirect.github.com/pytest-dev/pytest/issues/7166): Fixed progress percentages (the `[ 87%]` at the edge of the screen) sometimes not aligning correctly when running with pytest-xdist `-n`. #### Improved documentation - [#​12153](https://redirect.github.com/pytest-dev/pytest/issues/12153): Documented using `PYTEST_VERSION`{.interpreted-text role="envvar"} to detect if code is running from within a pytest run. - [#​12469](https://redirect.github.com/pytest-dev/pytest/issues/12469): The external plugin mentions in the documentation now avoid mentioning `setuptools entry-points `{.interpreted-text role="std:doc"} as the concept is much more generic nowadays. Instead, the terminology of "external", "installed", or "third-party" plugins (or packages) replaces that. \-- by `webknjaz`{.interpreted-text role="user"} - [#​12577](https://redirect.github.com/pytest-dev/pytest/issues/12577): \[CI]{.title-ref} and \[BUILD_NUMBER]{.title-ref} environment variables role is discribed in the reference doc. They now also appear when doing \[pytest -h]{.title-ref} \-- by `MarcBresson`{.interpreted-text role="user"}. #### Contributor-facing changes - [#​12467](https://redirect.github.com/pytest-dev/pytest/issues/12467): Migrated all internal type-annotations to the python3.10+ style by using the \[annotations]{.title-ref} future import. \-- by `RonnyPfannschmidt`{.interpreted-text role="user"} - [#​11771](https://redirect.github.com/pytest-dev/pytest/issues/11771), [#​12557](https://redirect.github.com/pytest-dev/pytest/issues/12557): The PyPy runtime version has been updated to 3.9 from 3.8 that introduced a flaky bug at the garbage collector which was not expected to fix there as the 3.8 is EoL. \-- by `x612skm`{.interpreted-text role="user"} - [#​12493](https://redirect.github.com/pytest-dev/pytest/issues/12493): The change log draft preview integration has been refactored to use a third party extension `sphinxcontib-towncrier`. The previous in-repo script was putting the change log preview file at `doc/en/_changelog_towncrier_draft.rst`{.interpreted-text role="file"}. Said file is no longer ignored in Git and might show up among untracked files in the development environments of the contributors. To address that, the contributors can run the following command that will clean it up: ```console $ git clean -x -i -- doc/en/_changelog_towncrier_draft.rst ``` \-- by `webknjaz`{.interpreted-text role="user"} - [#​12498](https://redirect.github.com/pytest-dev/pytest/issues/12498): All the undocumented `tox` environments now have descriptions. They can be listed in one's development environment by invoking `tox -av` in a terminal. \-- by `webknjaz`{.interpreted-text role="user"} - [#​12501](https://redirect.github.com/pytest-dev/pytest/issues/12501): The changelog configuration has been updated to introduce more accurate audience-tailored categories. Previously, there was a `trivial` change log fragment type with an unclear and broad meaning. It was removed and we now have `contrib`, `misc` and `packaging` in place of it. The new change note types target the readers who are downstream packagers and project contributors. Additionally, the miscellaneous section is kept for unspecified updates that do not fit anywhere else. \-- by `webknjaz`{.interpreted-text role="user"} - [#​12502](https://redirect.github.com/pytest-dev/pytest/issues/12502): The UX of the GitHub automation making pull requests to update the plugin list has been updated. Previously, the maintainers had to close the automatically created pull requests and re-open them to trigger the CI runs. From now on, they only need to click the \[Ready for review]{.title-ref} button instead. \-- by `webknjaz`{.interpreted-text role="user"} - [#​12522](https://redirect.github.com/pytest-dev/pytest/issues/12522): The `:pull:` RST role has been replaced with a shorter `:pr:` due to starting to use the implementation from the third-party `sphinx-issues`{.interpreted-text role="pypi"} Sphinx extension \-- by `webknjaz`{.interpreted-text role="user"}. - [#​12531](https://redirect.github.com/pytest-dev/pytest/issues/12531): The coverage reporting configuration has been updated to exclude pytest's own tests marked as expected to fail from the coverage report. This has an effect of reducing the influence of flaky tests on the resulting number. \-- by `webknjaz`{.interpreted-text role="user"} - [#​12533](https://redirect.github.com/pytest-dev/pytest/issues/12533): The `extlinks` Sphinx extension is no longer enabled. The `:bpo:` role it used to declare has been removed with that. BPO itself has migrated to GitHub some years ago and it is possible to link the respective issues by using their GitHub issue numbers and the `:issue:` role that the `sphinx-issues` extension implements. \-- by `webknjaz`{.interpreted-text role="user"} - [#​12562](https://redirect.github.com/pytest-dev/pytest/issues/12562): Possible typos in using the `:user:` RST role is now being linted through the pre-commit tool integration -- by `webknjaz`{.interpreted-text role="user"}. ### [`v8.2.2`](https://redirect.github.com/pytest-dev/pytest/releases/tag/8.2.2) [Compare Source](https://redirect.github.com/pytest-dev/pytest/compare/8.2.1...8.2.2) # pytest 8.2.2 (2024-06-04) ## Bug Fixes - [#​12355](https://redirect.github.com/pytest-dev/pytest/issues/12355): Fix possible catastrophic performance slowdown on a certain parametrization pattern involving many higher-scoped parameters. - [#​12367](https://redirect.github.com/pytest-dev/pytest/issues/12367): Fix a regression in pytest 8.2.0 where unittest class instances (a fresh one is created for each test) were not released promptly on test teardown but only on session teardown. - [#​12381](https://redirect.github.com/pytest-dev/pytest/issues/12381): Fix possible "Directory not empty" crashes arising from concurent cache dir (`.pytest_cache`) creation. Regressed in pytest 8.2.0. ## Improved Documentation - [#​12290](https://redirect.github.com/pytest-dev/pytest/issues/12290): Updated Sphinx theme to use Furo instead of Flask, enabling Dark mode theme. - [#​12356](https://redirect.github.com/pytest-dev/pytest/issues/12356): Added a subsection to the documentation for debugging flaky tests to mention lack of thread safety in pytest as a possible source of flakyness. - [#​12363](https://redirect.github.com/pytest-dev/pytest/issues/12363): The documentation webpages now links to a canonical version to reduce outdated documentation in search engine results. ### [`v8.2.1`](https://redirect.github.com/pytest-dev/pytest/releases/tag/8.2.1) [Compare Source](https://redirect.github.com/pytest-dev/pytest/compare/8.2.0...8.2.1) # pytest 8.2.1 (2024-05-19) ## Improvements - [#​12334](https://redirect.github.com/pytest-dev/pytest/issues/12334): Support for Python 3.13 (beta1 at the time of writing). ## Bug Fixes - [#​12120](https://redirect.github.com/pytest-dev/pytest/issues/12120): Fix \[PermissionError]{.title-ref} crashes arising from directories which are not selected on the command-line. - [#​12191](https://redirect.github.com/pytest-dev/pytest/issues/12191): Keyboard interrupts and system exits are now properly handled during the test collection. - [#​12300](https://redirect.github.com/pytest-dev/pytest/issues/12300): Fixed handling of 'Function not implemented' error under squashfuse_ll, which is a different way to say that the mountpoint is read-only. - [#​12308](https://redirect.github.com/pytest-dev/pytest/issues/12308): Fix a regression in pytest 8.2.0 where the permissions of automatically-created `.pytest_cache` directories became `rwx------` instead of the expected `rwxr-xr-x`. ## Trivial/Internal Changes - [#​12333](https://redirect.github.com/pytest-dev/pytest/issues/12333): pytest releases are now attested using the recent [Artifact Attestation](https://github.blog/2024-05-02-introducing-artifact-attestations-now-in-public-beta/) support from GitHub, allowing users to verify the provenance of pytest's sdist and wheel artifacts. ### [`v8.2.0`](https://redirect.github.com/pytest-dev/pytest/releases/tag/8.2.0) [Compare Source](https://redirect.github.com/pytest-dev/pytest/compare/8.1.2...8.2.0) # pytest 8.2.0 (2024-04-27) ## Deprecations - [#​12069](https://redirect.github.com/pytest-dev/pytest/issues/12069): A deprecation warning is now raised when implementations of one of the following hooks request a deprecated `py.path.local` parameter instead of the `pathlib.Path` parameter which replaced it: - `pytest_ignore_collect`{.interpreted-text role="hook"} - the `path` parameter - use `collection_path` instead. - `pytest_collect_file`{.interpreted-text role="hook"} - the `path` parameter - use `file_path` instead. - `pytest_pycollect_makemodule`{.interpreted-text role="hook"} - the `path` parameter - use `module_path` instead. - `pytest_report_header`{.interpreted-text role="hook"} - the `startdir` parameter - use `start_path` instead. - `pytest_report_collectionfinish`{.interpreted-text role="hook"} - the `startdir` parameter - use `start_path` instead. The replacement parameters are available since pytest 7.0.0. The old parameters will be removed in pytest 9.0.0. See `legacy-path-hooks-deprecated`{.interpreted-text role="ref"} for more details. ## Features - [#​11871](https://redirect.github.com/pytest-dev/pytest/issues/11871): Added support for reading command line arguments from a file using the prefix character `@`, like e.g.: `pytest @​tests.txt`. The file must have one argument per line. See `Read arguments from file `{.interpreted-text role="ref"} for details. ## Improvements - [#​11523](https://redirect.github.com/pytest-dev/pytest/issues/11523): `pytest.importorskip`{.interpreted-text role="func"} will now issue a warning if the module could be found, but raised `ImportError`{.interpreted-text role="class"} instead of `ModuleNotFoundError`{.interpreted-text role="class"}. The warning can be suppressed by passing `exc_type=ImportError` to `pytest.importorskip`{.interpreted-text role="func"}. See `import-or-skip-import-error`{.interpreted-text role="ref"} for details. - [#​11728](https://redirect.github.com/pytest-dev/pytest/issues/11728): For `unittest`-based tests, exceptions during class cleanup (as raised by functions registered with `TestCase.addClassCleanup `{.interpreted-text role="meth"}) are now reported instead of silently failing. - [#​11777](https://redirect.github.com/pytest-dev/pytest/issues/11777): Text is no longer truncated in the `short test summary info` section when `-vv` is given. - [#​12112](https://redirect.github.com/pytest-dev/pytest/issues/12112): Improved namespace packages detection when `consider_namespace_packages`{.interpreted-text role="confval"} is enabled, covering more situations (like editable installs). - [#​9502](https://redirect.github.com/pytest-dev/pytest/issues/9502): Added `PYTEST_VERSION`{.interpreted-text role="envvar"} environment variable which is defined at the start of the pytest session and undefined afterwards. It contains the value of `pytest.__version__`, and among other things can be used to easily check if code is running from within a pytest run. ## Bug Fixes - [#​12065](https://redirect.github.com/pytest-dev/pytest/issues/12065): Fixed a regression in pytest 8.0.0 where test classes containing `setup_method` and tests using `@staticmethod` or `@classmethod` would crash with `AttributeError: 'NoneType' object has no attribute 'setup_method'`. Now the `request.instance `{.interpreted-text role="attr"} attribute of tests using `@staticmethod` and `@classmethod` is no longer `None`, but a fresh instance of the class, like in non-static methods. Previously it was `None`, and all fixtures of such tests would share a single `self`. - [#​12135](https://redirect.github.com/pytest-dev/pytest/issues/12135): Fixed issue where fixtures adding their finalizer multiple times to fixtures they request would cause unreliable and non-intuitive teardown ordering in some instances. - [#​12194](https://redirect.github.com/pytest-dev/pytest/issues/12194): Fixed a bug with `--importmode=importlib` and `--doctest-modules` where child modules did not appear as attributes in parent modules. - [#​1489](https://redirect.github.com/pytest-dev/pytest/issues/1489): Fixed some instances where teardown of higher-scoped fixtures was not happening in the reverse order they were initialized in. ## Trivial/Internal Changes - [#​12069](https://redirect.github.com/pytest-dev/pytest/issues/12069): `pluggy>=1.5.0` is now required. - [#​12167](https://redirect.github.com/pytest-dev/pytest/issues/12167): `cache `{.interpreted-text role="ref"}: create supporting files (`CACHEDIR.TAG`, `.gitignore`, etc.) in a temporary directory to provide atomic semantics. ### [`v8.1.2`](https://redirect.github.com/pytest-dev/pytest/releases/tag/8.1.2) [Compare Source](https://redirect.github.com/pytest-dev/pytest/compare/8.1.1...8.1.2) # pytest 8.1.2 (2024-04-26) ## Bug Fixes - [#​12114](https://redirect.github.com/pytest-dev/pytest/issues/12114): Fixed error in `pytest.approx`{.interpreted-text role="func"} when used with \[numpy]{.title-ref} arrays and comparing with other types. ### [`v8.1.1`](https://redirect.github.com/pytest-dev/pytest/releases/tag/8.1.1) [Compare Source](https://redirect.github.com/pytest-dev/pytest/compare/8.1.0...8.1.1) # pytest 8.1.1 (2024-03-08) ::: {.note} ::: {.title} Note ::: This release is not a usual bug fix release -- it contains features and improvements, being a follow up to `8.1.0`, which has been yanked from PyPI. ::: ## Features - [#​11475](https://redirect.github.com/pytest-dev/pytest/issues/11475): Added the new `consider_namespace_packages`{.interpreted-text role="confval"} configuration option, defaulting to `False`. If set to `True`, pytest will attempt to identify modules that are part of [namespace packages](https://packaging.python.org/en/latest/guides/packaging-namespace-packages) when importing modules. - [#​11653](https://redirect.github.com/pytest-dev/pytest/issues/11653): Added the new `verbosity_test_cases`{.interpreted-text role="confval"} configuration option for fine-grained control of test execution verbosity. See `Fine-grained verbosity `{.interpreted-text role="ref"} for more details. ## Improvements - [#​10865](https://redirect.github.com/pytest-dev/pytest/issues/10865): `pytest.warns`{.interpreted-text role="func"} now validates that `warnings.warn`{.interpreted-text role="func"} was called with a \[str]{.title-ref} or a \[Warning]{.title-ref}. Currently in Python it is possible to use other types, however this causes an exception when `warnings.filterwarnings`{.interpreted-text role="func"} is used to filter those warnings (see [CPython #​103577](https://redirect.github.com/python/cpython/issues/103577) for a discussion). While this can be considered a bug in CPython, we decided to put guards in pytest as the error message produced without this check in place is confusing. - [#​11311](https://redirect.github.com/pytest-dev/pytest/issues/11311): When using `--override-ini` for paths in invocations without a configuration file defined, the current working directory is used as the relative directory. Previoulsy this would raise an `AssertionError`{.interpreted-text role="class"}. - [#​11475](https://redirect.github.com/pytest-dev/pytest/issues/11475): `--import-mode=importlib `{.interpreted-text role="ref"} now tries to import modules using the standard import mechanism (but still without changing :py`sys.path`{.interpreted-text role="data"}), falling back to importing modules directly only if that fails. This means that installed packages will be imported under their canonical name if possible first, for example `app.core.models`, instead of having the module name always be derived from their path (for example `.env310.lib.site_packages.app.core.models`). - [#​11801](https://redirect.github.com/pytest-dev/pytest/issues/11801): Added the `iter_parents() <_pytest.nodes.Node.iter_parents>`{.interpreted-text role="func"} helper method on nodes. It is similar to `listchain <_pytest.nodes.Node.listchain>`{.interpreted-text role="func"}, but goes from bottom to top, and returns an iterator, not a list. - [#​11850](https://redirect.github.com/pytest-dev/pytest/issues/11850): Added support for `sys.last_exc`{.interpreted-text role="data"} for post-mortem debugging on Python>=3.12. - [#​11962](https://redirect.github.com/pytest-dev/pytest/issues/11962): In case no other suitable candidates for configuration file are found, a `pyproject.toml` (even without a `[tool.pytest.ini_options]` table) will be considered as the configuration file and define the `rootdir`. - [#​11978](https://redirect.github.com/pytest-dev/pytest/issues/11978): Add `--log-file-mode` option to the logging plugin, enabling appending to log-files. This option accepts either `"w"` or `"a"` and defaults to `"w"`. Previously, the mode was hard-coded to be `"w"` which truncates the file before logging. - [#​12047](https://redirect.github.com/pytest-dev/pytest/issues/12047): When multiple finalizers of a fixture raise an exception, now all exceptions are reported as an exception group. Previously, only the first exception was reported. ## Bug Fixes - [#​11475](https://redirect.github.com/pytest-dev/pytest/issues/11475): Fixed regression where `--importmode=importlib` would import non-test modules more than once. - [#​11904](https://redirect.github.com/pytest-dev/pytest/issues/11904): Fixed a regression in pytest 8.0.0 that would cause test collection to fail due to permission errors when using `--pyargs`. This change improves the collection tree for tests specified using `--pyargs`, see `12043`{.interpreted-text role="pull"} for a comparison with pytest 8.0 and <8. - [#​12011](https://redirect.github.com/pytest-dev/pytest/issues/12011): Fixed a regression in 8.0.1 whereby `setup_module` xunit-style fixtures are not executed when `--doctest-modules` is passed. - [#​12014](https://redirect.github.com/pytest-dev/pytest/issues/12014): Fix the `stacklevel` used when warning about marks used on fixtures. - [#​12039](https://redirect.github.com/pytest-dev/pytest/issues/12039): Fixed a regression in `8.0.2` where tests created using `tmp_path`{.interpreted-text role="fixture"} have been collected multiple times in CI under Windows. ## Improved Documentation - [#​11790](https://redirect.github.com/pytest-dev/pytest/issues/11790): Documented the retention of temporary directories created using the `tmp_path` fixture in more detail. ## Trivial/Internal Changes - [#​11785](https://redirect.github.com/pytest-dev/pytest/issues/11785): Some changes were made to private functions which may affect plugins which access them: - `FixtureManager._getautousenames()` now takes a `Node` itself instead of the nodeid. - `FixtureManager.getfixturedefs()` now takes the `Node` itself instead of the nodeid. - The `_pytest.nodes.iterparentnodeids()` function is removed without replacement. Prefer to traverse the node hierarchy itself instead. If you really need to, copy the function from the previous pytest release. - [#​12069](https://redirect.github.com/pytest-dev/pytest/issues/12069): Delayed the deprecation of the following features to `9.0.0`: - `node-ctor-fspath-deprecation`{.interpreted-text role="ref"}. - `legacy-path-hooks-deprecated`{.interpreted-text role="ref"}. It was discovered after `8.1.0` was released that the warnings about the impeding removal were not being displayed, so the team decided to revert the removal. This is the reason for `8.1.0` being yanked. # pytest 8.1.0 (YANKED) ::: {.note} ::: {.title} Note ::: This release has been **yanked**: it broke some plugins without the proper warning period, due to some warnings not showing up as expected. See [#​12069](https://redirect.github.com/pytest-dev/pytest/issues/12069). ::: ### [`v8.1.0`](https://redirect.github.com/pytest-dev/pytest/releases/tag/8.1.0) [Compare Source](https://redirect.github.com/pytest-dev/pytest/compare/8.0.2...8.1.0) # pytest 8.1.0 (YANKED) > \[!IMPORTANT]\ > This release has been **yanked**: it broke some plugins without the proper warning period, due to some warnings not showing up as expected. See [#​12069](https://redirect.github.com/pytest-dev/pytest/issues/12069). ## Features - [#​11475](https://redirect.github.com/pytest-dev/pytest/issues/11475): Added the new `consider_namespace_packages`{.interpreted-text role="confval"} configuration option, defaulting to `False`. If set to `True`, pytest will attempt to identify modules that are part of [namespace packages](https://packaging.python.org/en/latest/guides/packaging-namespace-packages) when importing modules. - [#​11653](https://redirect.github.com/pytest-dev/pytest/issues/11653): Added the new `verbosity_test_cases`{.interpreted-text role="confval"} configuration option for fine-grained control of test execution verbosity. See `Fine-grained verbosity `{.interpreted-text role="ref"} for more details. ## Improvements - [#​10865](https://redirect.github.com/pytest-dev/pytest/issues/10865): `pytest.warns`{.interpreted-text role="func"} now validates that `warnings.warn`{.interpreted-text role="func"} was called with a \[str]{.title-ref} or a \[Warning]{.title-ref}. Currently in Python it is possible to use other types, however this causes an exception when `warnings.filterwarnings`{.interpreted-text role="func"} is used to filter those warnings (see [CPython #​103577](https://redirect.github.com/python/cpython/issues/103577) for a discussion). While this can be considered a bug in CPython, we decided to put guards in pytest as the error message produced without this check in place is confusing. - [#​11311](https://redirect.github.com/pytest-dev/pytest/issues/11311): When using `--override-ini` for paths in invocations without a configuration file defined, the current working directory is used as the relative directory. Previoulsy this would raise an `AssertionError`{.interpreted-text role="class"}. - [#​11475](https://redirect.github.com/pytest-dev/pytest/issues/11475): `--import-mode=importlib `{.interpreted-text role="ref"} now tries to import modules using the standard import mechanism (but still without changing :py`sys.path`{.interpreted-text role="data"}), falling back to importing modules directly only if that fails. This means that installed packages will be imported under their canonical name if possible first, for example `app.core.models`, instead of having the module name always be derived from their path (for example `.env310.lib.site_packages.app.core.models`). - [#​11801](https://redirect.github.com/pytest-dev/pytest/issues/11801): Added the `iter_parents() <_pytest.nodes.Node.iter_parents>`{.interpreted-text role="func"} helper method on nodes. It is similar to `listchain <_pytest.nodes.Node.listchain>`{.interpreted-text role="func"}, but goes from bottom to top, and returns an iterator, not a list. - [#​11850](https://redirect.github.com/pytest-dev/pytest/issues/11850): Added support for `sys.last_exc`{.interpreted-text role="data"} for post-mortem debugging on Python>=3.12. - [#​11962](https://redirect.github.com/pytest-dev/pytest/issues/11962): In case no other suitable candidates for configuration file are found, a `pyproject.toml` (even without a `[tool.pytest.ini_options]` table) will be considered as the configuration file and define the `rootdir`. - [#​11978](https://redirect.github.com/pytest-dev/pytest/issues/11978): Add `--log-file-mode` option to the logging plugin, enabling appending to log-files. This option accepts either `"w"` or `"a"` and defaults to `"w"`. Previously, the mode was hard-coded to be `"w"` which truncates the file before logging. - [#​12047](https://redirect.github.com/pytest-dev/pytest/issues/12047): When multiple finalizers of a fixture raise an exception, now all exceptions are reported as an exception group. Previously, only the first exception was reported. ## Bug Fixes - [#​11904](https://redirect.github.com/pytest-dev/pytest/issues/11904): Fixed a regression in pytest 8.0.0 that would cause test collection to fail due to permission errors when using `--pyargs`. This change improves the collection tree for tests specified using `--pyargs`, see `12043`{.interpreted-text role="pull"} for a comparison with pytest 8.0 and <8. - [#​12011](https://redirect.github.com/pytest-dev/pytest/issues/12011): Fixed a regression in 8.0.1 whereby `setup_module` xunit-style fixtures are not executed when `--doctest-modules` is passed. - [#​12014](https://redirect.github.com/pytest-dev/pytest/issues/12014): Fix the `stacklevel` used when warning about marks used on fixtures. - [#​12039](https://redirect.github.com/pytest-dev/pytest/issues/12039): Fixed a regression in `8.0.2` where tests created using `tmp_path`{.interpreted-text role="fixture"} have been collected multiple times in CI under Windows. ## Improved Documentation - [#​11790](https://redirect.github.com/pytest-dev/pytest/issues/11790): Documented the retention of temporary directories created using the `tmp_path` fixture in more detail. ## Trivial/Internal Changes - [#​11785](https://redirect.github.com/pytest-dev/pytest/issues/11785): Some changes were made to private functions which may affect plugins which access them: - `FixtureManager._getautousenames()` now takes a `Node` itself instead of the nodeid. - `FixtureManager.getfixturedefs()` now takes the `Node` itself instead of the nodeid. - The `_pytest.nodes.iterparentnodeids()` function is removed without replacement. Prefer to traverse the node hierarchy itself instead. If you really need to, copy the function from the previous pytest release. ### [`v8.0.2`](https://redirect.github.com/pytest-dev/pytest/releases/tag/8.0.2) [Compare Source](https://redirect.github.com/pytest-dev/pytest/compare/8.0.1...8.0.2) # pytest 8.0.2 (2024-02-24) ## Bug Fixes - [#​11895](https://redirect.github.com/pytest-dev/pytest/issues/11895): Fix collection on Windows where initial paths contain the short version of a path (for example `c:\PROGRA~1\tests`). - [#​11953](https://redirect.github.com/pytest-dev/pytest/issues/11953): Fix an `IndexError` crash raising from `getstatementrange_ast`. - [#​12021](https://redirect.github.com/pytest-dev/pytest/issues/12021): Reverted a fix to \[--maxfail]{.title-ref} handling in pytest 8.0.0 because it caused a regression in pytest-xdist whereby session fixture teardowns may get executed multiple times when the max-fails is reached. ### [`v8.0.1`](https://redirect.github.com/pytest-dev/pytest/releases/tag/8.0.1) [Compare Source](https://redirect.github.com/pytest-dev/pytest/compare/8.0.0...8.0.1) # pytest 8.0.1 (2024-02-16) ## Bug Fixes - [#​11875](https://redirect.github.com/pytest-dev/pytest/issues/11875): Correctly handle errors from `getpass.getuser`{.interpreted-text role="func"} in Python 3.13. - [#​11879](https://redirect.github.com/pytest-dev/pytest/issues/11879): Fix an edge case where `ExceptionInfo._stringify_exception` could crash `pytest.raises`{.interpreted-text role="func"}. - [#​11906](https://redirect.github.com/pytest-dev/pytest/issues/11906): Fix regression with `pytest.warns`{.interpreted-text role="func"} using custom warning subclasses which have more than one parameter in their \[\__init\_\_]{.title-ref}. - [#​11907](https://redirect.github.com/pytest-dev/pytest/issues/11907): Fix a regression in pytest 8.0.0 whereby calling `pytest.skip`{.interpreted-text role="func"} and similar control-flow exceptions within a `pytest.warns()`{.interpreted-text role="func"} block would get suppressed instead of propagating. - [#​11929](https://redirect.github.com/pytest-dev/pytest/issues/11929): Fix a regression in pytest 8.0.0 whereby autouse fixtures defined in a module get ignored by the doctests in the module. - [#​11937](https://redirect.github.com/pytest-dev/pytest/issues/11937): Fix a regression in pytest 8.0.0 whereby items would be collected in reverse order in some circumstances. ### [`v8.0.0`](https://redirect.github.com/pytest-dev/pytest/releases/tag/8.0.0): pytest 8.0.0 (2024-01-27) [Compare Source](https://redirect.github.com/pytest-dev/pytest/compare/7.4.4...8.0.0) See [8.0.0rc1](https://redirect.github.com/pytest-dev/pytest/releases/tag/8.0.0rc1) and [8.0.0rc2](https://redirect.github.com/pytest-dev/pytest/releases/tag/8.0.0rc2) for the full changes since pytest 7.4! #### Bug Fixes - [#​11842](https://redirect.github.com/pytest-dev/pytest/issues/11842): Properly escape the `reason` of a `skip `{.interpreted-text role="ref"} mark when writing JUnit XML files. - [#​11861](https://redirect.github.com/pytest-dev/pytest/issues/11861): Avoid microsecond exceeds `1_000_000` when using `log-date-format` with `%f` specifier, which might cause the test suite to crash.
splunk/addonfactory-solutions-library-python (solnlib) ### [`v6.0.1`](https://redirect.github.com/splunk/addonfactory-solutions-library-python/releases/tag/v6.0.1) [Compare Source](https://redirect.github.com/splunk/addonfactory-solutions-library-python/compare/v6.0.0...v6.0.1) ##### Bug Fixes - require splunk-sdk at least 2.0.2 ([#​414](https://redirect.github.com/splunk/addonfactory-solutions-library-python/issues/414)) ([f50bf52](https://redirect.github.com/splunk/addonfactory-solutions-library-python/commit/f50bf52abdc7ce1afb8f50f8a427e6c70421c3ac)) ### [`v6.0.0`](https://redirect.github.com/splunk/addonfactory-solutions-library-python/releases/tag/v6.0.0) [Compare Source](https://redirect.github.com/splunk/addonfactory-solutions-library-python/compare/v5.5.0...v6.0.0) ##### Features - removing requests and urllib3 dependencies ([#​413](https://redirect.github.com/splunk/addonfactory-solutions-library-python/issues/413)) ([a6fa555](https://redirect.github.com/splunk/addonfactory-solutions-library-python/commit/a6fa555ec8e724654a03fe200a94f643fd1c229e)) ##### BREAKING CHANGES - removing requests and urllib3 dependencies ### [`v5.5.0`](https://redirect.github.com/splunk/addonfactory-solutions-library-python/releases/tag/v5.5.0) [Compare Source](https://redirect.github.com/splunk/addonfactory-solutions-library-python/compare/v5.4.0...v5.5.0) ##### Features - add function to get the proxy details ([#​406](https://redirect.github.com/splunk/addonfactory-solutions-library-python/issues/406)) ([c9e1f73](https://redirect.github.com/splunk/addonfactory-solutions-library-python/commit/c9e1f7350620963422747d90cfde529d3bb17511))
splunk/addonfactory-ucc-generator (splunk-add-on-ucc-framework) ### [`v5.54.0`](https://redirect.github.com/splunk/addonfactory-ucc-generator/releases/tag/v5.54.0) [Compare Source](https://redirect.github.com/splunk/addonfactory-ucc-generator/compare/v5.53.2...v5.54.0) ##### Bug Fixes - allow packaging from 23.0 ([#​1484](https://redirect.github.com/splunk/addonfactory-ucc-generator/issues/1484)) ([29accc4](https://redirect.github.com/splunk/addonfactory-ucc-generator/commit/29accc40a6c560f0181473627d0552a53af878b4)) - display newest information in row more info section ([#​1445](https://redirect.github.com/splunk/addonfactory-ucc-generator/issues/1445)) ([2b34c6b](https://redirect.github.com/splunk/addonfactory-ucc-generator/commit/2b34c6b226619d0cfed6582a35181b7705de3983)), closes [#​1410](https://redirect.github.com/splunk/addonfactory-ucc-generator/issues/1410) - required star visibility when using modify prop ([#​1489](https://redirect.github.com/splunk/addonfactory-ucc-generator/issues/1489)) ([e1fe2b0](https://redirect.github.com/splunk/addonfactory-ucc-generator/commit/e1fe2b0b8322c5c49745ee3cc93cf538142325e0)) - support Windows when checking library version ([#​1482](https://redirect.github.com/splunk/addonfactory-ucc-generator/issues/1482)) ([db17b5c](https://redirect.github.com/splunk/addonfactory-ucc-generator/commit/db17b5c869b174639b0c24e5413bc9b517950940)) ##### Features - add license during init command ([#​1475](https://redirect.github.com/splunk/addonfactory-ucc-generator/issues/1475)) ([471294a](https://redirect.github.com/splunk/addonfactory-ucc-generator/commit/471294ae8e4c266a2f685aa4c01eb75fd1974db1)) - confirmation modal when activate/deactivate single input ([#​1421](https://redirect.github.com/splunk/addonfactory-ucc-generator/issues/1421)) ([34c8ec2](https://redirect.github.com/splunk/addonfactory-ucc-generator/commit/34c8ec250861eb06bd1cd4b22b430e5aa7e26a7c)) - do not create **pycache** in lib dir ([#​1469](https://redirect.github.com/splunk/addonfactory-ucc-generator/issues/1469)) ([ad58e50](https://redirect.github.com/splunk/addonfactory-ucc-generator/commit/ad58e50ca2b5588f6824a4da95a15e8c0857f032)) - **inputs:** show input services status count ([#​1430](https://redirect.github.com/splunk/addonfactory-ucc-generator/issues/1430)) ([2574451](https://redirect.github.com/splunk/addonfactory-ucc-generator/commit/257445159898a2207cdf7a397345c218678c8fcb)) ### [`v5.53.2`](https://redirect.github.com/splunk/addonfactory-ucc-generator/releases/tag/v5.53.2) [Compare Source](https://redirect.github.com/splunk/addonfactory-ucc-generator/compare/v5.53.1...v5.53.2) ##### Bug Fixes - **api:** cancelled requests don't emit user facing errors ([#​1472](https://redirect.github.com/splunk/addonfactory-ucc-generator/issues/1472)) ([0970441](https://redirect.github.com/splunk/addonfactory-ucc-generator/commit/09704416b5a56ddb518eabd01d596ec5e23157e3)) ### [`v5.53.1`](https://redirect.github.com/splunk/addonfactory-ucc-generator/releases/tag/v5.53.1) [Compare Source](https://redirect.github.com/splunk/addonfactory-ucc-generator/compare/v5.53.0...v5.53.1) ##### Bug Fixes - **select:** fetching options when some dependency is null ([#​1463](https://redirect.github.com/splunk/addonfactory-ucc-generator/issues/1463)) ([feb9bdf](https://redirect.github.com/splunk/addonfactory-ucc-generator/commit/feb9bdf27488fcd357e57e47173d72971cf24f35)) ### [`v5.53.0`](https://redirect.github.com/splunk/addonfactory-ucc-generator/releases/tag/v5.53.0) [Compare Source](https://redirect.github.com/splunk/addonfactory-ucc-generator/compare/v5.52.0...v5.53.0) ##### Bug Fixes - **Dropdown:** fix showing selected option when value is numeric ([#​1439](https://redirect.github.com/splunk/addonfactory-ucc-generator/issues/1439)) ([9e7394a](https://redirect.github.com/splunk/addonfactory-ucc-generator/commit/9e7394a2312238a79b9b5cb8d55f1427a6073696)) - generate oauth authentication fields for OpenAPI integration ([#​1425](https://redirect.github.com/splunk/addonfactory-ucc-generator/issues/1425)) ([beb561b](https://redirect.github.com/splunk/addonfactory-ucc-generator/commit/beb561b25755cbcc51326848bc78891f89cf47b3)) - **table:** custom mapping for values in Status column ([#​1451](https://redirect.github.com/splunk/addonfactory-ucc-generator/issues/1451)) ([4721738](https://redirect.github.com/splunk/addonfactory-ucc-generator/commit/472173801a50be6c9ac7ae91ab4a9d129d1bfd86)) ##### Features - add ability to provide custom pip flags ([#​1447](https://redirect.github.com/splunk/addonfactory-ucc-generator/issues/1447)) ([718c897](https://redirect.github.com/splunk/addonfactory-ucc-generator/commit/718c897347bd2db539354f6625be074e6d90d988)) - add grouping to configuration page ([#​1432](https://redirect.github.com/splunk/addonfactory-ucc-generator/issues/1432)) ([b94b228](https://redirect.github.com/splunk/addonfactory-ucc-generator/commit/b94b2289fec8e33d53414db36c6504428d84546c)) - deprecate .uccignore and upgrade additional_package ([#​1415](https://redirect.github.com/splunk/addonfactory-ucc-generator/issues/1415)) ([f6dd96f](https://redirect.github.com/splunk/addonfactory-ucc-generator/commit/f6dd96feadef395d92ca3c7c0a3a6ff70c3c8f10))
splunk/addonfactory-github-workflows (splunk/addonfactory-github-workflows) ### [`v1.7`](https://redirect.github.com/splunk/addonfactory-github-workflows/compare/v1.6...v1.7) [Compare Source](https://redirect.github.com/splunk/addonfactory-github-workflows/compare/v1.6...v1.7)

Configuration

📅 Schedule: Branch creation - "every 2 weeks on Sunday" (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.

renovate[bot] commented 2 days ago

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

The artifact failure details are included below:

File name: poetry.lock
Updating dependencies
Resolving dependencies...

The current project's Python requirement (>=3.7,<4.0) is not compatible with some of the required packages Python requirement:
  - solnlib requires Python <3.14,>=3.7, so it will not be satisfied for Python >=3.14,<4.0
  - solnlib requires Python <3.14,>=3.7, so it will not be satisfied for Python >=3.14,<4.0

Because no versions of solnlib match >6.0.0,<6.0.1 || >6.0.1,<7.0.0
 and solnlib (6.0.0) requires Python <3.14,>=3.7, solnlib is forbidden.
So, because solnlib (6.0.1) requires Python <3.14,>=3.7
 and splunktaucclib depends on solnlib (^6.0.0), version solving failed.

  • Check your dependencies Python requirement: The Python requirement can be specified via the `python` or `markers` properties

    For solnlib, a possible solution would be to set the `python` property to ">=3.7,<3.14"
    For solnlib, a possible solution would be to set the `python` property to ">=3.7,<3.14"

    https://python-poetry.org/docs/dependency-specification/#python-restricted-dependencies,
    https://python-poetry.org/docs/dependency-specification/#using-environment-markers