Skip to content

chore(deps)(deps): bump the python-versions group across 1 directory with 6 updates - #1195

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/uv/python-versions-708788cd1e
Open

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/uv/python-versions-708788cd1e

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 18, 2026

Copy link
Copy Markdown
Contributor

Bumps the python-versions group with 6 updates in the / directory:

Package From To
kaleido 1.5.0 1.5.1
sphinx-design 0.7.0 0.8.0
pydantic-settings 2.16.2 2.16.3
dagster 1.13.29 1.13.30
dagster-webserver 1.13.29 1.13.30
numpy 2.5.4 2.5.5

Updates kaleido from 1.5.0 to 1.5.1

Release notes

Sourced from kaleido's releases.

v1.5.1

Fixed

  • Prevent occasional hangs during startup by enabling page events before navigation [#482], with thanks to @​dennisjlee for the contribution!
Changelog

Sourced from kaleido's changelog.

v1.5.1 -- 2026-11-12

Fixed

  • Prevent occasional hangs during startup by enabling page events before navigation [#482], with thanks to @​dennisjlee for the contribution!
Commits
  • 0449637 chore: Update files for release of v1.5.1 (#486)
  • 561acda fix: Prevent race condition by enabling page events before navigation (#482)
  • See full diff in compare view

Updates sphinx-design from 0.7.0 to 0.8.0

Release notes

Sourced from sphinx-design's releases.

v0.8.0

New components (accordion, aside, steps, vertical tab sets, and explicit card header and footer directives), links that open in a new tab, badge tooltips, a plain-CSS build with no Sass, tab selections that persist across pages and visits, accessibility fixes, FontAwesome v6 support, and Octicons v19.42.0. Sphinx 7.2 or later is now required.

Upgrade notes

  • Sphinx >=7.2 is required (Sphinx 7.0 and 7.1 are no longer supported); Python stays at >=3.11 ({pr}276).

  • The ^^^ and +++ card separators are deprecated and warn by default. They still render as before, but the first card in a document that uses them emits one design.card_legacy warning, so a build run with -W fails until you do one of two things:

    • move the header and footer into the new card-header and card-footer directives (or the one-line :header: and :footer: options), which need sphinx-design 0.8.0 or later; or
    • add "design.card_legacy" to suppress_warnings in your conf.py.

    Once every card is migrated, set sd_card_legacy_separators = False to stop scanning for the separators. The plan is to turn the separators off by default in 1.0 and remove them in 2.0; the cards page has a migration table ({pr}294).

  • Tab selections persist in localStorage instead of sessionStorage, so a chosen tab is remembered across browsing sessions as well as across pages. The storage key prefix is set by the new sd_tabs_storage_prefix option; set it to an empty string to disable persistence ({pr}284, {issue}103).

  • Static assets are served through Sphinx's html_static_path, only for HTML-format builders. A _sphinx_design_static directory left in an existing build directory by an earlier version is unused and can be deleted ({pr}276).

  • The stylesheet is plain CSS, generated without Sass. The --sd-color-*-highlight hover and focus shades are now derived at runtime with color-mix() (behind the old value as a static fallback), so overriding a --sd-color-* variable now also changes its hover shade ({pr}290).

  • The private sphinx_design._compat.findall helper is removed; call node.findall(...) directly ({pr}276). The private CardDirective._create_component method is renamed _create_slot; the old name stays as an alias for one release ({pr}294).

  • sd-card-text is added only to the direct child paragraphs of a card or dropdown body, and is added to a paragraph's classes instead of replacing them; paragraphs nested deeper (in admonitions, lists, nested tab sets) no longer get it ({pr}278).

New

  • ✨ accordion directive: groups dropdowns so that opening one closes the others, using the browser's native <details name> behaviour with no JavaScript; :flush: renders it edge to edge by {user}chrisjsewell in {pr}291
  • ✨ aside directive: a call-out box floated beside the body text (:align:, :width:), rendered as a semantic <aside> in HTML and a plain titled container elsewhere by {user}chrisjsewell in {pr}292 ({issue}97)
  • ✨ steps and step directives for numbered procedures, with CSS-only number markers on an ordered list, :start: and :color: options by {user}chrisjsewell in {pr}293
  • ✨ card-header and card-footer directives, and :header: and :footer: options, for card and grid-item-card headers and footers: the card body is parsed once as ordinary content, and errors in a header or footer report their own line (see the upgrade notes for the legacy separators) by {user}chrisjsewell in {pr}294

... (truncated)

Changelog

Sourced from sphinx-design's changelog.

0.8.0 - 2026-11-10

New components (accordion, aside, steps, vertical tab sets, and explicit card header and footer directives), links that open in a new tab, badge tooltips, a plain-CSS build with no Sass, tab selections that persist across pages and visits, accessibility fixes, FontAwesome v6 support, and Octicons v19.42.0. Sphinx 7.2 or later is now required.

Upgrade notes

  • Sphinx >=7.2 is required (Sphinx 7.0 and 7.1 are no longer supported); Python stays at >=3.11 ({pr}276).

  • The ^^^ and +++ card separators are deprecated and warn by default. They still render as before, but the first card in a document that uses them emits one design.card_legacy warning, so a build run with -W fails until you do one of two things:

    • move the header and footer into the new card-header and card-footer directives (or the one-line :header: and :footer: options), which need sphinx-design 0.8.0 or later; or
    • add "design.card_legacy" to suppress_warnings in your conf.py.

    Once every card is migrated, set sd_card_legacy_separators = False to stop scanning for the separators. The plan is to turn the separators off by default in 1.0 and remove them in 2.0; the cards page has a migration table ({pr}294).

  • Tab selections persist in localStorage instead of sessionStorage, so a chosen tab is remembered across browsing sessions as well as across pages. The storage key prefix is set by the new sd_tabs_storage_prefix option; set it to an empty string to disable persistence ({pr}284, {issue}103).

  • Static assets are served through Sphinx's html_static_path, only for HTML-format builders. A _sphinx_design_static directory left in an existing build directory by an earlier version is unused and can be deleted ({pr}276).

  • The stylesheet is plain CSS, generated without Sass. The --sd-color-*-highlight hover and focus shades are now derived at runtime with color-mix() (behind the old value as a static fallback), so overriding a --sd-color-* variable now also changes its hover shade ({pr}290).

  • The private sphinx_design._compat.findall helper is removed; call node.findall(...) directly ({pr}276). The private CardDirective._create_component method is renamed _create_slot; the old name stays as an alias for one release ({pr}294).

  • sd-card-text is added only to the direct child paragraphs of a card or dropdown body, and is added to a paragraph's classes instead of replacing them; paragraphs nested deeper (in admonitions, lists, nested tab sets) no longer get it ({pr}278).

New

  • ✨ accordion directive: groups dropdowns so that opening one closes the others, using the browser's native <details name> behaviour with no JavaScript; :flush: renders it edge to edge by {user}chrisjsewell in {pr}291
  • ✨ aside directive: a call-out box floated beside the body text (:align:, :width:), rendered as a semantic <aside> in HTML and a plain titled container elsewhere by {user}chrisjsewell in {pr}292 ({issue}97)
  • ✨ steps and step directives for numbered procedures, with CSS-only number markers on an ordered list, :start: and :color: options by {user}chrisjsewell in {pr}293
  • ✨ card-header and card-footer directives, and :header: and :footer: options, for card and grid-item-card headers and footers: the card body is parsed once as ordinary content, and errors in a header or footer report their own line (see the upgrade notes for the legacy separators)

... (truncated)

Commits
  • fcaa5b3 🚀 RELEASE: v0.8.0 (#317)
  • cb9828f 🔧 Drop sd_custom_roles before 0.8.0: the badge roles take a tooltip role opti...
  • c7b2d2f ⬆️ UPGRADE: Octicons to v19.42.0 (#309)
  • 6c5a4be ✨ NEW: open card and button links in a new tab (#298)
  • f2accd9 ♻️ Card header/footer sub-directives: a pure parse replaces raw-text splittin...
  • 2f473aa ✨ Add sd_custom_roles: config-defined badge roles with baked tooltips (#295)
  • 0511463 ✨ Add a steps component (#293)
  • 7d1aeed ⬆️ Bump actions/setup-python to v7 and actions/upload-artifact to v7 (#299)
  • 4c3864d ✨ Add an aside component (#292)
  • 21af548 ⬆️ Allow pydata-sphinx-theme <0.25 (#313)
  • Additional commits viewable in compare view

Updates pydantic-settings from 2.16.2 to 2.16.3

Release notes

Sourced from pydantic-settings's releases.

v2.16.3

Highlights

This patch release fixes a security issue in the default secrets source, a regression from 2.14.2 that dropped nested secrets on Kubernetes, and a CliApp.serialize round-trip bug with CliUnknownArgs.

Security

  • SecretsSettingsSource no longer follows symlinks that resolve outside secrets_dir (#1138, fixes #1137). A secret file that is a symbolic link to a file outside secrets_dir was read into the matching field, so anyone who could place a link in secrets_dir could make the application load any file it can read. This is the plain-source counterpart of GHSA-4xgf-cpjx-pc3j, whose fix in 2.14.2 covered only NestedSecretsSettingsSource. Links that stay inside secrets_dir, such as the Kubernetes secret volume layout (passwd linking to ..data/passwd), still work.

Behavior changes

  • A secret file that resolves outside secrets_dir is now skipped with a warning instead of being read (#1138). If you deliberately point secret files at targets elsewhere on disk, move or copy the targets into secrets_dir, or point secrets_dir at the directory that holds them.
  • NestedSecretsSettingsSource skips hidden entries (names starting with .) again, as it did before 2.14.2, and stops with a SettingsError after 10,000 entries (#1070).

Bug fixes

Secrets

  • With secrets_nested_subdir=True, a directory reached through a second symlink is loaded again (#1070, fixes #1061). Since 2.14.2, only the name that sorted first was walked, so the standard Kubernetes secret volume layout (db linking to ..data/db) silently lost its nested secrets.
  • A symlink loop inside secrets_dir is skipped instead of aborting the load with RuntimeError on Python 3.11 and 3.12 (#1070, #1138).

CLI

  • CliApp.serialize keeps each level's CliUnknownArgs before that level's subcommand token (#1050, fixes #1048). They were emitted after the last subcommand, so parsing the output again moved a parent's unknown args onto the subcommand.

What's Changed

New Contributors

Full Changelog: pydantic/pydantic-settings@v2.16.2...v2.16.3

Commits
  • 50e676c Prepare release 2.16.3
  • e394a88 Prevent SecretsSettingsSource from following symlinks outside secrets_dir (#1...
  • 2e66451 Load nested secrets reached through a second directory link (#1070)
  • 0379552 Fix CliApp.serialize moving a parent unknown args into the subcommand (#1050)
  • See full diff in compare view

Updates dagster from 1.13.29 to 1.13.30

Release notes

Sourced from dagster's releases.

1.13.30 (core) / 0.29.30 (libraries)

New

  • Dropped support for Python 3.10. Dagster now requires Python 3.11 or later.
  • [ui] The asset catalog and asset graph no longer poll asset health data for assets whose health isn't shown, which reduces load when browsing large workspaces.
  • [dagster-cloud-cli] Added a dagster-cloud deployment copy-materializations command, which copies the latest asset materializations from one deployment to another and keeps their original timestamps.

Bugfixes

  • [dagster-cloud-cli] Fixed Serverless fast deploys failing with No module named ... when the project's code is not installed as a package.

Dagster Plus

  • Users with the "Edit concurrency limits" permission can now edit concurrency limits from the Concurrency settings page.
  • The Dagster+ MCP server now has tools to read schedules, sensors, and their ticks, to start and stop schedules and sensors, and to work with asset partitions, including adding and deleting dynamic partitions.
  • Serverless code locations that take more than 3 minutes to load no longer fail to deploy.
  • Serverless base images are no longer built for Python 3.10. Existing Python 3.10 PEX code locations keep running on the last Python 3.10 base image.
  • Fixed the "Send Sample Alert" button on the alert policy details page not sending Slack alerts.
  • Alert emails and Microsoft Teams alerts now escape customer-provided values such as job names and asset keys, so those values can no longer inject HTML.
Changelog

Sourced from dagster's changelog.

1.13.30 (core) / 0.29.30 (libraries)

New

  • Dropped support for Python 3.10. Dagster now requires Python 3.11 or later.
  • [ui] The asset catalog and asset graph no longer poll asset health data for assets whose health isn't shown, which reduces load when browsing large workspaces.
  • [dagster-cloud-cli] Added a dagster-cloud deployment copy-materializations command, which copies the latest asset materializations from one deployment to another and keeps their original timestamps.

Bugfixes

  • [dagster-cloud-cli] Fixed Serverless fast deploys failing with No module named ... when the project's code is not installed as a package.

Dagster Plus

  • Users with the "Edit concurrency limits" permission can now edit concurrency limits from the Concurrency settings page.
  • The Dagster+ MCP server now has tools to read schedules, sensors, and their ticks, to start and stop schedules and sensors, and to work with asset partitions, including adding and deleting dynamic partitions.
  • Serverless code locations that take more than 3 minutes to load no longer fail to deploy.
  • Serverless base images are no longer built for Python 3.10. Existing Python 3.10 PEX code locations keep running on the last Python 3.10 base image.
  • Fixed the "Send Sample Alert" button on the alert policy details page not sending Slack alerts.
  • Alert emails and Microsoft Teams alerts now escape customer-provided values such as job names and asset keys, so those values can no longer inject HTML.
Commits
  • 528c6d6 1.13.30
  • faf0ccd Changelog for 1.13.30 (#27767)
  • 93e5f51 [dagster-cloud] pluralize counts in copy-materializations output (#27718)
  • a62c589 fix(serverless): run PEX-bundle code servers from the project root (#27682)
  • cedd818 Read the sensor daemon's sensor states from the read replica behind a gate (#...
  • 5945778 Read the asset daemon's sensor states from the read replica behind a gate (#2...
  • 599d780 [mcp] Add partition tools (#27288)
  • 6ddd8f7 [mcp] Add start/stop schedule and sensor tools (#27287)
  • 288ed03 [mcp] Add schedule, sensor, and tick read tools (#27286)
  • 386b81c [dagster-cloud] correct automation note in copy-materializations help (#27717)
  • Additional commits viewable in compare view

Updates dagster-webserver from 1.13.29 to 1.13.30

Release notes

Sourced from dagster-webserver's releases.

1.13.30 (core) / 0.29.30 (libraries)

New

  • Dropped support for Python 3.10. Dagster now requires Python 3.11 or later.
  • [ui] The asset catalog and asset graph no longer poll asset health data for assets whose health isn't shown, which reduces load when browsing large workspaces.
  • [dagster-cloud-cli] Added a dagster-cloud deployment copy-materializations command, which copies the latest asset materializations from one deployment to another and keeps their original timestamps.

Bugfixes

  • [dagster-cloud-cli] Fixed Serverless fast deploys failing with No module named ... when the project's code is not installed as a package.

Dagster Plus

  • Users with the "Edit concurrency limits" permission can now edit concurrency limits from the Concurrency settings page.
  • The Dagster+ MCP server now has tools to read schedules, sensors, and their ticks, to start and stop schedules and sensors, and to work with asset partitions, including adding and deleting dynamic partitions.
  • Serverless code locations that take more than 3 minutes to load no longer fail to deploy.
  • Serverless base images are no longer built for Python 3.10. Existing Python 3.10 PEX code locations keep running on the last Python 3.10 base image.
  • Fixed the "Send Sample Alert" button on the alert policy details page not sending Slack alerts.
  • Alert emails and Microsoft Teams alerts now escape customer-provided values such as job names and asset keys, so those values can no longer inject HTML.
Changelog

Sourced from dagster-webserver's changelog.

1.13.30 (core) / 0.29.30 (libraries)

New

  • Dropped support for Python 3.10. Dagster now requires Python 3.11 or later.
  • [ui] The asset catalog and asset graph no longer poll asset health data for assets whose health isn't shown, which reduces load when browsing large workspaces.
  • [dagster-cloud-cli] Added a dagster-cloud deployment copy-materializations command, which copies the latest asset materializations from one deployment to another and keeps their original timestamps.

Bugfixes

  • [dagster-cloud-cli] Fixed Serverless fast deploys failing with No module named ... when the project's code is not installed as a package.

Dagster Plus

  • Users with the "Edit concurrency limits" permission can now edit concurrency limits from the Concurrency settings page.
  • The Dagster+ MCP server now has tools to read schedules, sensors, and their ticks, to start and stop schedules and sensors, and to work with asset partitions, including adding and deleting dynamic partitions.
  • Serverless code locations that take more than 3 minutes to load no longer fail to deploy.
  • Serverless base images are no longer built for Python 3.10. Existing Python 3.10 PEX code locations keep running on the last Python 3.10 base image.
  • Fixed the "Send Sample Alert" button on the alert policy details page not sending Slack alerts.
  • Alert emails and Microsoft Teams alerts now escape customer-provided values such as job names and asset keys, so those values can no longer inject HTML.
Commits
  • 528c6d6 1.13.30
  • faf0ccd Changelog for 1.13.30 (#27767)
  • 93e5f51 [dagster-cloud] pluralize counts in copy-materializations output (#27718)
  • a62c589 fix(serverless): run PEX-bundle code servers from the project root (#27682)
  • cedd818 Read the sensor daemon's sensor states from the read replica behind a gate (#...
  • 5945778 Read the asset daemon's sensor states from the read replica behind a gate (#2...
  • 599d780 [mcp] Add partition tools (#27288)
  • 6ddd8f7 [mcp] Add start/stop schedule and sensor tools (#27287)
  • 288ed03 [mcp] Add schedule, sensor, and tick read tools (#27286)
  • 386b81c [dagster-cloud] correct automation note in copy-materializations help (#27717)
  • Additional commits viewable in compare view

Updates numpy from 2.5.4 to 2.5.5

Release notes

Sourced from numpy's releases.

v2.5.5 (Nov 15, 2026)

NumPy 2.5.5 Release Notes

Released on 2026-11-15.

NumPy 2.5.5 is a patch release that fixes bugs discovered after the 2.5.4 release. It is unusually large for a patch release due to bugs discovered during continuing work on strings for the upcoming 2.6.0 release, ongoing threading work, the eMudhra compromise fixes, and updates in GitHub CI infrastructure.

This release supports Python versions 3.12-3.15.

Compatibility notes

  • Casting a structured void dtype or subarray dtype to numpy.dtypes.StringDType now raises a TypeError instead of interpreting the raw bytes of each element as UTF-8.

    (gh-33298)

Contributors

A total of 12 people contributed to this release. People with a "+" by their names contributed a patch for the first time.

  • Anush Vishwakarma +
  • Arthur Lacote
  • Bharath Pranav +
  • Charles Harris
  • David King +
  • Iason Krommydas
  • Joren Hammudoglu
  • Kevin Sheppard
  • Matti Picus
  • Nathan Goldbaum
  • Peter Hawkins
  • Shubham Bansal +

Pull requests merged

A total of 37 pull requests were merged for this release.

  • #32971: MAINT: Prepare 2.5.x for further development
  • #33100: MAINT: Update OpenBLAS to 0.3.34.237.2
  • #33114: MAINT: Update cibuildwheel to v4.3.3
  • #33117: BUG: warm finfo cache with float64 on 2.5.x (gh-32947)
  • #33130: MAINT: Update pixi workflow from main.
  • #33141: MAINT: Update cibuildwheel to v4.3.4 and uv to v0.13.5
  • #33155: BUG: fix nanquantile dtype for all-NaN first slice (#32940)

... (truncated)

Commits

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

…with 6 updates

Bumps the python-versions group with 6 updates in the / directory:

| Package | From | To |
| --- | --- | --- |
| [kaleido](https://github.com/plotly/kaleido) | `1.5.0` | `1.5.1` |
| [sphinx-design](https://github.com/executablebooks/sphinx-design) | `0.7.0` | `0.8.0` |
| [pydantic-settings](https://github.com/pydantic/pydantic-settings) | `2.16.2` | `2.16.3` |
| [dagster](https://github.com/dagster-io/dagster) | `1.13.29` | `1.13.30` |
| [dagster-webserver](https://github.com/dagster-io/dagster) | `1.13.29` | `1.13.30` |
| [numpy](https://github.com/numpy/numpy) | `2.5.4` | `2.5.5` |



Updates `kaleido` from 1.5.0 to 1.5.1
- [Release notes](https://github.com/plotly/kaleido/releases)
- [Changelog](https://github.com/plotly/kaleido/blob/main/CHANGELOG.md)
- [Commits](plotly/kaleido@v1.5.0...v1.5.1)

Updates `sphinx-design` from 0.7.0 to 0.8.0
- [Release notes](https://github.com/executablebooks/sphinx-design/releases)
- [Changelog](https://github.com/executablebooks/sphinx-design/blob/main/CHANGELOG.md)
- [Commits](executablebooks/sphinx-design@v0.7.0...v0.8.0)

Updates `pydantic-settings` from 2.16.2 to 2.16.3
- [Release notes](https://github.com/pydantic/pydantic-settings/releases)
- [Commits](pydantic/pydantic-settings@v2.16.2...v2.16.3)

Updates `dagster` from 1.13.29 to 1.13.30
- [Release notes](https://github.com/dagster-io/dagster/releases)
- [Changelog](https://github.com/dagster-io/dagster/blob/master/CHANGES.md)
- [Commits](dagster-io/dagster@1.13.29...1.13.30)

Updates `dagster-webserver` from 1.13.29 to 1.13.30
- [Release notes](https://github.com/dagster-io/dagster/releases)
- [Changelog](https://github.com/dagster-io/dagster/blob/master/CHANGES.md)
- [Commits](dagster-io/dagster@1.13.29...1.13.30)

Updates `numpy` from 2.5.4 to 2.5.5
- [Release notes](https://github.com/numpy/numpy/releases)
- [Changelog](https://github.com/numpy/numpy/blob/main/doc/RELEASE_WALKTHROUGH.rst)
- [Commits](numpy/numpy@v2.5.4...v2.5.5)

---
updated-dependencies:
- dependency-name: kaleido
  dependency-version: 1.5.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: python-versions
- dependency-name: sphinx-design
  dependency-version: 0.8.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: python-versions
- dependency-name: pydantic-settings
  dependency-version: 2.16.3
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: python-versions
- dependency-name: dagster
  dependency-version: 1.13.30
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: python-versions
- dependency-name: dagster-webserver
  dependency-version: 1.13.30
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: python-versions
- dependency-name: numpy
  dependency-version: 2.5.5
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: python-versions
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot requested a review from a team November 18, 2026 05:29
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file python:uv Pull requests that update python:uv code labels Nov 18, 2026
@sonarqubecloud

Copy link
Copy Markdown

This branch has not been deployed

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

Labels

dependencies Pull requests that update a dependency file python:uv Pull requests that update python:uv code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants