565: add census_tract_adr_type and census_tract_number validations except invalid_geoid

…flag

Task 536:

fix pricing_var_index_name, action_taken and ct_loan_term data

…_tract_ids

Features/554 two phase validation POC

Co-authored-by: Aldrian Harjati <[email protected]>

Co-authored-by: Aldrian Harjati <[email protected]>

Co-authored-by: Aldrian Harjati <[email protected]>

fix pricing_mca_addcost and naics description

add census_tract_number id validation and  function to parse/validate tract ids

add uid format and length validations

Co-authored-by: Aldrian Harjati <[email protected]>

* add uid duplicates_in_dataset validation

* changed check function to return series

* update 2-phase schema

* add count_limit parameter

* add more unit tests

* removed a duplicated unit test

---------

Co-authored-by: Aldrian Harjati <[email protected]>

* Created a new branch to resolve merge conflicts

* Addressed Le's and Aldrian's comments. In the meantime, working on black formatting.

* Modified the comments to reflect the changes

* Fixed formatting issues

* Fixed data for po_1_ethnicity

* Fixed data

* Fixed GoodData file issues

* Changed format

* Modified comments

* Addressed the comments

* Addressed the comment for line 981 for schema.py

* Fixed format in phase_validations.py

* cleaned up the comments

* Removed the fucntions that the new function "has_valid_fiedlset_pair" is replacing: _is_fieldset_equal_to_helper, _is_fieldset_not_equal_to_helper,is_fieldset_equal_to, is_fieldset_not_equal_to. Also, removed the unit tests for thses.

* Fixing merge conflict

---------

Co-authored-by: Nargis Sultani <[email protected]>

…ed schema; modified unit test, removed denial_reasons_conditional_enum_value function and its unit tests

Fixed data in goodfile; modified has_valid_enum_pair function; modifi…

* Ticket 11, added invalid_uid_lei validation and unit tests

* changed function name

* addressed Hans suggestions to have lei passed through command line and have a way to skip this validation

* addressed the comments

* modified comments

* addressed the comment and modified the phase validation

* modified function name

* fixed typo

* addressed the comment

* Addressed the comment

---------

Co-authored-by: Nargis Sultani <[email protected]>

…idation_scheme

Switched to two phase validation and deleted schema.py

* use `python-coverage-comment` to run github actions/checks
---------

Co-authored-by: Aldrian Harjati <[email protected]>

Task 33, adding validation id

