Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(deps): update dependency singledispatch to v4 #60

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 18, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
singledispatch ^3.7.0 -> ^4.0.0 age adoption passing confidence

Release Notes

jaraco/singledispatch (singledispatch)

v4.1.0

Compare Source

v4.0.0

Compare Source


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, 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 has been generated by Mend Renovate. View repository job log here.

@renovate
Copy link
Contributor Author

renovate bot commented Mar 18, 2023

⚠ 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: poetry.lock
Updating dependencies
Resolving dependencies...


The current project's supported Python range (>=2.7,<2.8 || >=3.6.0) is not compatible with some of the required packages Python requirement:
  - singledispatch requires Python >=3.8, so it will not be satisfied for Python >=2.7,<2.8 || >=3.6.0,<3.8
  - singledispatch requires Python >=3.7, so it will not be satisfied for Python >=2.7,<2.8 || >=3.6.0,<3.7

Because no versions of singledispatch match >4.0.0,<4.1.0 || >4.1.0,<5.0.0
 and singledispatch (4.0.0) requires Python >=3.7, singledispatch is forbidden.
So, because singledispatch (4.1.0) requires Python >=3.8
 and dayu-widgets depends on singledispatch (^4.0.0), version solving failed.

  • Check your dependencies Python requirement: The Python requirement can be specified via the `python` or `markers` properties
    
    For singledispatch, a possible solution would be to set the `python` property to ">=3.8"
    For singledispatch, a possible solution would be to set the `python` property to ">=3.7"

    https://python-poetry.org/docs/dependency-specification/#python-restricted-dependencies,
    https://python-poetry.org/docs/dependency-specification/#using-environment-markers

@renovate renovate bot force-pushed the renovate/singledispatch-4.x branch 6 times, most recently from 2b48a7f to 9c126ce Compare August 17, 2023 12:56
@renovate renovate bot force-pushed the renovate/singledispatch-4.x branch 5 times, most recently from 2938161 to 672c94c Compare September 26, 2023 13:28
Copy link
Contributor Author

renovate bot commented May 9, 2024

⚠️ 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: poetry.lock
Updating dependencies
Resolving dependencies...


The current project's supported Python range (>=2.7,<2.8 || >=3.6.0) is not compatible with some of the required packages Python requirement:
  - singledispatch requires Python >=3.8, so it will not be satisfied for Python >=2.7,<2.8 || >=3.6.0,<3.8
  - singledispatch requires Python >=3.7, so it will not be satisfied for Python >=2.7,<2.8 || >=3.6.0,<3.7

Because no versions of singledispatch match >4.0.0,<4.1.0 || >4.1.0,<5.0.0
 and singledispatch (4.0.0) requires Python >=3.7, singledispatch is forbidden.
So, because singledispatch (4.1.0) requires Python >=3.8
 and dayu-widgets depends on singledispatch (^4.0.0), version solving failed.

  • Check your dependencies Python requirement: The Python requirement can be specified via the `python` or `markers` properties
    
    For singledispatch, a possible solution would be to set the `python` property to ">=3.8"
    For singledispatch, a possible solution would be to set the `python` property to ">=3.7"

    https://python-poetry.org/docs/dependency-specification/#python-restricted-dependencies,
    https://python-poetry.org/docs/dependency-specification/#using-environment-markers

@renovate renovate bot force-pushed the renovate/singledispatch-4.x branch 6 times, most recently from 30d26a5 to da65df6 Compare June 14, 2024 06:53
@renovate renovate bot force-pushed the renovate/singledispatch-4.x branch 2 times, most recently from 4fc4839 to 2f18022 Compare June 21, 2024 03:09
@renovate renovate bot force-pushed the renovate/singledispatch-4.x branch from 2f18022 to 32af1e0 Compare June 21, 2024 03:11
@muyr muyr closed this Jun 21, 2024
Copy link
Contributor Author

renovate bot commented Jun 21, 2024

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 4.x releases. But if you manually upgrade to 4.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

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.

1 participant