Merge branch 'main' into feat/tests-with-uv

Author: sgaist

.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.1"
+  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.15.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/)

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/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.

changelog/13823.feature.rst

@@ -0,0 +1,18 @@
+Added a :confval:`strict` configuration option to enable all strictness-related options.
+
+When set to ``true``, the :confval:`strict` option currently enables
+
+* :confval:`strict_config`
+* :confval:`strict_markers`
+* :confval:`strict_parametrization_ids`
+* :confval:`strict_xfail`
+
+The individual strictness options can be explicitly set to override the global :confval:`strict` setting.
+
+The previously-deprecated ``--strict`` command-line flag now enables strict mode.
+
+If pytest adds new strictness options in the future, they will also be enabled in strict mode.
+Therefore, you should only enable strict mode if you use a pinned/locked version of pytest,
+or if you want to proactively adopt new strictness options as they are added.
+
+See :ref:`strict mode` for more details.

changelog/13823.improvement.rst

@@ -0,0 +1,4 @@
+Added :confval:`strict_xfail` as an alias to the ``xfail_strict`` option,
+:confval:`strict_config` as an alias to the ``--strict-config`` flag,
+and :confval:`strict_markers` as an alias to the ``--strict-markers`` flag.
+This makes all strictness options consistently have configuration options with the prefix ``strict_``.

changelog/13841.contrib.rst

@@ -0,0 +1 @@
+``tox>=4`` is now required when contributing to pytest.