Chore(deps): Bump textual from 0.73 to 6.4.0#413
Conversation
Bumps [textual](https://github.com/Textualize/textual) from 0.73 to 6.4.0. - [Release notes](https://github.com/Textualize/textual/releases) - [Changelog](https://github.com/Textualize/textual/blob/main/CHANGELOG.md) - [Commits](Textualize/textual@v0.73.0...v6.4.0) --- updated-dependencies: - dependency-name: textual dependency-version: 6.4.0 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
|
Failed to retrieve llama text: Invalid URL '/completion': No scheme supplied. Perhaps you meant https:///completion? |
foxpatch-aleph
left a comment
foxpatch-aleph
left a comment
There was a problem hiding this comment.
This is a straightforward dependency bump from textual 0.73 to 6.4.0 — a major version jump. The change itself is mechanically correct, but the major version bump (0.73 → 6.4.0) spans many breaking changes in textual's API (widget lifecycle, CSS, component model). Without evidence that the project's textual-based UI code has been tested or updated for compatibility, this carries risk. The PR should ideally include verification that the TUI still works correctly after this upgrade.
pyproject.toml (line 45): This is a major version bump (0.73 → 6.4.0) that spans multiple breaking releases. Textual has made significant API changes across these versions (e.g., widget arrangement API, hover pseudo-class behavior, CSS rule changes). The diff only updates the version pin but provides no evidence that the TUI code was tested or adapted. It would be worth confirming the TUI works end-to-end after this upgrade, or noting that no textual features beyond basic usage are exercised.
foxpatch-aleph
left a comment
foxpatch-aleph
left a comment
There was a problem hiding this comment.
This is a straightforward dependency bump from textual 0.73 to 6.4.0, a major version jump. The change itself is correct, but the version constraint uses an exact pin (==6.4.0) rather than a compatible release specifier, which is consistent with the existing pinning style in pyproject.toml. The main concern is that this is a large version jump (0.73 → 6.4.0) that likely includes breaking changes in the textual API — the project's TUI code should be verified for compatibility. Additionally, textual 6.3.0 dropped Python 3.8 support, which may affect the project's supported Python range.
pyproject.toml (line 45): This is a major version bump (0.73 → 6.4.0). Textual has historically made breaking API changes between major versions. The project's TUI/interactive code that imports from textual should be audited for compatibility — widget APIs, CSS property names, and event handling interfaces changed significantly across these versions. CI passing is the key signal here, but if there are no TUI-specific tests, breakage may not be caught automatically.
pyproject.toml (line 45): Textual 6.3.0 dropped Python 3.8 support. If this project still targets Python 3.8, this constraint will conflict with that support matrix. Check the project's python_requires or CI matrix to ensure alignment.
foxpatch-aleph
left a comment
foxpatch-aleph
left a comment
There was a problem hiding this comment.
This is a straightforward dependency bump from textual 0.73 to 6.4.0. The change is minimal (one line in pyproject.toml) and represents a major version upgrade of the textual TUI library. While this is a large version jump, textual 6.x dropped Python 3.8 support and added Python 3.14 support, which aligns with modern Python support. The upgrade brings bug fixes and improvements. The main risk would be breaking changes in the textual API between 0.73 and 6.x, but since this is a dependency bump PR from Dependabot, the CI should catch any compatibility issues. The change itself is correct and the pinned version (==6.4.0) follows the existing versioning convention in the project.
pyproject.toml (line 45): This is a major version bump (0.73 → 6.4.0). The textual library had significant API changes across major versions. Verify that any code in this repo using textual's API (TUI components, widgets, etc.) is compatible with 6.x. In particular, check for usage of deprecated or removed APIs from the 1.x–6.x migration path.
1 participant
Bumps textual from 0.73 to 6.4.0.
Release notes
Sourced from textual's releases.
... (truncated)
Changelog
Sourced from textual's changelog.
... (truncated)
Commits
3427dbaMerge pull request #6188 from Textualize/bump640cd7d2dcbump0a6f0fcMerge pull request #6161 from TomJGooding/ci-bump-codeql-action-to-v33e04ac3Merge pull request #6163 from Tom-Newton/tomnewton/avoid_circular_dependencyacbc319Merge branch 'main' into tomnewton/avoid_circular_dependencyb801c15Merge pull request #6182 from samueldg/fix-manager-class-typos45475d5Merge pull request #6186 from Textualize/select-cells-fix8498718simplify cell selectionc3e72edtext selection test8bc1c65fix for selecting cellsYou can trigger a rebase of this PR by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)