Skip to content

fix(deps): update python to >=3.14,<3.15 #118

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.

Sign up for GitHub

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

Jump to bottom
Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

fix(deps): update python to >=3.14,<3.15 #118

wants to merge 1 commit into from

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Oct 26, 2024 •
edited
Loading

This PR contains the following updates:

Package Type Update Change
python dependencies minor >=3.12,<3.13 -> >=3.14,<3.15

Release Notes

containerbase/python-prebuild (python)

v3.14.0

Compare Source

Bug Fixes
  • deps: update dependency python to v3.14.0

v3.13.8

Compare Source

Bug Fixes
  • deps: update dependency python to v3.13.8

v3.13.7

Compare Source

Bug Fixes
  • deps: update dependency python to v3.13.7

v3.13.6

Compare Source

Bug Fixes
  • deps: update dependency python to v3.13.6

v3.13.5

Compare Source

Bug Fixes
  • deps: update dependency python to v3.13.5

v3.13.4

Compare Source

Bug Fixes
  • deps: update dependency python to v3.13.4

v3.13.3

Compare Source

Bug Fixes
  • deps: update dependency python to v3.13.3

v3.13.2

Compare Source

Bug Fixes
  • deps: update dependency python to v3.13.2

v3.13.1

Compare Source

Bug Fixes
  • deps: update dependency python to v3.13.1

v3.13.0

Compare Source

Bug Fixes
  • deps: update dependency python to v3.13.0

Configuration

📅 Schedule: Branch creation - "before 5am on saturday" (UTC), 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 renovate bot force-pushed the renovate/python-3.x branch 4 times, most recently from a785122 to 04ce319 Compare October 27, 2024 10:51
@renovate renovate bot force-pushed the renovate/python-3.x branch from 04ce319 to 70450ff Compare August 7, 2025 21:29
@renovate renovate bot force-pushed the renovate/python-3.x branch from 70450ff to 8bc2eb7 Compare August 16, 2025 02:00
@renovate
Copy link
Contributor Author

renovate bot commented Aug 19, 2025 •
edited
Loading

⚠️ 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...

Creating virtualenv almufarrigh in /tmp/renovate/repos/github/ieasybooks/almufarrigh/.venv

The current project's supported Python range (>=3.14,<3.15) is not compatible with some of the required packages Python requirement:
  - pyside6 requires Python <3.14,>=3.9, so it will not be satisfied for Python >=3.14,<3.15
  - pyside6 requires Python <3.14,>=3.9, so it will not be satisfied for Python >=3.14,<3.15
  - pyside6 requires Python <3.14,>=3.9, so it will not be satisfied for Python >=3.14,<3.15
  - pyside6 requires Python <3.13,>=3.8, so it will not be satisfied for Python >=3.14,<3.15
  - pyside6 requires Python <3.13,>=3.8, so it will not be satisfied for Python >=3.14,<3.15
  - pyside6 requires Python <3.13,>=3.8, so it will not be satisfied for Python >=3.14,<3.15
  - pyside6 requires Python <3.13,>=3.8, so it will not be satisfied for Python >=3.14,<3.15
  - pyside6 requires Python <3.13,>=3.9, so it will not be satisfied for Python >=3.14,<3.15
  - pyside6 requires Python <3.13,>=3.9, so it will not be satisfied for Python >=3.14,<3.15
  - pyside6 requires Python <3.13,>=3.9, so it will not be satisfied for Python >=3.14,<3.15
  - pyside6 requires Python <3.13,>=3.9, so it will not be satisfied for Python >=3.14,<3.15
  - pyside6 requires Python <3.13,>=3.9, so it will not be satisfied for Python >=3.14,<3.15
  - pyside6 requires Python <3.13,>=3.9, so it will not be satisfied for Python >=3.14,<3.15
  - pyside6 requires Python <3.14,>=3.9, so it will not be satisfied for Python >=3.14,<3.15
  - pyside6 requires Python <3.14,>=3.9, so it will not be satisfied for Python >=3.14,<3.15
  - pyside6 requires Python <3.14,>=3.9, so it will not be satisfied for Python >=3.14,<3.15
  - pyside6 requires Python <3.14,>=3.9, so it will not be satisfied for Python >=3.14,<3.15
  - pyside6 requires Python <3.14,>=3.9, so it will not be satisfied for Python >=3.14,<3.15
  - pyside6 requires Python <3.14,>=3.9, so it will not be satisfied for Python >=3.14,<3.15
  - pyside6 requires Python <3.14,>=3.9, so it will not be satisfied for Python >=3.14,<3.15
  - pyside6 requires Python <3.14,>=3.9, so it will not be satisfied for Python >=3.14,<3.15

