Skip to content

Conversation

@dependabot
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Oct 21, 2025

Updates the requirements on typer to permit the latest version.

Release notes

Sourced from typer's releases.

0.20.0

Features

Upgrades

Internal

Changelog

Sourced from typer's changelog.

0.20.0

Features

Upgrades

Internal

0.19.2

Fixes

  • 🐛 Fix list convertor with an empty list default factory . PR #1350 by @​svlandeg.

Refactors

Internal

0.19.1

Note: this is the last version to support Python 3.7, going forward Typer will require Python 3.8+. And soon Python 3.8 will also be dropped as Python 3.8 reached it's end of life almost a year ago.

Fixes

... (truncated)

Commits
  • 1b74bfe 🔖 Release version 0.20.0
  • e9ee0e7 📝 Update release notes
  • f6718b8 ✨ Enable command suggestions on typo by default (#1371)
  • ffbaed5 📝 Update release notes
  • 9e4764d ⬆️ Add support for Python 3.14 (#1372)
  • a06eb77 📝 Update release notes
  • 6cd1a9e 👷 Add nightly workflow to run tests against CPython main branch (#1374)
  • 9f38ada 📝 Update release notes
  • e0ca377 ⬆ Bump mkdocs-material from 9.6.21 to 9.6.22 (#1377)
  • dc2fd89 📝 Update release notes
  • Additional commits viewable in compare view

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 merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

@dependabot dependabot bot added the development Tech debt, refactors, CI, tests, and other related work. label Oct 21, 2025
@desertaxle
Copy link
Member

@claude can you run uv sync for this branch to update uv.lock for the new typer version?

@claude
Copy link

claude bot commented Oct 21, 2025

Claude finished @desertaxle's task —— View job


Task: Update uv.lock for typer version bump

  • Check repository setup instructions
  • Attempted to run uv sync to update lock file
  • Diagnosed circular dependency issue

Issue Found

I encountered a circular dependency resolution error when attempting to run uv sync or uv lock --upgrade-package typer. The error occurs because:

  1. The project is named prefect and includes an optional dependency prefect[aws]
  2. prefect[aws] depends on prefect-aws>=0.5.8
  3. prefect-aws itself depends on prefect, creating a circular dependency
  4. uv's dependency resolver cannot handle this circular dependency, especially when resolving for Python 3.13

The error message:

× No solution found when resolving dependencies for split (markers: python_full_version == '3.13.*'):
  ╰─▶ Because prefect[aws] depends on prefect-aws>=0.5.8 and prefect-aws depends on your project,
      your project's requirements are unsatisfiable.
      
      hint: The package `prefect-aws` depends on the package `prefect` but
      the name is shadowed by your project.

Attempted Solutions

I tried several approaches:

  • uv sync - Failed with circular dependency error
  • uv lock --upgrade-package typer - Failed with same error
  • uv lock --prerelease=allow - Failed with same error
  • Temporarily excluding Python 3.13 - Still failed
  • Various uv flags (--no-sources, --no-build-isolation) - All failed

Next Steps

This appears to be a known limitation with uv's handling of workspace dependencies and circular references. The issue needs to be resolved either by:

  1. Upgrading to a newer version of uv that handles this case better (current version: 0.9.4, but the pyproject requires >=0.6.15)
  2. Restructuring the project dependencies to avoid the circular reference
  3. Waiting for a fix in uv itself

The pyproject.toml has been successfully updated with the new typer constraint (>=0.12.0,!=0.12.2,<0.21.0), but the lock file cannot be regenerated until this circular dependency issue is resolved.

Would you like me to investigate alternative approaches or would you prefer to handle the lock file update manually/via a different method?


Job Run | Branch

Updates the requirements on [typer](https://github.com/fastapi/typer) to permit the latest version.
- [Release notes](https://github.com/fastapi/typer/releases)
- [Changelog](https://github.com/fastapi/typer/blob/master/docs/release-notes.md)
- [Commits](fastapi/typer@0.12.0...0.20.0)

---
updated-dependencies:
- dependency-name: typer
  dependency-version: 0.20.0
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot force-pushed the dependabot/pip/typer-gte-0.12.0-and-neq-0.12.2-and-lt-0.21.0 branch from 033da10 to b1d5302 Compare October 23, 2025 20:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

development Tech debt, refactors, CI, tests, and other related work.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants