Skip to content

chore(deps): update dependency tox to v4.49.0#946

Merged
zhindes merged 1 commit intomasterfrom
users/renovate/python
Mar 23, 2026
Merged

chore(deps): update dependency tox to v4.49.0#946
zhindes merged 1 commit intomasterfrom
users/renovate/python

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Mar 22, 2026

This PR contains the following updates:

Package Change Age Confidence
tox (changelog) 4.47.04.49.0 age confidence

Release Notes

tox-dev/tox (tox)

v4.49.0

Compare Source

What's Changed
New Contributors

Full Changelog: tox-dev/tox@4.48.1...4.49.0

v4.48.1

Compare Source

What's Changed

Full Changelog: tox-dev/tox@4.48.0...4.48.1

v4.48.0

Compare Source

What's Changed

Full Changelog: tox-dev/tox@4.47.3...4.48.0

v4.47.3

Compare Source

What's Changed

Full Changelog: tox-dev/tox@4.47.2...4.47.3

v4.47.2

Compare Source

What's Changed

New Contributors

Full Changelog: tox-dev/tox@4.47.1...4.47.2

v4.47.1

Compare Source

What's Changed

Full Changelog: tox-dev/tox@4.47.0...4.47.1


Configuration

📅 Schedule: Branch creation - Only on Sunday ( * * * * 0 ) in timezone US/Central, 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.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate
Copy link
Contributor Author

renovate bot commented Mar 22, 2026

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: pyproject.toml
Artifact update for tox resolved to version 4.50.3, which is a pending version that has not yet passed the Minimum Release Age threshold.
Renovate was attempting to update to 4.49.0
This is (likely) not a bug in Renovate, but due to the way your project pins dependencies, _and_ how Renovate calls your package manager to update them.
Until Renovate supports specifying an exact update to your package manager (https://github.com/renovatebot/renovate/issues/41624), it is recommended to directly pin your dependencies (with `rangeStrategy=pin` for apps, or `rangeStrategy=widen` for libraries)
See also: https://docs.renovatebot.com/dependency-pinning/

@github-actions
Copy link
Contributor

Test Results

    48 files  ±0      48 suites  ±0   1h 18m 32s ⏱️ +25s
 3 209 tests ±0   2 556 ✅ ±0     653 💤 ±0  0 ❌ ±0 
62 228 runs  ±0  49 398 ✅ ±0  12 830 💤 ±0  0 ❌ ±0 

Results for commit ad59a37. ± Comparison against base commit 6c6ecde.

@zhindes zhindes merged commit 5902200 into master Mar 23, 2026
35 of 36 checks passed
@bkeryan
Copy link
Collaborator

bkeryan commented Mar 23, 2026

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: pyproject.toml
Artifact update for tox resolved to version 4.50.3, which is a pending version that has not yet passed the Minimum Release Age threshold.
Renovate was attempting to update to 4.49.0
This is (likely) not a bug in Renovate, but due to the way your project pins dependencies, _and_ how Renovate calls your package manager to update them.
Until Renovate supports specifying an exact update to your package manager (https://github.com/renovatebot/renovate/issues/41624), it is recommended to directly pin your dependencies (with `rangeStrategy=pin` for apps, or `rangeStrategy=widen` for libraries)
See also: https://docs.renovatebot.com/dependency-pinning/

FYI @zhindes @mshafer-NI It's good that Renovate warns about this now, but I don't like the suggested solution because it basically turns pyproject.toml into a lock file that gets updated whenever new dependency versions are released.

@zhindes
Copy link
Collaborator

zhindes commented Mar 23, 2026

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: pyproject.toml
Artifact update for tox resolved to version 4.50.3, which is a pending version that has not yet passed the Minimum Release Age threshold.
Renovate was attempting to update to 4.49.0
This is (likely) not a bug in Renovate, but due to the way your project pins dependencies, _and_ how Renovate calls your package manager to update them.
Until Renovate supports specifying an exact update to your package manager (https://github.com/renovatebot/renovate/issues/41624), it is recommended to directly pin your dependencies (with `rangeStrategy=pin` for apps, or `rangeStrategy=widen` for libraries)
See also: https://docs.renovatebot.com/dependency-pinning/

FYI @zhindes @mshafer-NI It's good that Renovate warns about this now, but I don't like the suggested solution because it basically turns pyproject.toml into a lock file that gets updated whenever new dependency versions are released.

Wow... I somehow totally missed this when I approved and merged that this morning. My workflow was to look at the description, the diff of the lock, and then the results:
image

@mshafer-NI
Copy link
Collaborator

FYI @zhindes @mshafer-NI It's good that Renovate warns about this now, but I don't like the suggested solution because it basically turns pyproject.toml into a lock file that gets updated whenever new dependency versions are released.

I explicitly want our configs to be set to "widen" dep range. For the same reason that we have historically used ">="

@bkeryan
Copy link
Collaborator

bkeryan commented Mar 23, 2026

FYI @zhindes @mshafer-NI It's good that Renovate warns about this now, but I don't like the suggested solution because it basically turns pyproject.toml into a lock file that gets updated whenever new dependency versions are released.

I explicitly want our configs to be set to "widen" dep range. For the same reason that we have historically used ">="

My interpretation of Renovate's suggestion is that we should put upper bounds in pyproject.toml like click = ">=8.0.0, <8.3.1" and I think that will have the following results:

  • Renovate edits pyproject.toml whenever any dependency is updated, causing pyproject.toml to have as much churn & merge conflicts as a lock file
  • When a new dependency version is released, customers cannot use it until we release a new version of nidaqmx. For example, when click 8.3.2 is released, customers cannot upgrade to it until Renovate widens the range in nidaqmx's pyproject.toml to click = ">=8.0.0, <8.3.2" and NI releases a new nidaqmx version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants