Merge branch 'main' into fix-exit-exceptiongroup-13650

Author: gomri15

.coveragerc

@@ -25,6 +25,7 @@ exclude_lines =
     ^\s*raise NotImplementedError\b
     ^\s*return NotImplemented\b
     ^\s*assert False(,|$)
+    ^\s*case unreachable:
     ^\s*assert_never\(
 
     ^\s*if TYPE_CHECKING:

.github/workflows/deploy.yml

@@ -50,7 +50,7 @@ jobs:
         persist-credentials: true
 
     - name: Download Package
-      uses: actions/download-artifact@v5
+      uses: actions/download-artifact@v6
       with:
         name: Packages
         path: dist
@@ -86,7 +86,7 @@ jobs:
         persist-credentials: false
 
     - name: Download Package
-      uses: actions/download-artifact@v5
+      uses: actions/download-artifact@v6
       with:
         name: Packages
         path: dist

.github/workflows/test.yml

@@ -256,7 +256,7 @@ jobs:
         persist-credentials: false
 
     - name: Download Package
-      uses: actions/download-artifact@v5
+      uses: actions/download-artifact@v6
       with:
         name: Packages
         path: dist

.pre-commit-config.yaml

@@ -1,6 +1,6 @@
 repos:
 - repo: https://github.com/astral-sh/ruff-pre-commit
-  rev: "v0.14.0"
+  rev: "v0.14.2"
   hooks:
     - id: ruff-check
       args: ["--fix"]
@@ -12,7 +12,7 @@ repos:
     -   id: end-of-file-fixer
     -   id: check-yaml
 - repo: https://github.com/woodruffw/zizmor-pre-commit
-  rev: v1.14.2
+  rev: v1.16.0
   hooks:
     - id: zizmor
 -   repo: https://github.com/adamchainz/blacken-docs
@@ -48,7 +48,7 @@ repos:
             # on <3.11
           - exceptiongroup>=1.0.0rc8
 -   repo: https://github.com/RobertCraigie/pyright-python
-    rev: v1.1.406
+    rev: v1.1.407
     hooks:
     -   id: pyright
         files: ^(src/|scripts/)
@@ -66,7 +66,7 @@ repos:
         # Manual because passing pyright is a work in progress.
         stages: [manual]
 - repo: https://github.com/tox-dev/pyproject-fmt
-  rev: "v2.10.0"
+  rev: "v2.11.0"
   hooks:
     - id: pyproject-fmt
       # https://pyproject-fmt.readthedocs.io/en/latest/#calculating-max-supported-python-version

AUTHORS

@@ -83,6 +83,7 @@ Carlos Jenkins
 Ceridwen
 Charles Cloud
 Charles Machalow
+Charles-Meldhine Madi Mnemoi (cmnemoi)
 Charnjit SiNGH (CCSJ)
 Cheuk Ting Ho
 Chris Mahoney

CONTRIBUTING.rst

@@ -203,7 +203,7 @@ Short version
 
 #. Write a ``changelog`` entry: ``changelog/2574.bugfix.rst``, use issue id number
    and one of ``feature``, ``improvement``, ``bugfix``, ``doc``, ``deprecation``,
-   ``breaking``, ``vendor`` or ``trivial`` for the issue type.
+   ``breaking``, ``vendor``, ``packaging``, ``contrib``, or ``misc`` for the issue type.
 
 
 #. Unless your change is a trivial or a documentation fix (e.g., a typo or reword of a small section) please
@@ -305,8 +305,9 @@ Here is a simple overview, with pytest-specific bits:
 
 #. Create a new changelog entry in ``changelog``. The file should be named ``<issueid>.<type>.rst``,
    where *issueid* is the number of the issue related to the change and *type* is one of
-   ``feature``, ``improvement``, ``bugfix``, ``doc``, ``deprecation``, ``breaking``, ``vendor``
-   or ``trivial``. You may skip creating the changelog entry if the change doesn't affect the
+   ``feature``, ``improvement``, ``bugfix``, ``doc``, ``deprecation``, ``breaking``, ``vendor``,
+   ``packaging``, ``contrib``, or ``misc``.
+   You may skip creating the changelog entry if the change doesn't affect the
    documented behaviour of pytest.
 
 #. Add yourself to ``AUTHORS`` file if not there yet, in alphabetical order.

README.rst

@@ -79,7 +79,7 @@ To execute it::
     ========================== 1 failed in 0.04 seconds ===========================
 
 
-Due to ``pytest``'s detailed assertion introspection, only plain ``assert`` statements are used. See `getting-started <https://docs.pytest.org/en/stable/getting-started.html#our-first-test-run>`_ for more examples.
+Thanks to ``pytest``'s detailed assertion introspection, you can simply use plain ``assert`` statements. See `getting-started <https://docs.pytest.org/en/stable/getting-started.html#our-first-test-run>`_ for more examples.
 
 
 Features

changelog/13537.bugfix.rst

@@ -0,0 +1 @@
+Fix bug in which ExceptionGroup with only Skipped exceptions in teardown was not handled correctly and showed as error.

changelog/1367.feature.rst

@@ -0,0 +1,28 @@
+**Support for subtests** has been added.
+
+:ref:`subtests <subtests>` are an alternative to parametrization, useful in situations where the parametrization values are not all known at collection time.
+
+**Example**
+
+.. code-block:: python
+
+    def contains_docstring(p: Path) -> bool:
+        """Return True if the given Python file contains a top-level docstring."""
+        ...
+
+
+    def test_py_files_contain_docstring(subtests: pytest.Subtests) -> None:
+        for path in Path.cwd().glob("*.py"):
+            with subtests.test(path=str(path)):
+                assert contains_docstring(path)
+
+
+Each assert failure or error is caught by the context manager and reported individually, giving a clear picture of all files that are missing a docstring.
+
+In addition, :meth:`unittest.TestCase.subTest` is now also supported.
+
+This feature was originally implemented as a separate plugin in `pytest-subtests <https://github.com/pytest-dev/pytest-subtests>`__, but since then has been merged into the core.
+
+.. note::
+
+    This feature is experimental and will likely evolve in future releases. By that we mean that we might change how subtests are reported on failure, but the functionality and how to use it are stable.

changelog/13743.feature.rst

@@ -0,0 +1,37 @@
+Added support for native TOML configuration files.
+
+While pytest, since version 6, supports configuration in ``pyproject.toml`` files under ``[tool.pytest.ini_options]``,
+it does so in an "INI compatibility mode", where all configuration values are treated as strings or list of strings.
+Now, pytest supports the native TOML data model.
+
+In ``pyproject.toml``, the native TOML configuration is under the ``[tool.pytest]`` table.
+
+.. code-block:: toml
+
+    # pyproject.toml
+    [tool.pytest]
+    minversion = "9.0"
+    addopts = ["-ra", "-q"]
+    testpaths = [
+        "tests",
+        "integration",
+    ]
+
+The ``[tool.pytest.ini_options]`` table remains supported, but both tables cannot be used at the same time.
+
+If you prefer to use a separate configuration file, or don't use ``pyproject.toml``, you can use ``pytest.toml`` or ``.pytest.toml``:
+
+.. code-block:: toml
+
+    # pytest.toml or .pytest.toml
+    [pytest]
+    minversion = "9.0"
+    addopts = ["-ra", "-q"]
+    testpaths = [
+        "tests",
+        "integration",
+    ]
+
+The documentation now shows configuration snippets in both TOML and INI formats, in a tabbed interface.
+
+See :ref:`config file formats` for full details.