[antonrh]

Bumps the version to 0.81.0. A minor rather than a patch: a wrong anydi_container now fails the whole run, and test mode is on in sessions where it used to stay off.

After merge: git tag 0.81.0 && git push origin 0.81.0, then publish the notes below on the release.

Release notes

pytest plugin

• The container is in test mode before the first fixture runs, so a conftest that overrides through the container your application imports no longer warns Using override() without enabling test mode. Before, test mode came on only when some test requested the container fixture, so the warnings, and whether overrides applied to every resolution, depended on which test ran first. This covers the container named by anydi_container and a global container that exists once the tests are collected. Test mode is turned off again when the session ends. A container from your own container fixture still enters test mode when the fixture first runs. by @antonrh in Put the pytest plugin's container in test mode from the start #333
• A wrong anydi_container path now stops the run with a usage error naming the setting. Before, it failed only in the tests that requested the container fixture, so a run that never requested it passed. by @antonrh in Put the pytest plugin's container in test mode from the start #333
• anydi = false turns the plugin off for a project: no container fixture, no injection, the container left alone. The plugin stays on by default. by @antonrh in Put the pytest plugin's container in test mode from the start #333

[tool.pytest.ini_options]
anydi = false

[codspeed]

Merging this PR will not alter performance

✅ 17 untouched benchmarks

---

_{Comparing prepare-0.81.0 (aa2460f) with main (35f5e66)}