Because no versions of pyside6 match >6.6.1,<6.6.2 || >6.6.2,<6.6.3 || >6.6.3,<6.6.3.1 || >6.6.3.1,<6.7.0 || >6.7.0,<6.7.1 || >6.7.1,<6.7.2 || >6.7.2,<6.7.3 || >6.7.3,<6.8.0 || >6.8.0,<6.8.0.1 || >6.8.0.1,<6.8.0.2 || >6.8.0.2,<6.8.1 || >6.8.1,<6.8.1.1 || >6.8.1.1,<6.8.2 || >6.8.2,<6.8.2.1 || >6.8.2.1,<6.8.3 || >6.8.3,<6.9.0 || >6.9.0,<6.9.1 || >6.9.1,<6.9.2 || >6.9.2,<6.9.3 || >6.9.3,<6.10.0 || >6.10.0,<7.0.0
 and pyside6 (6.6.1) requires Python <3.13,>=3.8, pyside6 is forbidden.
And because pyside6 (6.6.2) requires Python <3.13,>=3.8, pyside6 is forbidden.
And because pyside6 (6.6.3) requires Python <3.13,>=3.8
 and pyside6 (6.6.3.1) requires Python <3.13,>=3.8, pyside6 is forbidden.
And because pyside6 (6.7.0) requires Python <3.13,>=3.9
 and pyside6 (6.7.1) requires Python <3.13,>=3.9, pyside6 is forbidden.
And because pyside6 (6.7.2) requires Python <3.13,>=3.9
 and pyside6 (6.7.3) requires Python <3.13,>=3.9, pyside6 is forbidden.
And because pyside6 (6.8.0) requires Python <3.13,>=3.9
 and pyside6 (6.8.0.1) requires Python <3.13,>=3.9, pyside6 is forbidden.
And because pyside6 (6.8.1) requires Python <3.14,>=3.9
 and pyside6 (6.8.1.1) requires Python <3.14,>=3.9, pyside6 is forbidden.
And because pyside6 (6.8.2) requires Python <3.14,>=3.9
 and pyside6 (6.8.2.1) requires Python <3.14,>=3.9, pyside6 is forbidden.
And because pyside6 (6.8.3) requires Python <3.14,>=3.9
 and pyside6 (6.9.0) requires Python <3.14,>=3.9, pyside6 is forbidden.
And because pyside6 (6.9.1) requires Python <3.14,>=3.9
 and pyside6 (6.9.2) requires Python <3.14,>=3.9, pyside6 is forbidden.
And because pyside6 (6.9.3) requires Python <3.14,>=3.9
 and pyside6 (6.10.0) requires Python <3.14,>=3.9, pyside6 is forbidden.
So, because pyside6 (6.8.0.2) requires Python <3.14,>=3.9
 and almufarrigh depends on pyside6 (^6.6.1), version solving failed.

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

    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/python-3.x branch from 8bc2eb7 to 2712a5d Compare August 19, 2025 19:30
@renovate renovate bot force-pushed the renovate/python-3.x branch from 2712a5d to 0dc65c4 Compare October 8, 2025 04:23
@renovate renovate bot changed the title fix(deps): update python to >=3.13,<3.14 fix(deps): update python to >=3.14,<3.15 Oct 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

dependencies

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant