Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: tox-dev/tox
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: 4.37.0
Choose a base ref
...
head repository: tox-dev/tox
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: 4.38.0
Choose a head ref
  • 3 commits
  • 4 files changed
  • 4 contributors

Commits on Feb 17, 2026

  1. 🐛 fix(test): resolve Windows CI flake in provision integration tests (#… 

    …3732)

The Windows CI job `test 3.12 on windows-2025` fails intermittently on
`test_provision_install_pkg_pep517`. Investigation showed the test
consistently takes ~32s on Windows due to provisioned subprocess pip
installs, which exceeds the global 30s `pytest-timeout`. The "deadlock"
stack trace is actually `pytest-timeout` dumping threads before killing
the test. 🔍

The fix raises the timeout to 120s for both provision integration tests
that spawn real subprocesses. This also re-enables
`test_provision_requires_ok` on Windows, which was skipped under the
assumption it deadlocked — the actual cause was the same 30s timeout
being too tight for these heavier integration tests.

Validated with 20/20 passes on `windows-2025` CI runners.
    @gaborbernat
    gaborbernat authored Feb 17, 2026
    Configuration menu
    Copy the full SHA
    559e89c View commit details
    Browse the repository at this point in the history

  2. Scope deps rejection to pure PEP-517 build types (#3730) 

    PR #3687 (fix for #3412) added a hard Fail in
Pep517VenvPackager._setup_env() that rejects any deps on PEP-517
packaging environments. This broke two downstream consumers:

tox-uv — Tests for editable-legacy, workspace, and no_pyproject
scenarios set deps = wheel on .pkg because uv doesn't seed wheel into
venvs by default (unlike virtualenv). The editable-legacy flow needs
wheel importable in the packaging venv for setup.py develop. CI:
https://github.com/tox-dev/tox-uv/actions/runs/22071221669

Uses package = external with deps = build on .pkg to run python -m build
for sdist→wheel workflow. Discussion:
#3491 (reply in thread)
Fix PR: qiskit-community/qiskit-experiments#1615


Only raise the error when call_require_hooks is a subset of {"sdist",
"wheel", "editable"} (standard PEP-517 types). Allow deps when
editable-legacy or external is involved

Fixes: #3731

<!-- Thank you for your contribution!

Please, make sure you address all the checklists (for details on how see
[development
documentation](http://tox.readthedocs.org/en/latest/development.html#development))!
-->

- [x] ran the linter to address style issues (`tox -e fix`)
- [x] wrote descriptive pull request text
- [x] ensured there are test(s) validating the fix
- [x] added news fragment in `docs/changelog` folder
- [ ] updated/extended the documentation

---------

Co-authored-by: Bernát Gábor <gaborjbernat@gmail.com>
Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
    @rahuldevikar @gaborbernat @pre-commit-ci
    3 people authored Feb 17, 2026
    Configuration menu
    Copy the full SHA
    6b54516 View commit details
    Browse the repository at this point in the history

  3. release 4.38.0

    @gaborbernat
    gaborbernat committed Feb 17, 2026
    Configuration menu
    Copy the full SHA
    7c2180b View commit details
    Browse the repository at this point in the history
Loading