Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
This PR contains the following updates:
| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
| [black](https://redirect.github.com/psf/black)
([changelog](https://redirect.github.com/psf/black/blob/main/CHANGES.md))
| `^23.7.0` -> `^24.0.0` |
[](https://docs.renovatebot.com/merge-confidence/)
|
[](https://docs.renovatebot.com/merge-confidence/)
|
[](https://docs.renovatebot.com/merge-confidence/)
|
[](https://docs.renovatebot.com/merge-confidence/)
|
| [pytest](https://redirect.github.com/pytest-dev/pytest)
([changelog](https://docs.pytest.org/en/stable/changelog.html)) |
`^7.4.0` -> `^8.0.0` |
[](https://docs.renovatebot.com/merge-confidence/)
|
[](https://docs.renovatebot.com/merge-confidence/)
|
[](https://docs.renovatebot.com/merge-confidence/)
|
[](https://docs.renovatebot.com/merge-confidence/)
|
| [pytest-cov](https://redirect.github.com/pytest-dev/pytest-cov)
([changelog](https://pytest-cov.readthedocs.io/en/latest/changelog.html))
| `^4.1.0` -> `^5.0.0` |
[](https://docs.renovatebot.com/merge-confidence/)
|
[](https://docs.renovatebot.com/merge-confidence/)
|
[](https://docs.renovatebot.com/merge-confidence/)
|
[](https://docs.renovatebot.com/merge-confidence/)
|
| [safety](https://redirect.github.com/pyupio/safety) | `^2.3.5` ->
`^3.0.0` |
[](https://docs.renovatebot.com/merge-confidence/)
|
[](https://docs.renovatebot.com/merge-confidence/)
|
[](https://docs.renovatebot.com/merge-confidence/)
|
[](https://docs.renovatebot.com/merge-confidence/)
|
---
### Release Notes
<details>
<summary>psf/black (black)</summary>
###
[`v24.8.0`](https://redirect.github.com/psf/black/blob/HEAD/CHANGES.md#2480)
[Compare
Source](https://redirect.github.com/psf/black/compare/24.4.2...24.8.0)
##### Stable style
- Fix crash when `# fmt: off` is used before a closing parenthesis or
bracket.
([#​4363](https://redirect.github.com/psf/black/issues/4363))
##### Packaging
- Packaging metadata updated: docs are explictly linked, the issue
tracker is now also
linked. This improves the PyPI listing for Black.
([#​4345](https://redirect.github.com/psf/black/issues/4345))
##### Parser
- Fix regression where Black failed to parse a multiline f-string
containing another
multiline string
([#​4339](https://redirect.github.com/psf/black/issues/4339))
- Fix regression where Black failed to parse an escaped single quote
inside an f-string
([#​4401](https://redirect.github.com/psf/black/issues/4401))
- Fix bug with Black incorrectly parsing empty lines with a backslash
([#​4343](https://redirect.github.com/psf/black/issues/4343))
- Fix bugs with Black's tokenizer not handling `\{` inside f-strings
very well
([#​4422](https://redirect.github.com/psf/black/issues/4422))
- Fix incorrect line numbers in the tokenizer for certain tokens within
f-strings
([#​4423](https://redirect.github.com/psf/black/issues/4423))
##### Performance
- Improve performance when a large directory is listed in `.gitignore`
([#​4415](https://redirect.github.com/psf/black/issues/4415))
##### *Blackd*
- Fix blackd (and all extras installs) for docker container
([#​4357](https://redirect.github.com/psf/black/issues/4357))
###
[`v24.4.2`](https://redirect.github.com/psf/black/blob/HEAD/CHANGES.md#2442)
[Compare
Source](https://redirect.github.com/psf/black/compare/24.4.1...24.4.2)
This is a bugfix release to fix two regressions in the new f-string
parser introduced in
24.4.1.
##### Parser
- Fix regression where certain complex f-strings failed to parse
([#​4332](https://redirect.github.com/psf/black/issues/4332))
##### Performance
- Fix bad performance on certain complex string literals
([#​4331](https://redirect.github.com/psf/black/issues/4331))
###
[`v24.4.1`](https://redirect.github.com/psf/black/blob/HEAD/CHANGES.md#2441)
[Compare
Source](https://redirect.github.com/psf/black/compare/24.4.0...24.4.1)
##### Highlights
- Add support for the new Python 3.12 f-string syntax introduced by PEP
701 ([#​3822](https://redirect.github.com/psf/black/issues/3822))
##### Stable style
- Fix crash involving indented dummy functions containing newlines
([#​4318](https://redirect.github.com/psf/black/issues/4318))
##### Parser
- Add support for type parameter defaults, a new syntactic feature added
to Python 3.13
by PEP 696
([#​4327](https://redirect.github.com/psf/black/issues/4327))
##### Integrations
- Github Action now works even when `git archive` is skipped
([#​4313](https://redirect.github.com/psf/black/issues/4313))
###
[`v24.4.0`](https://redirect.github.com/psf/black/blob/HEAD/CHANGES.md#2440)
[Compare
Source](https://redirect.github.com/psf/black/compare/24.3.0...24.4.0)
##### Stable style
- Fix unwanted crashes caused by AST equivalency check
([#​4290](https://redirect.github.com/psf/black/issues/4290))
##### Preview style
- `if` guards in `case` blocks are now wrapped in parentheses when the
line is too long.
([#​4269](https://redirect.github.com/psf/black/issues/4269))
- Stop moving multiline strings to a new line unless inside brackets
([#​4289](https://redirect.github.com/psf/black/issues/4289))
##### Integrations
- Add a new option `use_pyproject` to the GitHub Action `psf/black`.
This will read the
Black version from `pyproject.toml`.
([#​4294](https://redirect.github.com/psf/black/issues/4294))
###
[`v24.3.0`](https://redirect.github.com/psf/black/blob/HEAD/CHANGES.md#2430)
[Compare
Source](https://redirect.github.com/psf/black/compare/24.2.0...24.3.0)
##### Highlights
This release is a milestone: it fixes Black's first CVE security
vulnerability. If you
run Black on untrusted input, or if you habitually put thousands of
leading tab
characters in your docstrings, you are strongly encouraged to upgrade
immediately to fix
[CVE-2024-21503](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-21503).
This release also fixes a bug in Black's AST safety check that allowed
Black to make
incorrect changes to certain f-strings that are valid in Python 3.12 and
higher.
##### Stable style
- Don't move comments along with delimiters, which could cause crashes
([#​4248](https://redirect.github.com/psf/black/issues/4248))
- Strengthen AST safety check to catch more unsafe changes to strings.
Previous versions
of Black would incorrectly format the contents of certain unusual
f-strings containing
nested strings with the same quote type. Now, Black will crash on such
strings until
support for the new f-string syntax is implemented.
([#​4270](https://redirect.github.com/psf/black/issues/4270))
- Fix a bug where line-ranges exceeding the last code line would not
work as expected
([#​4273](https://redirect.github.com/psf/black/issues/4273))
##### Performance
- Fix catastrophic performance on docstrings that contain large numbers
of leading tab
characters. This fixes
[CVE-2024-21503](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-21503).
([#​4278](https://redirect.github.com/psf/black/issues/4278))
##### Documentation
- Note what happens when `--check` is used with `--quiet`
([#​4236](https://redirect.github.com/psf/black/issues/4236))
###
[`v24.2.0`](https://redirect.github.com/psf/black/blob/HEAD/CHANGES.md#2420)
[Compare
Source](https://redirect.github.com/psf/black/compare/24.1.1...24.2.0)
##### Stable style
- Fixed a bug where comments where mistakenly removed along with
redundant parentheses
([#​4218](https://redirect.github.com/psf/black/issues/4218))
##### Preview style
- Move the `hug_parens_with_braces_and_square_brackets` feature to the
unstable style
due to an outstanding crash and proposed formatting tweaks
([#​4198](https://redirect.github.com/psf/black/issues/4198))
- Fixed a bug where base expressions caused inconsistent formatting of
\*\* in tenary
expression
([#​4154](https://redirect.github.com/psf/black/issues/4154))
- Checking for newline before adding one on docstring that is almost at
the line limit
([#​4185](https://redirect.github.com/psf/black/issues/4185))
- Remove redundant parentheses in `case` statement `if` guards
([#​4214](https://redirect.github.com/psf/black/issues/4214)).
##### Configuration
- Fix issue where *Black* would ignore input files in the presence of
symlinks
([#​4222](https://redirect.github.com/psf/black/issues/4222))
- *Black* now ignores `pyproject.toml` that is missing a `tool.black`
section when
discovering project root and configuration. Since *Black* continues to
use version
control as an indicator of project root, this is expected to primarily
change behavior
for users in a monorepo setup (desirably). If you wish to preserve
previous behavior,
simply add an empty `[tool.black]` to the previously discovered
`pyproject.toml`
([#​4204](https://redirect.github.com/psf/black/issues/4204))
##### Output
- Black will swallow any `SyntaxWarning`s or `DeprecationWarning`s
produced by the `ast`
module when performing equivalence checks
([#​4189](https://redirect.github.com/psf/black/issues/4189))
##### Integrations
- Add a JSONSchema and provide a validate-pyproject entry-point
([#​4181](https://redirect.github.com/psf/black/issues/4181))
###
[`v24.1.1`](https://redirect.github.com/psf/black/blob/HEAD/CHANGES.md#2411)
[Compare
Source](https://redirect.github.com/psf/black/compare/24.1.0...24.1.1)
Bugfix release to fix a bug that made Black unusable on certain file
systems with strict
limits on path length.
##### Preview style
- Consistently add trailing comma on typed parameters
([#​4164](https://redirect.github.com/psf/black/issues/4164))
##### Configuration
- Shorten the length of the name of the cache file to fix crashes on
file systems that
do not support long paths
([#​4176](https://redirect.github.com/psf/black/issues/4176))
###
[`v24.1.0`](https://redirect.github.com/psf/black/blob/HEAD/CHANGES.md#2410)
[Compare
Source](https://redirect.github.com/psf/black/compare/23.12.1...24.1.0)
##### Highlights
This release introduces the new 2024 stable style
([#​4106](https://redirect.github.com/psf/black/issues/4106)),
stabilizing the following
changes:
- Add parentheses around `if`-`else` expressions
([#​2278](https://redirect.github.com/psf/black/issues/2278))
- Dummy class and function implementations consisting only of `...` are
formatted more
compactly
([#​3796](https://redirect.github.com/psf/black/issues/3796))
- If an assignment statement is too long, we now prefer splitting on the
right-hand side
([#​3368](https://redirect.github.com/psf/black/issues/3368))
- Hex codes in Unicode escape sequences are now standardized to
lowercase
([#​2916](https://redirect.github.com/psf/black/issues/2916))
- Allow empty first lines at the beginning of most blocks
([#​3967](https://redirect.github.com/psf/black/issues/3967),
[#​4061](https://redirect.github.com/psf/black/issues/4061))
- Add parentheses around long type annotations
([#​3899](https://redirect.github.com/psf/black/issues/3899))
- Enforce newline after module docstrings
([#​3932](https://redirect.github.com/psf/black/issues/3932),
[#​4028](https://redirect.github.com/psf/black/issues/4028))
- Fix incorrect magic trailing comma handling in return types
([#​3916](https://redirect.github.com/psf/black/issues/3916))
- Remove blank lines before class docstrings
([#​3692](https://redirect.github.com/psf/black/issues/3692))
- Wrap multiple context managers in parentheses if combined in a single
`with` statement
([#​3489](https://redirect.github.com/psf/black/issues/3489))
- Fix bug in line length calculations for power operations
([#​3942](https://redirect.github.com/psf/black/issues/3942))
- Add trailing commas to collection literals even if there's a comment
after the last
entry
([#​3393](https://redirect.github.com/psf/black/issues/3393))
- When using `--skip-magic-trailing-comma` or `-C`, trailing commas are
stripped from
subscript expressions with more than 1 element
([#​3209](https://redirect.github.com/psf/black/issues/3209))
- Add extra blank lines in stubs in a few cases
([#​3564](https://redirect.github.com/psf/black/issues/3564),
[#​3862](https://redirect.github.com/psf/black/issues/3862))
- Accept raw strings as docstrings
([#​3947](https://redirect.github.com/psf/black/issues/3947))
- Split long lines in case blocks
([#​4024](https://redirect.github.com/psf/black/issues/4024))
- Stop removing spaces from walrus operators within subscripts
([#​3823](https://redirect.github.com/psf/black/issues/3823))
- Fix incorrect formatting of certain async statements
([#​3609](https://redirect.github.com/psf/black/issues/3609))
- Allow combining `# fmt: skip` with other comments
([#​3959](https://redirect.github.com/psf/black/issues/3959))
There are already a few improvements in the `--preview` style, which are
slated for the
2025 stable style. Try them out and
[share your feedback](https://redirect.github.com/psf/black/issues). In
the past, the preview
style has included some features that we were not able to stabilize.
This year, we're
adding a separate `--unstable` style for features with known problems.
Now, the
`--preview` style only includes features that we actually expect to make
it into next
year's stable style.
##### Stable style
Several bug fixes were made in features that are moved to the stable
style in this
release:
- Fix comment handling when parenthesising conditional expressions
([#​4134](https://redirect.github.com/psf/black/issues/4134))
- Fix bug where spaces were not added around parenthesized walruses in
subscripts,
unlike other binary operators
([#​4109](https://redirect.github.com/psf/black/issues/4109))
- Remove empty lines before docstrings in async functions
([#​4132](https://redirect.github.com/psf/black/issues/4132))
- Address a missing case in the change to allow empty lines at the
beginning of all
blocks, except immediately before a docstring
([#​4130](https://redirect.github.com/psf/black/issues/4130))
- For stubs, fix logic to enforce empty line after nested classes with
bodies
([#​4141](https://redirect.github.com/psf/black/issues/4141))
##### Preview style
- Add `--unstable` style, covering preview features that have known
problems that would
block them from going into the stable style. Also add the
`--enable-unstable-feature`
flag; for example, use
`--enable-unstable-feature hug_parens_with_braces_and_square_brackets`
to apply this
preview feature throughout 2024, even if a later Black release
downgrades the feature
to unstable
([#​4096](https://redirect.github.com/psf/black/issues/4096))
- Format module docstrings the same as class and function docstrings
([#​4095](https://redirect.github.com/psf/black/issues/4095))
- Fix crash when using a walrus in a dictionary
([#​4155](https://redirect.github.com/psf/black/issues/4155))
- Fix unnecessary parentheses when wrapping long dicts
([#​4135](https://redirect.github.com/psf/black/issues/4135))
- Stop normalizing spaces before `# fmt: skip` comments
([#​4146](https://redirect.github.com/psf/black/issues/4146))
##### Configuration
- Print warning when configuration in `pyproject.toml` contains an
invalid key
([#​4165](https://redirect.github.com/psf/black/issues/4165))
- Fix symlink handling, properly ignoring symlinks that point outside of
root ([#​4161](https://redirect.github.com/psf/black/issues/4161))
- Fix cache mtime logic that resulted in false positive cache hits
([#​4128](https://redirect.github.com/psf/black/issues/4128))
- Remove the long-deprecated `--experimental-string-processing` flag.
This feature can
currently be enabled with `--preview --enable-unstable-feature
string_processing`.
([#​4096](https://redirect.github.com/psf/black/issues/4096))
##### Integrations
- Revert the change to run Black's pre-commit integration only on
specific git hooks
([#​3940](https://redirect.github.com/psf/black/issues/3940)) for
better compatibility with older versions of pre-commit
([#​4137](https://redirect.github.com/psf/black/issues/4137))
</details>
<details>
<summary>pytest-dev/pytest (pytest)</summary>
###
[`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/compare/8.2.2...8.3.0)
[Compare
Source](https://redirect.github.com/pytest-dev/pytest/compare/8.2.2...8.3.0)
###
[`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 <args-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
<unittest.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
<pytest.FixtureRequest.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 <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
<pytest.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 <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
<pytest.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 <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 <pytest.mark.skip
ref>`{.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.
</details>
<details>
<summary>pytest-dev/pytest-cov (pytest-cov)</summary>
###
[`v5.0.0`](https://redirect.github.com/pytest-dev/pytest-cov/blob/HEAD/CHANGELOG.rst#500-2024-03-24)
[Compare
Source](https://redirect.github.com/pytest-dev/pytest-cov/compare/v4.1.0...v5.0.0)
- Removed support for xdist rsync (now deprecated).
Contributed by Matthias Reichenbach in `#​623
<https://github.com/pytest-dev/pytest-cov/pull/623>`\_.
- Switched docs theme to Furo.
- Various legacy Python cleanup and CI improvements.
Contributed by Christian Clauss and Hugo van Kemenade in
`#​630 <https://github.com/pytest-dev/pytest-cov/pull/630>`*,
`#​631 <https://github.com/pytest-dev/pytest-cov/pull/631>`*,
`#​632 <https://github.com/pytest-dev/pytest-cov/pull/632>`\_ and
`#​633 <https://github.com/pytest-dev/pytest-cov/pull/633>`\_.
- Added a `pyproject.toml` example in the docs.
Contributed by Dawn James in `#​626
<https://github.com/pytest-dev/pytest-cov/pull/626>`\_.
- Modernized project's pre-commit hooks to use ruff. Initial POC
contributed by
Christian Clauss in `#​584
<https://github.com/pytest-dev/pytest-cov/pull/584>`\_.
</details>
<details>
<summary>pyupio/safety (safety)</summary>
###
[`v3.2.7`](https://redirect.github.com/pyupio/safety/blob/HEAD/CHANGELOG.md#327---2024-08-29)
[Compare
Source](https://redirect.github.com/pyupio/safety/compare/3.2.6...3.2.7)
- fix/increase-auth-timeout: increase timeout to 5s
([#​583](https://redirect.github.com/pyupio/safety/issues/583))
- Update Issue Templates: Add Feature Request Template and Improve Issue
Submission Process
([#​580](https://redirect.github.com/pyupio/safety/issues/580))
###
[`v3.2.6`](https://redirect.github.com/pyupio/safety/blob/HEAD/CHANGELOG.md#326---2024-08-21)
[Compare
Source](https://redirect.github.com/pyupio/safety/compare/3.2.5...3.2.6)
- fix/update-schemas-0-0-4
([#​581](https://redirect.github.com/pyupio/safety/issues/581))
- chore/update-coc-email
([#​579](https://redirect.github.com/pyupio/safety/issues/579))
- docs(contributing): add CONTRIBUTING.md with guidelines for
contributors
([#​571](https://redirect.github.com/pyupio/safety/issues/571))
- chore: update-network-url
([#​569](https://redirect.github.com/pyupio/safety/issues/569))
###
[`v3.2.5`](https://redirect.github.com/pyupio/safety/blob/HEAD/CHANGELOG.md#325---2024-08-09)
[Compare
Source](https://redirect.github.com/pyupio/safety/compare/3.2.4...3.2.5)
- fix: increment schemas version
([#​567](https://redirect.github.com/pyupio/safety/issues/567))
- Add SLA Document
([#​565](https://redirect.github.com/pyupio/safety/issues/565))
- Add Table of Contents to README.md
([#​564](https://redirect.github.com/pyupio/safety/issues/564))
- docs: code of conduct
([#​559](https://redirect.github.com/pyupio/safety/issues/559))
- Add More Badges
([#​558](https://redirect.github.com/pyupio/safety/issues/558))
- feat: fixed issue responder
([#​561](https://redirect.github.com/pyupio/safety/issues/561))
- feat(logger): config.ini, proxy, network stats
([#​547](https://redirect.github.com/pyupio/safety/issues/547))
- refactor: replace private typer functions with rich module equivalents
([#​556](https://redirect.github.com/pyupio/safety/issues/556))
- feat(safety_cli): docstrings, type hints, comments
([#​549](https://redirect.github.com/pyupio/safety/issues/549))
- feat: add GitHub Action to automatically respond to new issues
([#​554](https://redirect.github.com/pyupio/safety/issues/554))
- readme: add download badge to readme
([#​557](https://redirect.github.com/pyupio/safety/issues/557))
- fix(debug): fix --debug flag and associated tests
([#​552](https://redirect.github.com/pyupio/safety/issues/552))
- chore: release 3.2.4
([#​545](https://redirect.github.com/pyupio/safety/issues/545))
- fix(cache): handle get_from_cache=None and ensure directory exists
([#​544](https://redirect.github.com/pyupio/safety/issues/544))
- REQUEST_TIMEOUT Env Var
([#​541](https://redirect.github.com/pyupio/safety/issues/541))
- Update URLs, Lint
([#​540](https://redirect.github.com/pyupio/safety/issues/540))
###
[`v3.2.4`](https://redirect.github.com/pyupio/safety/blob/HEAD/CHANGELOG.md#324---2024-07-04)
[Compare
Source](https://redirect.github.com/pyupio/safety/compare/3.2.3...3.2.4)
- Handle `get_from_cache=None` and ensure directory exists
([#​538](https://redirect.github.com/pyupio/safety/issues/538))
- Switch filelock package to compatible release clause
([#​538](https://redirect.github.com/pyupio/safety/issues/538))
- Add filelock to `install_requires`
([#​538](https://redirect.github.com/pyupio/safety/issues/538))
###
[`v3.2.3`](https://redirect.github.com/pyupio/safety/blob/HEAD/CHANGELOG.md#323---2024-06-10)
[Compare
Source](https://redirect.github.com/pyupio/safety/compare/3.2.2...3.2.3)
- Increase request timeout to 30 seconds
([#​535](https://redirect.github.com/pyupio/safety/issues/535))
- fix: fail on none severities
([#​534](https://redirect.github.com/pyupio/safety/issues/534))
###
[`v3.2.2`](https://redirect.github.com/pyupio/safety/blob/HEAD/CHANGELOG.md#322---2024-06-07)
[Compare
Source](https://redirect.github.com/pyupio/safety/compare/3.2.1...3.2.2)
- fix: include scan template in build
([#​531](https://redirect.github.com/pyupio/safety/issues/531))
###
[`v3.2.1`](https://redirect.github.com/pyupio/safety/blob/HEAD/CHANGELOG.md#321---2024-06-04)
[Compare
Source](https://redirect.github.com/pyupio/safety/compare/3.2.0...3.2.1)
- fix: include all templates in the manifest
([#​529](https://redirect.github.com/pyupio/safety/issues/529))
- fix: use available email verification claims
([#​528](https://redirect.github.com/pyupio/safety/issues/528))
###
[`v3.2.0`](https://redirect.github.com/pyupio/safety/blob/HEAD/CHANGELOG.md#320---2024-05-01)
[Compare
Source](https://redirect.github.com/pyupio/safety/compare/3.1.0...3.2.0)
- feat: add SAFETY_DB_DIR env var to the scan command
([#​523](https://redirect.github.com/pyupio/safety/issues/523))
- fix: update pyinstaller target
([#​522](https://redirect.github.com/pyupio/safety/issues/522))
- docs: added note on hiring and added careers page link
([#​510](https://redirect.github.com/pyupio/safety/issues/510))
###
[`v3.1.0`](https://redirect.github.com/pyupio/safety/blob/HEAD/CHANGELOG.md#310---2024-03-25)
[Compare
Source](https://redirect.github.com/pyupio/safety/compare/3.0.1...3.1.0)
- fix: ensure compatibility with Pydantic version 2.0
([#​509](https://redirect.github.com/pyupio/safety/issues/509))
- feat: introduce --headless flag to enable an alternative login
mechanism that bypasses the need for a local web server.
([#​508](https://redirect.github.com/pyupio/safety/issues/508))
###
[`v3.0.1`](https://redirect.github.com/pyupio/safety/blob/HEAD/CHANGELOG.md#301---2024-01-19)
[Compare
Source](https://redirect.github.com/pyupio/safety/compare/3.0.0...3.0.1)
- fix: add back the license legacy cmd
([#​498](https://redirect.github.com/pyupio/safety/issues/498))
- perf: unpin authlib and remove jwt
###
[`v3.0.0`](https://redirect.github.com/pyupio/safety/blob/HEAD/CHANGELOG.md#300---2024-01-17)
[Compare
Source](https://redirect.github.com/pyupio/safety/compare/2.4.0b2...3.0.0)
##### Safety 3.0.0 major version release!
- Safety 3.0.0 is a significant update to Safety CLI from 2.x versions,
including enhancements to core features, new capabilities, and breaking
changes from 2.x.
- See our [Blog article announcing Safety CLI
3](https://safetycli.com/research/safety-cli-3-vulnerability-scanning-for-secure-python-development)
for more details on Safety 3 and these changes
- See [Migrating from Safety 2.x to Safety CLI
3](https://docs.safetycli.com/safety-docs/safety-cli-3/migrating-from-safety-cli-2.x-to-safety-cli-3.x)
for notes and steps to migrating from Safety 2 to Safety 3
##### Main updates
- Added scan command, which scans a project’s directory for all Python
dependencies and includes many improvements over the `check` command,
including automatic Python project scanning, native support for Poetry
and Pipenv files, Python virtual environment folders, and more granular
configuration options.
- Added auth commands, enabling new browser-based authentication of
Safety CLI.
- An updated safety policy file schema to support new scan and
system-scan commands. This policy file schema is a breaking change from
the policy schema used for `safety check`. To migrate a Safety 2.x
policy, see [Migrating from Safety 2.x to Safety CLI
3](https://docs.safetycli.com/safety-docs/safety-cli-3/migrating-from-safety-cli-2.x-to-safety-cli-3.x).
- Updated screen output to modern interactive interface, with new help
interfaces.
- Updated to new JSON output structure to support new scan command,
other ecosystems, and other security findings.
- Added a supporting [safety-schemas project
dependency](https://pypi.org/project/safety-schemas/), also published
and maintained by Safety, which defines Safety vulnerability database
file, Safety CLI policy file, and Safety CLI JSON output schemas as
pydantic models, formalizing these into testable and versioned schemas.
##### New scan command:
- New scan command: scans a Python project directory for Python
dependencies and security vulnerabilities. Safety scan replaces `safety
check` with a more powerful and easier to use command. The scan command:
- Finds and scans Python dependency files and virtual environments
inside the target directory without needing to specify file or
environment locations.
- Adds native scanning and reporting for Poetry and Pipenv manifest
files, and Python virtual environment folders.
- Adds configuration of scanning rules to;
- exclude files and folders from the scan using Unix shell-style
wildcards only
- Include files to be scanned
- Max folder depth setting
- Reporting configuration rules
- Reporting rules defining which types and specific vulnerabilities to
include or ignore stay the same as safety 2.x, although now in a
slightly different structure.
- Failing rules
- Adds ability to configure rules for when safety should return a
non-zero (failing) exit code, which can be different from reporting
rules under the `report` field.
- Auto-updating rules
- Adds ability to easily update insecure package versions in pip
requirements files.
##### Other new commands:
- Added auth command: manages Safety CLI’s authentication in development
environments, allowing easy authentication via the browser.
- auth login - adds ability to authenticate safety cli via the browser
- auth register - adds ability to register for a Safety account via the
CLI, and get scanning within minutes
- auth status -
- auth logout -
- `safety check` command can still be used with the API key --key
argument, and scan and system-scan commands should also be
- Added configure command: configures safety cli using a config.ini
file, either saved to the user settings or system settings. This can be
used to configure safety’s authentication methods and global proxy
details.
- Added system-scan command (beta): Adds the system-scan command, which
scans a machine for Python files and environments, reporting these to
screen output. system-scan is an experimental beta feature that can scan
an entire drive or machine for Python dependency files and Python
virtual environments, reporting on packages found and their associated
security vulnerabilities.
- Added check-updates command: Check for version updates to Safety CLI,
and supports screen and JSON format outputs. Can be used in
organizations to test and rollout new version updates as recommended by
Safety Cybersecurity.
##### New policy file schema for scan and system-scan commands
- New policy file schema to support safety scan and safety system-scan.
Adds scanning-settings root property, which contains settings to
configure rules and settings for how safety traverses the directory and
subdirectories being scanned, including “exclude” rules, “include”
rules, the max directory depth to scan and which root directories safety
system-scan should start from.
- Adds report root property, which defi
</details>
---
### Configuration
📅 **Schedule**: Branch creation - "on the 2nd and 4th day instance on
sunday after 9pm" in timezone America/New_York, 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](https://redirect.github.com/renovatebot/renovate/discussions) if
that's undesired.
---
- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check
this box
---
This PR was generated by [Mend Renovate](https://mend.io/renovate/).
View the [repository job
log](https://developer.mend.io/github/HHS/simpler-grants-gov).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy40NDAuNyIsInVwZGF0ZWRJblZlciI6IjM4LjgwLjAiLCJ0YXJnZXRCcmFuY2giOiJtYWluIiwibGFiZWxzIjpbImRlcGVuZGVuY2llcyJdfQ==-->
---------
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: Michael Chouinard <chouinar6@gmail.com>- Loading branch information
1 parent
7a43951
commit 434016a