test_ok2/changelog
Kodi Arfer 3683722bcb
FormattedExcinfo.get_source: avoid crash when line number is out-of-bounds/negative
pytest could crash given pathological AST position attributes, which shouldn't happen when testing real Python code, but could happen when testing AST produced by e.g. Hylang.

Another example of the failure is in the nightly CI for the JAX project: https://github.com/google/jax/actions/runs/4607513902/jobs/8142126075

Co-authored-by: Bruno Oliveira <nicoddemus@gmail.com>
Co-authored-by: Jake VanderPlas <jakevdp@google.com>
2023-04-05 22:48:24 -03:00
..
1904.bugfix.rst Correctly handle tracebackhide for chained exceptions (#10772) 2023-03-15 08:10:25 -03:00
6267.improvement.rst Avoid truncation when truncating means longer output (#10446) 2022-12-17 10:24:46 -03:00
7431.feature.rst Add --log-disable CLI option (#10371) 2022-10-23 18:23:34 -03:00
8141.feature.rst Change the default policy to all 2022-12-25 00:18:38 +09:00
10226.improvement.rst Use exceptiongroup for teardown errors 2022-10-23 15:45:50 -07:00
10525.feature.rst Class methods can now be discovered as tests (#10552) 2022-12-02 15:53:04 +00:00
10658.improvement.rst Allow spaces in -p arguments (#10658) 2023-01-21 08:22:44 -03:00
10669.trivial.rst Drop attrs dependency, use dataclasses instead (#10669) 2023-01-20 11:13:36 +02:00
10710.improvement.rst Propagate timestamps from CallInfo to TestReport objects (#10711) 2023-02-10 17:52:54 -03:00
10727.improvement.rst split up report header lines 2023-03-17 21:58:26 +01:00
10743.bugfix.rst Fix walrus operator support in assertion rewriting (#10758) 2023-03-10 07:32:36 -03:00
10755.feature.rst New option to allow a progress report even when capture=no (#10755) 2023-03-07 17:49:37 -03:00
10765.bugfix.rst Apply suggestions from code review 2023-02-28 11:02:17 -03:00
10782.doc.rst Fix example in the documentation (#10782) 2023-03-05 17:01:21 +01:00
10840.improvement.rst FormattedExcinfo.get_source: avoid crash when line number is out-of-bounds/negative 2023-04-05 22:48:24 -03:00
README.rst docs: use doc/en/_build/html for html output (#6842) 2020-02-29 00:47:30 +01:00
_template.rst Update CHANGELOG template to put issue links at the start of entries 2018-07-07 11:02:33 -03:00

README.rst

This directory contains "newsfragments" which are short files that contain a small **ReST**-formatted
text that will be added to the next ``CHANGELOG``.

The ``CHANGELOG`` will be read by **users**, so this description should be aimed to pytest users
instead of describing internal changes which are only relevant to the developers.

Make sure to use full sentences in the **past or present tense** and use punctuation, examples::

    Improved verbose diff output with sequences.

    Terminal summary statistics now use multiple colors.

Each file should be named like ``<ISSUE>.<TYPE>.rst``, where
``<ISSUE>`` is an issue number, and ``<TYPE>`` is one of:

* ``feature``: new user facing features, like new command-line options and new behavior.
* ``improvement``: improvement of existing functionality, usually without requiring user intervention (for example, new fields being written in ``--junitxml``, improved colors in terminal, etc).
* ``bugfix``: fixes a bug.
* ``doc``: documentation improvement, like rewording an entire session or adding missing docs.
* ``deprecation``: feature deprecation.
* ``breaking``: a change which may break existing suites, such as feature removal or behavior change.
* ``vendor``: changes in packages vendored in pytest.
* ``trivial``: fixing a small typo or internal change that might be noteworthy.

So for example: ``123.feature.rst``, ``456.bugfix.rst``.

If your PR fixes an issue, use that number here. If there is no issue,
then after you submit the PR and get the PR number you can add a
changelog using that instead.

If you are not sure what issue type to use, don't hesitate to ask in your PR.

``towncrier`` preserves multiple paragraphs and formatting (code blocks, lists, and so on), but for entries
other than ``features`` it is usually better to stick to a single paragraph to keep it concise.

You can also run ``tox -e docs`` to build the documentation
with the draft changelog (``doc/en/_build/html/changelog.html``) if you want to get a preview of how your change will look in the final release notes.