Bump tox from 4.3.3 to 4.3.5

[dependabot]

Bumps tox from 4.3.3 to 4.3.5.

Release notes

Sourced from tox's releases.

4.3.5

What's Changed

• Include WHEEL metadata when using PDM and poetry backends by @​masenf in tox-dev/tox#2881

Full Changelog: tox-dev/tox@4.3.4...4.3.5

4.3.4

What's Changed

• Provision cwd by @​masenf in tox-dev/tox#2877
• Fix the type annotation for color param of Spinner.finalize() by @​kurtmckee in tox-dev/tox#2879

Full Changelog: tox-dev/tox@4.3.3...4.3.4

Changelog

Sourced from tox's changelog.

v4.3.5 (2023-01-18)

Bugfixes - 4.3.5

- When building a ``wheel`` or ``editable`` package with a PEP 517 backend, no
  longer pass an empty ``metadata_directory`` to the backend ``build_wheel`` or
  ``build_editable`` endpoint.
Some backends, such as PDM and poetry, will not generate package metadata in
the presence of a metadata_directory, even if it is empty.
Prior to this change, attempting to install a wheel created by tox using PDM or
poetry would return an error like "There is no item named
'my-package.0.1.dist-info/WHEEL' in the archive" - by :user:masenf. (:issue:2880)
v4.3.4 (2023-01-17)
Bugfixes - 4.3.4

• When executing via the provisioning environment (.tox by default), run tox in working directory of the parent process.

  Prior to this change (from tox 4.0.0), the provisioned tox would execute with {tox_root} as the working directory, which breaks when a relative path is passed to -c or --conf and tox is executed in a working directory other than {tox_root} - by :user:masenf. (:issue:2876)

Misc - 4.3.4

- :issue:`2878`

Commits

• 7eec025 release 4.3.5
• 8323aaa Include WHEEL metadata when using PDM and poetry backends (#2881)
• 23510dc release 4.3.4
• d53f062 Fix the type annotation for color param of Spinner.finalize() (#2879)
• 2a87375 Provision cwd (#2877)
• See full diff in compare view

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 commands and options

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 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)