You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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/
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.
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:
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 ">="
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.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
4.47.0→4.49.0Release Notes
tox-dev/tox (tox)
v4.49.0Compare Source
What's Changed
New Contributors
Full Changelog: tox-dev/tox@4.48.1...4.49.0
v4.48.1Compare Source
What's Changed
Full Changelog: tox-dev/tox@4.48.0...4.48.1
v4.48.0Compare Source
What's Changed
Full Changelog: tox-dev/tox@4.47.3...4.48.0
v4.47.3Compare Source
What's Changed
Full Changelog: tox-dev/tox@4.47.2...4.47.3
v4.47.2Compare Source
What's Changed
New Contributors
Full Changelog: tox-dev/tox@4.47.1...4.47.2
v4.47.1Compare 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.
This PR was generated by Mend Renovate. View the repository job log.