fix(deps): update python

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
python	dependencies	minor	3.12.* -> 3.13.*
python	final	minor	3.12-slim -> 3.13-slim

---

Release Notes

containerbase/python-prebuild (python)

v3.13.0

Compare Source

Bug Fixes

• deps: update dependency python to v3.13.0

---

Configuration

📅 Schedule: Branch creation - "every weekend" in timezone US/Eastern, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

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

---

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

[renovate]

⚠️ 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 ol-data-platform-S2WBxKbv-py3.13 in /home/ubuntu/.cache/pypoetry/virtualenvs

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

Because no versions of dagster-webserver match >1.8,<1.8.1 || >1.8.1,<1.8.2 || >1.8.2,<1.8.4 || >1.8.4,<1.8.5 || >1.8.5,<1.8.6 || >1.8.6,<1.8.7 || >1.8.7,<1.8.8 || >1.8.8,<1.8.9 || >1.8.9,<1.8.10 || >1.8.10,<1.8.11 || >1.8.11,<1.8.12 || >1.8.12,<1.8.13 || >1.8.13,<1.9.0 || >1.9.0,<1.9.1 || >1.9.1,<1.9.2 || >1.9.2,<1.9.3 || >1.9.3,<2.0
 and dagster-webserver (1.8.0) requires Python <3.13,>=3.8, dagster-webserver is forbidden.
And because dagster-webserver (1.8.1) requires Python <3.13,>=3.8, dagster-webserver is forbidden.
And because dagster-webserver (1.8.2) requires Python <3.13,>=3.8
 and dagster-webserver (1.8.4) requires Python <3.13,>=3.8, dagster-webserver is forbidden.
And because dagster-webserver (1.8.5) requires Python <3.13,>=3.8
 and dagster-webserver (1.8.6) requires Python <3.13,>=3.8, dagster-webserver is forbidden.
And because dagster-webserver (1.8.7) requires Python <3.13,>=3.8
 and dagster-webserver (1.8.8) requires Python <3.13,>=3.8, dagster-webserver is forbidden.
And because dagster-webserver (1.8.9) requires Python <3.13,>=3.8
 and dagster-webserver (1.8.10) requires Python <3.13,>=3.8, dagster-webserver is forbidden.
And because dagster-webserver (1.8.11) requires Python <3.13,>=3.8
 and dagster-webserver (1.8.12) requires Python <3.13,>=3.8, dagster-webserver is forbidden.
And because dagster-webserver (1.8.13) requires Python <3.13,>=3.8
 and dagster-webserver (1.9.0) requires Python <3.13,>=3.9, dagster-webserver is forbidden.
And because dagster-webserver (1.9.1) requires Python <3.13,>=3.9
 and dagster-webserver (1.9.2) requires Python <3.13,>=3.9, dagster-webserver is forbidden.
So, because dagster-webserver (1.9.3) requires Python <3.13,>=3.9
 and ol-data-platform depends on dagster-webserver (^1.8), version solving failed.

  • Check your dependencies Python requirement: The Python requirement can be specified via the `python` or `markers` properties
    
    For dagster-webserver, a possible solution would be to set the `python` property to "<empty>"
    For dagster-webserver, a possible solution would be to set the `python` property to "<empty>"
    For dagster-webserver, a possible solution would be to set the `python` property to "<empty>"
    For dagster-webserver, a possible solution would be to set the `python` property to "<empty>"
    For dagster-webserver, a possible solution would be to set the `python` property to "<empty>"
    For dagster-webserver, a possible solution would be to set the `python` property to "<empty>"
    For dagster-webserver, a possible solution would be to set the `python` property to "<empty>"
    For dagster-webserver, a possible solution would be to set the `python` property to "<empty>"
    For dagster-webserver, a possible solution would be to set the `python` property to "<empty>"
    For dagster-webserver, a possible solution would be to set the `python` property to "<empty>"
    For dagster-webserver, a possible solution would be to set the `python` property to "<empty>"
    For dagster-webserver, a possible solution would be to set the `python` property to "<empty>"
    For dagster-webserver, a possible solution would be to set the `python` property to "<empty>"
    For dagster-webserver, a possible solution would be to set the `python` property to "<empty>"
    For dagster-webserver, a possible solution would be to set the `python` property to "<empty>"
    For dagster-webserver, a possible solution would be to set the `python` property to "<empty>"
    For dagster-webserver, 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