Update repo to use poetry (ticket #41)

Changes:
- Removed requirements.txt
- Removed setup.cfg
- Updated devcontainer's dockerfile to use poetry (instead of pip)
- Created pyproject containing requirements and setup.cfg content
- Created poetry.lock
- Updated few comments in phase_validations and schema_template (that
were not formatted properly).
- Updated github-actions tests to use poetry (instead of pip)

Tests:
- Validate that we still able to execute python through VSCode
- Validate that we still able to run Tests through VSCode
- Passed linters
- Passed unit-tests

---------

Co-authored-by: Aldrian Harjati <[email protected]>

Co-authored-by: Nargis Sultani <[email protected]>

Currently, we have to install black-formatter manually after
reloading/rebuilding dev-container, and occasionally, we forget to
re-install this extension that caused formatting issue.

This update will install black-formatter automatically when
rebuilding/creating dev-container.

Co-authored-by: Aldrian Harjati <[email protected]>

closed #48 

Update:
- update deprecated pandas function to fix warning.  
- update global_data function to make it easier for unit testing.
- add global_data unit tests

Co-authored-by: Aldrian Harjati <[email protected]>

…poetry files (#53)

Fixed bug where user cannot setup dev-container in VS code
Issue
docker cannot get pyproject and poetry files because incorrect path
Fix:
Removing the parent path because we already defined parent path in
devcontainer's build context

Test:
Successfully load devcontainer in my and nargis laptop

---------

Co-authored-by: Aldrian Harjati <[email protected]>

Co-authored-by: Nargis Sultani <[email protected]>

Add code coverage badge in readme to display current coverage status
Link to this readme:
https://github.com/cfpb/regtech-data-validator/tree/features/add_code_coverage_status#coverage

Co-authored-by: Aldrian Harjati <[email protected]>

closes #55 

Update README with updates:
- Add phase 1 and phase 2 reference
- Add quick notes on new files
- Update test instruction with LEI update

---------

Co-authored-by: Aldrian Harjati <[email protected]>
Co-authored-by: Hans Keeler <[email protected]>

Closes #52 

I misunderstood the requirements first. I thought we had to create tests
to make sure the GoodFile had the correct data for each field. I
understood the requirements later.

---------

Co-authored-by: Nargis Sultani <[email protected]>

update readme:
- Change focus to use Poetry
- Add more details on POETRY steps (installation, developments and
tests)
- Add more details on VScode development
- Add contact/help information

---------

Co-authored-by: Aldrian Harjati <[email protected]>

…#60)

Grab bag of tune-up in prep for open-sourcing this repo.

1. Restructure repo to be more compliant with modern Python projects.
    1. Move `tests` out to top-level directory.
    2. Rename `src/validator` to `regtech_data_validator`.
2. Consolidate external datasource code and data to `data` dir.
    1. Move `config.py` settings into their respective scripts, and file
        paths are now passed in as CLI args instead.
3. Move processed CSV files into the project itself. This allows for
    simpler data lookups via package name via `importlib.resources`.
    This allowed the removal of the `ROOT_PATH` Python path logic in all of
    the `__init__.py`s.
4. Refactor `global_data.py` to load data only once where module is
    first imported.
5. Refactor `SBLCheck`'s
    1. `warning: bool` for a more explicit `severity`, backed by an enum
        that only allows `ERROR` and `WARNING`.
        1. Several of the warning-level validations were not setting
            `warning=True`, and were thus defaulting to `False`. This will prevent
            that. I also fixed all these instances.
        2. Removes the need for translation to `severity` when building JSON
            output.
    2. Use explicit args in the constructor, and pass all shared args on to
        parent class. This removes the need for the arg `name`/`id` error handling. 
6. Switch CLI output from Python dict to JSON.
7. Rollback `black` version used in linting Action due to bug in latest version.
    -  psf/black#3953

**Note:** Some of the files that I both moved _and_ changed seem to now
show as having deleted the old file and created a new one. I'm not sure
why it's doing this. I did the moves and changes in separate commits,
which usually prevents this, but doesn't seem to be the case here.
Perhaps there's just so much change in some that git considers it a
whole new file? 🤷 It's kind of annoying, especially if it results in
losing git history for those files.

### Replace `main.py` to [Typer](https://typer.tiangolo.com/) CLI app

The CLI setup in `main.py` is pretty primitive, and is really geared
towards _us_, developers on this project. I would like to create a
utility that outside technical users can use to test their files against
our validation logic. To get there without having to reinvent many
wheels, we need an actual CLI framework. That's where
[Typer](https://typer.tiangolo.com/) comes in.

Typer is a wrapper around
[Click](https://click.palletsprojects.com/en/8.1.x/), written by the
same dev as FastAPI, so it follows many of the same patterns as we're
used to there, such as leaning into Python's `typing` and
[Pydantic](https://docs.pydantic.dev/latest/) for example.


### Return validation results as Pandas `DataFrame` instead of vanilla
`dict`

I also wanted to support multiple output formats; at least json, csv,
and default to a human-readable table. And while we _could_ do that with
a `dict`, it's much easier to work with `DataFrame`s as they're already
tabular in nature and have a ton of transform functionality built-in.
So, I have also refactored the `validate` function to return a Panda's
`DataFrame` instead of a vanilla `dict`. This made it much easier to
output validation data in multiple formats.

Along with this, I did a fair bit of refactoring of that surrounding
code, breaking up the big monolith function into smaller testable
functions.

### `cfpb-val` script

To simply using the CLI, I've added a shortcut script so you don't have
to call the full path to the Python script. In it's current form, you
can now call just...

    cfpb-val --help

...instead of...

    python regtech_data_validator/cli.py --help 

#### Better script name?

I'm not in love with `cfpb-val`. I started off with `cfpb-comply`, but I
didn't love that either. I'm looking for something that's short, but
also very clear that it's CFPB-related, and having to do with this
project. `cfpb-rdv`?

### Lots of `README.md` love

I've reworked the `README.md` quite a bit, focusing on users coming to
this repo for the first time, and trying to get the CLI to work. This
includes pushing the Poetry-based install up to the top and simplifying
it, slimming and pushing down development-related setup, and adding
details about how to use the CLI itself.

See:
https://github.com/cfpb/regtech-data-validator/blob/add-typer-cli/README.md

### Refactor `lei` arg to more generic `context`

In attempt to future-proof this a bit, I've added a multi-value
`context` arg to the CLI, which allows you to pass arbitrary
`<key>=<value>` pairs, `lei` being the only key that's current used for
anything.

### Other tidbits I found along the way

- Removed deprecated `python.formatting.provider` VS Code configuration
- Removes no longer used `Makefile`
- Fixes several validations that had incorrect IDs, severities, or were
in the wrong phase

---------

Co-authored-by: lchen-2101 <[email protected]>

closes #66

closes #61 
update 
- update the principal owner validation IDs to match new ones
- update devcontainer docker file to run pip install separately.
(background: devcontainer was failing with old setup)

---------

Co-authored-by: Aldrian Harjati <[email protected]>
Co-authored-by: Nargis Sultani <[email protected]>

closes #71

These are all changes to make our python code consistent with the CVS
located at
https://raw.githubusercontent.com/cfpb/sbl-content/main/fig-files/validation-spec/2024-validations.csv

This goes hand in hand with issue #65 

Of note is the addition of W0680, which checks the Census GEO id against
the census CSV.

Majority of the changes involved missing spaces, copy/paste errors, etc.

The updates to this file are still in progress as there are 4 errors
(E0940, E1120, E1300, E1480) that have descriptions that Chynna and
Shomari are looking into to verify if the CSV is correct. So this PR is
simply to get a head start.

…tionscsv (#69)

This adds a pytest (test_csv_differences.py) to validate our python code
against the CSV located at
https://raw.githubusercontent.com/cfpb/sbl-content/main/fig-files/validation-spec/2024-validations.csv

This will compare error/warning codes (making sure neither the code nor
csv have codes the other doesn't), the type (error or warning) and the
description.

Special note is taken of E2014 and E2015 due to formatting in the CSV.
In the near future when the frontend is ready to start displaying
error/warning descriptions, discussions will be had to figure out how we
want to display the more complicated descriptions and what sort of
formatting the backend should have. Right now, we preserve as much of
the formatting as we can but the pytest will also strip all of this off
for these two errors (or any others added to the remove_formatting list)
and compare just character data. In general, we do NOT want to do this
because several strings in our python code were missing spaces and other
standard grammatical formatting, and stripping that off would have
caused the test to improperly accept that description.

This story is being worked in conjunction with #68 which is being used
to update the phase_validations.py for other discrepancies found during
testing. It is being routinely merged into this branch to properly run
the pytest.

Closes #73 

README updated with test_csv_to_code_differences.py

Add `dependabot.yml` with GitHub Actions and PIP checks. According to
the docs, the `pip` value covers Poetry as well.

SEE:
https://docs.github.com/en/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#package-ecosystem

PR #76 currently cannot be merged because the CodeQL check is blocking
it.


https://github.com/cfpb/regtech-data-validator/pull/76/checks?check_run_id=20738517606

I don't fully understand this error message, but I'm hopeful switching
to the code-based configuration of the CodeQL Action will help with
debugging.

Bumps [black](https://github.com/psf/black) from 23.10.1 to 24.1.1.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/psf/black/releases">black's
releases</a>.</em></p>
<blockquote>
<h2>24.1.1</h2>
<p>Bugfix release to fix a bug that made Black unusable on certain file
systems
with strict limits on path length.</p>
<h3>Preview style</h3>
<ul>
<li>Consistently add trailing comma on typed parameters (<a
href="https://redirect.github.com/psf/black/issues/4164">#4164</a>)</li>
</ul>
<h3>Configuration</h3>
<ul>
<li>Shorten the length of the name of the cache file to fix crashes on
file systems that
do not support long paths (<a
href="https://redirect.github.com/psf/black/issues/4176">#4176</a>)</li>
</ul>
<h2>24.1.0</h2>
<h3>Highlights</h3>
<p>This release introduces the new 2024 stable style (<a
href="https://redirect.github.com/psf/black/issues/4106">#4106</a>),
stabilizing the following
changes:</p>
<ul>
<li>Add parentheses around <code>if</code>-<code>else</code> expressions
(<a
href="https://redirect.github.com/psf/black/issues/2278">#2278</a>)</li>
<li>Dummy class and function implementations consisting only of
<code>...</code> are formatted more
compactly (<a
href="https://redirect.github.com/psf/black/issues/3796">#3796</a>)</li>
<li>If an assignment statement is too long, we now prefer splitting on
the right-hand side
(<a
href="https://redirect.github.com/psf/black/issues/3368">#3368</a>)</li>
<li>Hex codes in Unicode escape sequences are now standardized to
lowercase (<a
href="https://redirect.github.com/psf/black/issues/2916">#2916</a>)</li>
<li>Allow empty first lines at the beginning of most blocks (<a
href="https://redirect.github.com/psf/black/issues/3967">#3967</a>, <a
href="https://redirect.github.com/psf/black/issues/4061">#4061</a>)</li>
<li>Add parentheses around long type annotations (<a
href="https://redirect.github.com/psf/black/issues/3899">#3899</a>)</li>
<li>Enforce newline after module docstrings (<a
href="https://redirect.github.com/psf/black/issues/3932">#3932</a>, <a
href="https://redirect.github.com/psf/black/issues/4028">#4028</a>)</li>
<li>Fix incorrect magic trailing comma handling in return types (<a
href="https://redirect.github.com/psf/black/issues/3916">#3916</a>)</li>
<li>Remove blank lines before class docstrings (<a
href="https://redirect.github.com/psf/black/issues/3692">#3692</a>)</li>
<li>Wrap multiple context managers in parentheses if combined in a
single <code>with</code> statement
(<a
href="https://redirect.github.com/psf/black/issues/3489">#3489</a>)</li>
<li>Fix bug in line length calculations for power operations (<a
href="https://redirect.github.com/psf/black/issues/3942">#3942</a>)</li>
<li>Add trailing commas to collection literals even if there's a comment
after the last
entry (<a
href="https://redirect.github.com/psf/black/issues/3393">#3393</a>)</li>
<li>When using <code>--skip-magic-trailing-comma</code> or
<code>-C</code>, trailing commas are stripped from
subscript expressions with more than 1 element (<a
href="https://redirect.github.com/psf/black/issues/3209">#3209</a>)</li>
<li>Add extra blank lines in stubs in a few cases (<a
href="https://redirect.github.com/psf/black/issues/3564">#3564</a>, <a
href="https://redirect.github.com/psf/black/issues/3862">#3862</a>)</li>
<li>Accept raw strings as docstrings (<a
href="https://redirect.github.com/psf/black/issues/3947">#3947</a>)</li>
<li>Split long lines in case blocks (<a
href="https://redirect.github.com/psf/black/issues/4024">#4024</a>)</li>
<li>Stop removing spaces from walrus operators within subscripts (<a
href="https://redirect.github.com/psf/black/issues/3823">#3823</a>)</li>
<li>Fix incorrect formatting of certain async statements (<a
href="https://redirect.github.com/psf/black/issues/3609">#3609</a>)</li>
<li>Allow combining <code># fmt: skip</code> with other comments (<a
href="https://redirect.github.com/psf/black/issues/3959">#3959</a>)</li>
</ul>
<p>There are already a few improvements in the <code>--preview</code>
style, which are slated for the
2025 stable style. Try them out and
<a href="https://github.com/psf/black/issues">share your feedback</a>.
In the past, the preview
style has included some features that we were not able to stabilize.
This year, we're</p>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a
href="https://github.com/psf/black/blob/main/CHANGES.md">black's
changelog</a>.</em></p>
<blockquote>
<h2>24.1.1</h2>
<p>Bugfix release to fix a bug that made Black unusable on certain file
systems with strict
limits on path length.</p>
<h3>Preview style</h3>
<ul>
<li>Consistently add trailing comma on typed parameters (<a
href="https://redirect.github.com/psf/black/issues/4164">#4164</a>)</li>
</ul>
<h3>Configuration</h3>
<ul>
<li>Shorten the length of the name of the cache file to fix crashes on
file systems that
do not support long paths (<a
href="https://redirect.github.com/psf/black/issues/4176">#4176</a>)</li>
</ul>
<h2>24.1.0</h2>
<h3>Highlights</h3>
<p>This release introduces the new 2024 stable style (<a
href="https://redirect.github.com/psf/black/issues/4106">#4106</a>),
stabilizing the following
changes:</p>
<ul>
<li>Add parentheses around <code>if</code>-<code>else</code> expressions
(<a
href="https://redirect.github.com/psf/black/issues/2278">#2278</a>)</li>
<li>Dummy class and function implementations consisting only of
<code>...</code> are formatted more
compactly (<a
href="https://redirect.github.com/psf/black/issues/3796">#3796</a>)</li>
<li>If an assignment statement is too long, we now prefer splitting on
the right-hand side
(<a
href="https://redirect.github.com/psf/black/issues/3368">#3368</a>)</li>
<li>Hex codes in Unicode escape sequences are now standardized to
lowercase (<a
href="https://redirect.github.com/psf/black/issues/2916">#2916</a>)</li>
<li>Allow empty first lines at the beginning of most blocks (<a
href="https://redirect.github.com/psf/black/issues/3967">#3967</a>, <a
href="https://redirect.github.com/psf/black/issues/4061">#4061</a>)</li>
<li>Add parentheses around long type annotations (<a
href="https://redirect.github.com/psf/black/issues/3899">#3899</a>)</li>
<li>Enforce newline after module docstrings (<a
href="https://redirect.github.com/psf/black/issues/3932">#3932</a>, <a
href="https://redirect.github.com/psf/black/issues/4028">#4028</a>)</li>
<li>Fix incorrect magic trailing comma handling in return types (<a
href="https://redirect.github.com/psf/black/issues/3916">#3916</a>)</li>
<li>Remove blank lines before class docstrings (<a
href="https://redirect.github.com/psf/black/issues/3692">#3692</a>)</li>
<li>Wrap multiple context managers in parentheses if combined in a
single <code>with</code> statement
(<a
href="https://redirect.github.com/psf/black/issues/3489">#3489</a>)</li>
<li>Fix bug in line length calculations for power operations (<a
href="https://redirect.github.com/psf/black/issues/3942">#3942</a>)</li>
<li>Add trailing commas to collection literals even if there's a comment
after the last
entry (<a
href="https://redirect.github.com/psf/black/issues/3393">#3393</a>)</li>
<li>When using <code>--skip-magic-trailing-comma</code> or
<code>-C</code>, trailing commas are stripped from
subscript expressions with more than 1 element (<a
href="https://redirect.github.com/psf/black/issues/3209">#3209</a>)</li>
<li>Add extra blank lines in stubs in a few cases (<a
href="https://redirect.github.com/psf/black/issues/3564">#3564</a>, <a
href="https://redirect.github.com/psf/black/issues/3862">#3862</a>)</li>
<li>Accept raw strings as docstrings (<a
href="https://redirect.github.com/psf/black/issues/3947">#3947</a>)</li>
<li>Split long lines in case blocks (<a
href="https://redirect.github.com/psf/black/issues/4024">#4024</a>)</li>
<li>Stop removing spaces from walrus operators within subscripts (<a
href="https://redirect.github.com/psf/black/issues/3823">#3823</a>)</li>
<li>Fix incorrect formatting of certain async statements (<a
href="https://redirect.github.com/psf/black/issues/3609">#3609</a>)</li>
<li>Allow combining <code># fmt: skip</code> with other comments (<a
href="https://redirect.github.com/psf/black/issues/3959">#3959</a>)</li>
</ul>
<p>There are already a few improvements in the <code>--preview</code>
style, which are slated for the
2025 stable style. Try them out and
<a href="https://github.com/psf/black/issues">share your feedback</a>.
In the past, the preview
style has included some features that we were not able to stabilize.
This year, we're</p>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/psf/black/commit/e026c93888f91a47a9c9f4e029f3eb07d96375e6"><code>e026c93</code></a>
Prepare release 24.1.1 (<a
href="https://redirect.github.com/psf/black/issues/4186">#4186</a>)</li>
<li><a
href="https://github.com/psf/black/commit/79fc1158a98281dac798feb14b8fddb4051e4a42"><code>79fc115</code></a>
chore: ignore node_modules (produced by a pre-commit check) (<a
href="https://redirect.github.com/psf/black/issues/4184">#4184</a>)</li>
<li><a
href="https://github.com/psf/black/commit/8bf04549ffd276a1bad6eb110e66e6557ee630d9"><code>8bf0454</code></a>
Consistently add trailing comma on typed parameters (<a
href="https://redirect.github.com/psf/black/issues/4164">#4164</a>)</li>
<li><a
href="https://github.com/psf/black/commit/1607e9ab20ad550cf940482d0d361ca31fc03189"><code>1607e9a</code></a>
Fix missing space in option description (<a
href="https://redirect.github.com/psf/black/issues/4182">#4182</a>)</li>
<li><a
href="https://github.com/psf/black/commit/ed770ba4dd50c419148a0fca2b43937a7447e1f9"><code>ed770ba</code></a>
Fix cache file length (<a
href="https://redirect.github.com/psf/black/issues/4176">#4176</a>)</li>
<li><a
href="https://github.com/psf/black/commit/659c29a41c7c686687aef21f57b95bcfa236b03b"><code>659c29a</code></a>
New changelog</li>
<li><a
href="https://github.com/psf/black/commit/0e6e46b9eb45f5a22062fe84c2c2ff46bd0d738e"><code>0e6e46b</code></a>
Prepare release 24.1.0 (<a
href="https://redirect.github.com/psf/black/issues/4170">#4170</a>)</li>
<li><a
href="https://github.com/psf/black/commit/4f47cac1925a2232892ceae438e2c62f81517714"><code>4f47cac</code></a>
Add --unstable flag (<a
href="https://redirect.github.com/psf/black/issues/4096">#4096</a>)</li>
<li><a
href="https://github.com/psf/black/commit/bccec8adfbed2bbc24c0859e8758d5e7809d42b7"><code>bccec8a</code></a>
Show warning on invalid toml configuration (<a
href="https://redirect.github.com/psf/black/issues/4165">#4165</a>)</li>
<li><a
href="https://github.com/psf/black/commit/7d789469ed947022f183962b823f5862511272ac"><code>7d78946</code></a>
Describe 2024 module docstring more accurately (<a
href="https://redirect.github.com/psf/black/issues/4168">#4168</a>)</li>
<li>Additional commits viewable in <a
href="https://github.com/psf/black/compare/23.10.1...24.1.1">compare
view</a></li>
</ul>
</details>
<br />


[![Dependabot compatibility
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=black&package-manager=pip&previous-version=23.10.1&new-version=24.1.1)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)

Dependabot will resolve any conflicts with this PR as long as you don't
alter it yourself. You can also trigger a rebase manually by commenting
`@dependabot rebase`.

[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits
that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after
your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge
and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating
it. You can achieve the same result by closing it manually
- `@dependabot show <dependency name> ignore conditions` will show all
of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will close this PR and stop
Dependabot creating any more for this major version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop
Dependabot creating any more for this minor version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop
Dependabot creating any more for this dependency (unless you reopen the
PR or upgrade to it yourself)


</details>

---------

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Hans Keeler <[email protected]>

Closes #89 

Added versions to the linter actions. Since the pyproject.toml specifies
distinct versions for each (instead of say ^24.1.0), I put the version
equal to what is in the toml. Note that, as in the other stories
referenced, the black linter supports the concept of capability
versions. We're just not using itwith:
          version: 0.0.278here.

…#95)

Small changes to the docs, updating the `cfpb-val` examples' output to
match current functionality, and tweaked some other areas for clarity.

Bumps [pytest](https://github.com/pytest-dev/pytest) from 8.0.0 to
8.0.1.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/pytest-dev/pytest/releases">pytest's
releases</a>.</em></p>
<blockquote>
<h2>8.0.1</h2>
<h1>pytest 8.0.1 (2024-02-16)</h1>
<h2>Bug Fixes</h2>
<ul>
<li><a
href="https://redirect.github.com/pytest-dev/pytest/issues/11875">#11875</a>:
Correctly handle errors from
<code>getpass.getuser</code>{.interpreted-text role=&quot;func&quot;} in
Python 3.13.</li>
<li><a
href="https://redirect.github.com/pytest-dev/pytest/issues/11879">#11879</a>:
Fix an edge case where <code>ExceptionInfo._stringify_exception</code>
could crash <code>pytest.raises</code>{.interpreted-text
role=&quot;func&quot;}.</li>
<li><a
href="https://redirect.github.com/pytest-dev/pytest/issues/11906">#11906</a>:
Fix regression with <code>pytest.warns</code>{.interpreted-text
role=&quot;func&quot;} using custom warning subclasses which have more
than one parameter in their [__init__]{.title-ref}.</li>
<li><a
href="https://redirect.github.com/pytest-dev/pytest/issues/11907">#11907</a>:
Fix a regression in pytest 8.0.0 whereby calling
<code>pytest.skip</code>{.interpreted-text role=&quot;func&quot;} and
similar control-flow exceptions within a
<code>pytest.warns()</code>{.interpreted-text role=&quot;func&quot;}
block would get suppressed instead of propagating.</li>
<li><a
href="https://redirect.github.com/pytest-dev/pytest/issues/11929">#11929</a>:
Fix a regression in pytest 8.0.0 whereby autouse fixtures defined in a
module get ignored by the doctests in the module.</li>
<li><a
href="https://redirect.github.com/pytest-dev/pytest/issues/11937">#11937</a>:
Fix a regression in pytest 8.0.0 whereby items would be collected in
reverse order in some circumstances.</li>
</ul>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/pytest-dev/pytest/commit/d7d320a15a1f8dae909e0aa71f20ab5daeaa42d3"><code>d7d320a</code></a>
Prepare release version 8.0.1</li>
<li><a
href="https://github.com/pytest-dev/pytest/commit/93699166dc3d90676b126d2b1615fbd41cf0be4d"><code>9369916</code></a>
Merge pull request <a
href="https://redirect.github.com/pytest-dev/pytest/issues/11992">#11992</a>
from bluetech/backport-11991</li>
<li><a
href="https://github.com/pytest-dev/pytest/commit/a232abd56cd7ddc0d6dbeefd851c538ec547ab06"><code>a232abd</code></a>
[8.0.x] recwarn: fix pytest.warns handling of Warnings with multiple
arguments</li>
<li><a
href="https://github.com/pytest-dev/pytest/commit/92203d2b78135446510ec70d46452937effcb1d9"><code>92203d2</code></a>
Merge pull request <a
href="https://redirect.github.com/pytest-dev/pytest/issues/11990">#11990</a>
from bluetech/backport-11920</li>
<li><a
href="https://github.com/pytest-dev/pytest/commit/f1aa9226ac5b1962fdad442652765d5e589c7137"><code>f1aa922</code></a>
[8.0.x] recwarn: let base exceptions propagate through
<code>pytest.warns</code> again</li>
<li><a
href="https://github.com/pytest-dev/pytest/commit/d86d08156337b40ad0cf6e4bfe38ecfa0e5eb5bd"><code>d86d081</code></a>
[8.0.x] Added <code>logot</code> to the plugin list (<a
href="https://redirect.github.com/pytest-dev/pytest/issues/11977">#11977</a>)</li>
<li><a
href="https://github.com/pytest-dev/pytest/commit/c554c3d200747f9f56b4054619ba4fb6f8910bb5"><code>c554c3d</code></a>
Merge pull request <a
href="https://redirect.github.com/pytest-dev/pytest/issues/11968">#11968</a>
from pytest-dev/backport-11957-to-8.0.x</li>
<li><a
href="https://github.com/pytest-dev/pytest/commit/a6851e3459159f94387debf0b357c9b6481a2f48"><code>a6851e3</code></a>
[8.0.x] main: fix reversed collection order in Session</li>
<li><a
href="https://github.com/pytest-dev/pytest/commit/e6f6be3bc9e876f1853fdea68ec49cfc1c4c246d"><code>e6f6be3</code></a>
[8.0.x] Improve error message when using <a
href="https://github.com/pytest"><code>@​pytest</code></a>.fixture twice
(<a
href="https://redirect.github.com/pytest-dev/pytest/issues/11958">#11958</a>)</li>
<li><a
href="https://github.com/pytest-dev/pytest/commit/23b91d12de9bcbd0ce965bebefcbcc53a588b438"><code>23b91d1</code></a>
[8.0.x] Merge pull request <a
href="https://redirect.github.com/pytest-dev/pytest/issues/11941">#11941</a>
from bluetech/doctest-parsefactories (<a
href="https://redirect.github.com/pytest-dev/pytest/issues/11948">#11948</a>)</li>
<li>Additional commits viewable in <a
href="https://github.com/pytest-dev/pytest/compare/8.0.0...8.0.1">compare
view</a></li>
</ul>
</details>
<br />


[![Dependabot compatibility
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=pytest&package-manager=pip&previous-version=8.0.0&new-version=8.0.1)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)

Dependabot will resolve any conflicts with this PR as long as you don't
alter it yourself. You can also trigger a rebase manually by commenting
`@dependabot rebase`.

[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits
that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after
your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge
and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating
it. You can achieve the same result by closing it manually
- `@dependabot show <dependency name> ignore conditions` will show all
of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will close this PR and stop
Dependabot creating any more for this major version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop
Dependabot creating any more for this minor version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop
Dependabot creating any more for this dependency (unless you reopen the
PR or upgrade to it yourself)


</details>

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

Bumps [black](https://github.com/psf/black) from 24.1.1 to 24.2.0.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/psf/black/releases">black's
releases</a>.</em></p>
<blockquote>
<h2>24.2.0</h2>
<h3>Stable style</h3>
<ul>
<li>Fixed a bug where comments where mistakenly removed along with
redundant parentheses
(<a
href="https://redirect.github.com/psf/black/issues/4218">#4218</a>)</li>
</ul>
<h3>Preview style</h3>
<ul>
<li>Move the <code>hug_parens_with_braces_and_square_brackets</code>
feature to the unstable style
due to an outstanding crash and proposed formatting tweaks (<a
href="https://redirect.github.com/psf/black/issues/4198">#4198</a>)</li>
<li>Fixed a bug where base expressions caused inconsistent formatting of
** in tenary
expression (<a
href="https://redirect.github.com/psf/black/issues/4154">#4154</a>)</li>
<li>Checking for newline before adding one on docstring that is almost
at the line limit
(<a
href="https://redirect.github.com/psf/black/issues/4185">#4185</a>)</li>
<li>Remove redundant parentheses in <code>case</code> statement
<code>if</code> guards (<a
href="https://redirect.github.com/psf/black/issues/4214">#4214</a>).</li>
</ul>
<h3>Configuration</h3>
<ul>
<li>Fix issue where <em>Black</em> would ignore input files in the
presence of symlinks (<a
href="https://redirect.github.com/psf/black/issues/4222">#4222</a>)</li>
<li><em>Black</em> now ignores <code>pyproject.toml</code> that is
missing a <code>tool.black</code> section when
discovering project root and configuration. Since <em>Black</em>
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 <code>[tool.black]</code> to the previously
discovered <code>pyproject.toml</code>
(<a
href="https://redirect.github.com/psf/black/issues/4204">#4204</a>)</li>
</ul>
<h3>Output</h3>
<ul>
<li>Black will swallow any <code>SyntaxWarning</code>s or
<code>DeprecationWarning</code>s produced by the <code>ast</code>
module when performing equivalence checks (<a
href="https://redirect.github.com/psf/black/issues/4189">#4189</a>)</li>
</ul>
<h3>Integrations</h3>
<ul>
<li>Add a JSONSchema and provide a validate-pyproject entry-point (<a
href="https://redirect.github.com/psf/black/issues/4181">#4181</a>)</li>
</ul>
</blockquote>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a
href="https://github.com/psf/black/blob/main/CHANGES.md">black's
changelog</a>.</em></p>
<blockquote>
<h2>24.2.0</h2>
<h3>Stable style</h3>
<ul>
<li>Fixed a bug where comments where mistakenly removed along with
redundant parentheses
(<a
href="https://redirect.github.com/psf/black/issues/4218">#4218</a>)</li>
</ul>
<h3>Preview style</h3>
<ul>
<li>Move the <code>hug_parens_with_braces_and_square_brackets</code>
feature to the unstable style
due to an outstanding crash and proposed formatting tweaks (<a
href="https://redirect.github.com/psf/black/issues/4198">#4198</a>)</li>
<li>Fixed a bug where base expressions caused inconsistent formatting of
** in tenary
expression (<a
href="https://redirect.github.com/psf/black/issues/4154">#4154</a>)</li>
<li>Checking for newline before adding one on docstring that is almost
at the line limit
(<a
href="https://redirect.github.com/psf/black/issues/4185">#4185</a>)</li>
<li>Remove redundant parentheses in <code>case</code> statement
<code>if</code> guards (<a
href="https://redirect.github.com/psf/black/issues/4214">#4214</a>).</li>
</ul>
<h3>Configuration</h3>
<ul>
<li>Fix issue where <em>Black</em> would ignore input files in the
presence of symlinks (<a
href="https://redirect.github.com/psf/black/issues/4222">#4222</a>)</li>
<li><em>Black</em> now ignores <code>pyproject.toml</code> that is
missing a <code>tool.black</code> section when
discovering project root and configuration. Since <em>Black</em>
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 <code>[tool.black]</code> to the previously
discovered <code>pyproject.toml</code>
(<a
href="https://redirect.github.com/psf/black/issues/4204">#4204</a>)</li>
</ul>
<h3>Output</h3>
<ul>
<li>Black will swallow any <code>SyntaxWarning</code>s or
<code>DeprecationWarning</code>s produced by the <code>ast</code>
module when performing equivalence checks (<a
href="https://redirect.github.com/psf/black/issues/4189">#4189</a>)</li>
</ul>
<h3>Integrations</h3>
<ul>
<li>Add a JSONSchema and provide a validate-pyproject entry-point (<a
href="https://redirect.github.com/psf/black/issues/4181">#4181</a>)</li>
</ul>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/psf/black/commit/6fdf8a4af28071ed1d079c01122b34c5d587207a"><code>6fdf8a4</code></a>
Prepare release 24.2.0 (<a
href="https://redirect.github.com/psf/black/issues/4226">#4226</a>)</li>
<li><a
href="https://github.com/psf/black/commit/8af439407c051d55f3221cc93795d20bd9af49c9"><code>8af4394</code></a>
fix: Don't remove comments along with parens (<a
href="https://redirect.github.com/psf/black/issues/4218">#4218</a>)</li>
<li><a
href="https://github.com/psf/black/commit/35e97769190d8c8fe94d9ea2d70d7d88b22a2642"><code>35e9776</code></a>
Bump pre-commit/action from 3.0.0 to 3.0.1 (<a
href="https://redirect.github.com/psf/black/issues/4225">#4225</a>)</li>
<li><a
href="https://github.com/psf/black/commit/23dfc5b2c3b0694a8c27e58e28439591976aaf94"><code>23dfc5b</code></a>
Fix ignoring input files for symlink reasons (<a
href="https://redirect.github.com/psf/black/issues/4222">#4222</a>)</li>
<li><a
href="https://github.com/psf/black/commit/a20100395cf6179a81289452efad1d8e72b19682"><code>a201003</code></a>
Simplify check for symlinks that resolve outside root (<a
href="https://redirect.github.com/psf/black/issues/4221">#4221</a>)</li>
<li><a
href="https://github.com/psf/black/commit/dab37a6a1117d690d683121edc4d7c8fb8dd75a7"><code>dab37a6</code></a>
Remove redundant parentheses in <code>case</code> statement
<code>if</code> guards (<a
href="https://redirect.github.com/psf/black/issues/4214">#4214</a>)</li>
<li><a
href="https://github.com/psf/black/commit/32230e6f5c4bc6bb5c469451e15f3f54d9884b51"><code>32230e6</code></a>
fix: bug where the doublestar operation had inconsistent formatting. (<a
href="https://redirect.github.com/psf/black/issues/4154">#4154</a>)</li>
<li><a
href="https://github.com/psf/black/commit/7edb50f5a0afc56bb648dc14640ced144366b43a"><code>7edb50f</code></a>
fix: additional newline added to docstring when the previous line length
is l...</li>
<li><a
href="https://github.com/psf/black/commit/3e80de3447dee272e9977ab58b1560a669b7b848"><code>3e80de3</code></a>
Bump furo from 2023.9.10 to 2024.1.29 in /docs (<a
href="https://redirect.github.com/psf/black/issues/4211">#4211</a>)</li>
<li><a
href="https://github.com/psf/black/commit/a08b480a2f39fb4fc7b210d8b450e33d3879f77d"><code>a08b480</code></a>
Bump pypa/cibuildwheel from 2.16.4 to 2.16.5 (<a
href="https://redirect.github.com/psf/black/issues/4212">#4212</a>)</li>
<li>Additional commits viewable in <a
href="https://github.com/psf/black/compare/24.1.1...24.2.0">compare
view</a></li>
</ul>
</details>
<br />


[![Dependabot compatibility
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=black&package-manager=pip&previous-version=24.1.1&new-version=24.2.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)

Dependabot will resolve any conflicts with this PR as long as you don't
alter it yourself. You can also trigger a rebase manually by commenting
`@dependabot rebase`.

[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits
that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after
your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge
and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating
it. You can achieve the same result by closing it manually
- `@dependabot show <dependency name> ignore conditions` will show all
of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will close this PR and stop
Dependabot creating any more for this major version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop
Dependabot creating any more for this minor version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop
Dependabot creating any more for this dependency (unless you reopen the
PR or upgrade to it yourself)


</details>

---------

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Hans Keeler <[email protected]>
Co-authored-by: Adam <[email protected]>

Bumps [pytest](https://github.com/pytest-dev/pytest) from 8.0.2 to
8.1.0.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/pytest-dev/pytest/releases">pytest's
releases</a>.</em></p>
<blockquote>
<h2>8.1.0</h2>
<h1>pytest 8.1.0 (2024-03-03)</h1>
<h2>Features</h2>
<ul>
<li>
<p><a
href="https://redirect.github.com/pytest-dev/pytest/issues/11475">#11475</a>:
Added the new <code>consider_namespace_packages</code>{.interpreted-text
role=&quot;confval&quot;} configuration option, defaulting to
<code>False</code>.</p>
<p>If set to <code>True</code>, pytest will attempt to identify modules
that are part of <a
href="https://packaging.python.org/en/latest/guides/packaging-namespace-packages">namespace
packages</a> when importing modules.</p>
</li>
<li>
<p><a
href="https://redirect.github.com/pytest-dev/pytest/issues/11653">#11653</a>:
Added the new <code>verbosity_test_cases</code>{.interpreted-text
role=&quot;confval&quot;} configuration option for fine-grained control
of test execution verbosity.
See <code>Fine-grained verbosity
&lt;pytest.fine_grained_verbosity&gt;</code>{.interpreted-text
role=&quot;ref&quot;} for more details.</p>
</li>
</ul>
<h2>Improvements</h2>
<ul>
<li>
<p><a
href="https://redirect.github.com/pytest-dev/pytest/issues/10865">#10865</a>:
<code>pytest.warns</code>{.interpreted-text role=&quot;func&quot;} now
validates that <code>warnings.warn</code>{.interpreted-text
role=&quot;func&quot;} 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
<code>warnings.filterwarnings</code>{.interpreted-text
role=&quot;func&quot;} is used to filter those warnings (see [CPython <a
href="https://redirect.github.com/pytest-dev/pytest/issues/103577">#103577</a>](<a
href="https://redirect.github.com/python/cpython/issues/103577">python/cpython#103577</a>)
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.</p>
</li>
<li>
<p><a
href="https://redirect.github.com/pytest-dev/pytest/issues/11311">#11311</a>:
When using <code>--override-ini</code> for paths in invocations without
a configuration file defined, the current working directory is used
as the relative directory.</p>
<p>Previoulsy this would raise an
<code>AssertionError</code>{.interpreted-text
role=&quot;class&quot;}.</p>
</li>
<li>
<p><a
href="https://redirect.github.com/pytest-dev/pytest/issues/11475">#11475</a>:
<code>--import-mode=importlib
&lt;import-mode-importlib&gt;</code>{.interpreted-text
role=&quot;ref&quot;} now tries to import modules using the standard
import mechanism (but still without changing
:py<code>sys.path</code>{.interpreted-text role=&quot;data&quot;}),
falling back to importing modules directly only if that fails.</p>
<p>This means that installed packages will be imported under their
canonical name if possible first, for example
<code>app.core.models</code>, instead of having the module name always
be derived from their path (for example
<code>.env310.lib.site_packages.app.core.models</code>).</p>
</li>
<li>
<p><a
href="https://redirect.github.com/pytest-dev/pytest/issues/11801">#11801</a>:
Added the <code>iter_parents()
&lt;_pytest.nodes.Node.iter_parents&gt;</code>{.interpreted-text
role=&quot;func&quot;} helper method on nodes.
It is similar to <code>listchain
&lt;_pytest.nodes.Node.listchain&gt;</code>{.interpreted-text
role=&quot;func&quot;}, but goes from bottom to top, and returns an
iterator, not a list.</p>
</li>
<li>
<p><a
href="https://redirect.github.com/pytest-dev/pytest/issues/11850">#11850</a>:
Added support for <code>sys.last_exc</code>{.interpreted-text
role=&quot;data&quot;} for post-mortem debugging on Python&gt;=3.12.</p>
</li>
<li>
<p><a
href="https://redirect.github.com/pytest-dev/pytest/issues/11962">#11962</a>:
In case no other suitable candidates for configuration file are found, a
<code>pyproject.toml</code> (even without a
<code>[tool.pytest.ini_options]</code> table) will be considered as the
configuration file and define the <code>rootdir</code>.</p>
</li>
<li>
<p><a
href="https://redirect.github.com/pytest-dev/pytest/issues/11978">#11978</a>:
Add <code>--log-file-mode</code> option to the logging plugin, enabling
appending to log-files. This option accepts either
<code>&quot;w&quot;</code> or <code>&quot;a&quot;</code> and defaults to
<code>&quot;w&quot;</code>.</p>
<p>Previously, the mode was hard-coded to be <code>&quot;w&quot;</code>
which truncates the file before logging.</p>
</li>
<li>
<p><a
href="https://redirect.github.com/pytest-dev/pytest/issues/12047">#12047</a>:
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.</p>
</li>
</ul>
<h2>Bug Fixes</h2>
<ul>
<li>
<p><a
href="https://redirect.github.com/pytest-dev/pytest/issues/11904">#11904</a>:
Fixed a regression in pytest 8.0.0 that would cause test collection to
fail due to permission errors when using <code>--pyargs</code>.</p>
<p>This change improves the collection tree for tests specified using
<code>--pyargs</code>, see <code>12043</code>{.interpreted-text
role=&quot;pull&quot;} for a comparison with pytest 8.0 and &lt;8.</p>
</li>
</ul>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="https://github.com/pytest-dev/pytest/commit/b9a167f9bbbd6eda4f0360c5bf5b7f5af50f2bc4"><code>b9a167f</code></a>
Prepare release version 8.1.0</li>
<li><a
href="https://github.com/pytest-dev/pytest/commit/00043f7f1047b29fdaeb18e169fe9d6146988cb8"><code>00043f7</code></a>
Merge pull request <a
href="https://redirect.github.com/pytest-dev/pytest/issues/12038">#12038</a>
from bluetech/fixtures-rm-arg2index</li>
<li><a
href="https://github.com/pytest-dev/pytest/commit/f4e10251a4a003495b5228cea421d4de5fa0ce89"><code>f4e1025</code></a>
Merge pull request <a
href="https://redirect.github.com/pytest-dev/pytest/issues/12048">#12048</a>
from bluetech/fixture-teardown-excgroup</li>
<li><a
href="https://github.com/pytest-dev/pytest/commit/43492f5707b38dab9b62dfb829bb41a13579629f"><code>43492f5</code></a>
Merge pull request <a
href="https://redirect.github.com/pytest-dev/pytest/issues/12051">#12051</a>
from jakkdl/test_debugging_pythonbreakpoint</li>
<li><a
href="https://github.com/pytest-dev/pytest/commit/82fe28dae4eec900123175cee87245f37b964e5c"><code>82fe28d</code></a>
[automated] Update plugin list (<a
href="https://redirect.github.com/pytest-dev/pytest/issues/12049">#12049</a>)</li>
<li><a
href="https://github.com/pytest-dev/pytest/commit/5e2ee7175c145f84ff9882be9496abb56e6e56f2"><code>5e2ee71</code></a>
monkeypatch.delenv PYTHONBREAKPOINT in two tests that previously
failed/skipped</li>
<li><a
href="https://github.com/pytest-dev/pytest/commit/89ee4493ccbcd118349082cd78eb52a761683120"><code>89ee449</code></a>
Merge pull request <a
href="https://redirect.github.com/pytest-dev/pytest/issues/11997">#11997</a>
from nicoddemus/11475-importlib</li>
<li><a
href="https://github.com/pytest-dev/pytest/commit/8248946a552635f5751a58c7a6dfd24e98db7404"><code>8248946</code></a>
Do not collect symlinked tests under Windows (<a
href="https://redirect.github.com/pytest-dev/pytest/issues/12050">#12050</a>)</li>
<li><a
href="https://github.com/pytest-dev/pytest/commit/434282e17f5f1f4fcc1464a0a0921cf19804bdd7"><code>434282e</code></a>
fixtures: use exception group when multiple finalizers raise in fixture
teardown</li>
<li><a
href="https://github.com/pytest-dev/pytest/commit/d6134bc21e27efee7a2e264bd089e6c223515904"><code>d6134bc</code></a>
doc: document consider_namespace_packages option</li>
<li>Additional commits viewable in <a
href="https://github.com/pytest-dev/pytest/compare/8.0.2...8.1.0">compare
view</a></li>
</ul>
</details>
<br />


[![Dependabot compatibility
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=pytest&package-manager=pip&previous-version=8.0.2&new-version=8.1.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)

Dependabot will resolve any conflicts with this PR as long as you don't
alter it yourself. You can also trigger a rebase manually by commenting
`@dependabot rebase`.

[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)

---

<details>
<summary>Dependabot commands and options</summary>
<br />

You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits
that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after
your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge
and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating
it. You can achieve the same result by closing it manually
- `@dependabot show <dependency name> ignore conditions` will show all
of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will close this PR and stop
Dependabot creating any more for this major version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop
Dependabot creating any more for this minor version (unless you reopen
the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop
Dependabot creating any more for this dependency (unless you reopen the
PR or upgrade to it yourself)


</details>

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>