Bump rich-click from 1.8.9 to 1.9.0

[dependabot]

Bumps rich-click from 1.8.9 to 1.9.0.

Release notes

Sourced from rich-click's releases.

v1.9.0

[!WARNING] Version 1.9.0 deprecates support for a lot of old versions of things:

• Python 3.7 support is removed. The minimum supported Python version is 3.8.
• Click 7 support is removed. The minimum supported Click version is 8.0.
• Rich 10 and 11 support is removed. The minimum supported Rich version is 12.

[!WARNING] Version 1.9.0 introduces a minor breaking change: The DEFAULT_STRING, ENVVAR_STRING, REQUIRED_STRING, and DEPRECATED_STRING config options are now rendered with Text.from_markup. So for example, REQUIRED_STRING = "[required]" would be rendered as Rich markup. You must now escape the rich markup: REQUIRED_STRING = "\\[required]"

Big changes:

• Themes! Check them out with rich-click --themes.
• Typer support: rich-click typer_app --help.
• RichPanels API introduced. This replaces the "groups" feature going forward (although groups will continue to be supported).
  • @click.option_panel()
  • @click.command_panel()
• IDE tab completion support for decorators. Now you should no longer need to guess what goes in @click.option() or @click.command(context_settings=...) etc.
• Help for arguments: help= is now a valid kwarg for @click.argument() decorator. See docs for more information.

Small changes:

• "Deprecated" text properly handled and stylized in all places.
• Command aliases: @cli.command(aliases=["foo"])
• Improved rich-click CLI usability: improved patching and improved script detection+execution.
• context_settings={"help_to_stderr": True} support.
• Added suite of padding_* config options to control padding.
  • Better newline handling:
    • Unordered lists create newlines in help text, e.g. "\n- foo\n- bar" or "\n* foo\n* bar"
    • Newline control in help text with text_paragraph_linebreaks config option.
• Added a few text_* config options, including notably text_kwargs which can control code styles in Markdown.

Backend (mostly invisible) changes:

• Overhauled our test suite to use inline-snapshot! 😁
• Improved test coverage and CI.
• typing_extensions now only required for < Python 3.11.
• RichHelpFormatter now defers printing by default if a user does not specify a Console. [#231] (With contributions from @​ofek)
  • This more closely aligns the RichHelpFormatter with how base Click works.
• Significant refactors to help text rendering.
• Reintroduced deprecation warnings for a couple of features deprecated in 1.8.
• There was an issue where the rich.highlighter module could load during CLI execution. We now assert in unit-tests that no rich modules are loaded during code execution, so going forward, rich imports should no longer ever be a side-effect of CLI execution.

v1.9.0.dev6

[!WARNING] Version 1.9.0 deprecates support for a lot of old versions of things:

... (truncated)

Changelog

Sourced from rich-click's changelog.

Version 1.9.0 (2025-09-16)

[!WARNING] Version 1.9.0 deprecates support for a lot of old versions of things:

• Python 3.7 support is removed. The minimum supported Python version is 3.8.
• Click 7 support is removed. The minimum supported Click version is 8.0.
• Rich 10 and 11 support is removed. The minimum supported Rich version is 12.

[!WARNING] Version 1.9.0 introduces a minor breaking change: The DEFAULT_STRING, ENVVAR_STRING, REQUIRED_STRING, and DEPRECATED_STRING config options are now rendered with Text.from_markup. So for example, REQUIRED_STRING = "[required]" would be rendered as Rich markup. You must now escape the rich markup: REQUIRED_STRING = "\\[required]"

Big changes:

• Themes! Check them out with rich-click --themes.
• Typer support: rich-click typer_app --help.
• RichPanels API introduced. This replaces the "groups" feature going forward (although groups will continue to be supported).
  • @click.option_panel()
  • @click.command_panel()
• IDE tab completion support for decorators. Now you should no longer need to guess what goes in @click.option() or @click.command(context_settings=...) etc.
• Help for arguments: help= is now a valid kwarg for @click.argument() decorator. See docs for more information.

Small changes:

• "Deprecated" text properly handled and stylized in all places.
• Command aliases: @cli.command(aliases=["foo"])
• Improved rich-click CLI usability: improved patching and improved script detection+execution.
• context_settings={"help_to_stderr": True} support.
• Added suite of padding_* config options to control padding.
  • Better newline handling:
    • Unordered lists create newlines in help text, e.g. "\n- foo\n- bar" or "\n* foo\n* bar"
    • Newline control in help text with text_paragraph_linebreaks config option.
• Added a few text_* config options, including notably text_kwargs which can control code styles in Markdown.

Backend (mostly invisible) changes:

• Overhauled our test suite to use inline-snapshot! 😁
• Improved test coverage and CI.
• typing_extensions now only required for < Python 3.11.
• RichHelpFormatter now defers printing by default if a user does not specify a Console. [#231] (With contributions from @​ofek)
  • This more closely aligns the RichHelpFormatter with how base Click works.
• Significant refactors to help text rendering.
• Reintroduced deprecation warnings for a couple of features deprecated in 1.8.
• There was an issue where the rich.highlighter module could load during CLI execution. We now assert in unit-tests that no rich modules are loaded during code execution, so going forward, rich imports should no longer ever be a side-effect of CLI execution.

Commits

• e13aa75 push back 1 day
• e13d8f1 Merge pull request #289 from dwreeves/main
• 88dfa91 Merge pull request #290 from dwreeves/hotfix-devnull
• c9cafb3 should not be writing to devnull, should instead write to unused buffer
• e23f40d 1.9.0 full release
• 1a6c77a Merge pull request #287 from dwreeves/final-touches
• 2c7220d Merge branch 'final-touches' of github.com-dwreeves:dwreeves/rich-click into ...
• d6bd485 fix esptool
• 53b73a9 Generate new screengrabs with rich-codex
• e608f63 Additional clarity in docs
• 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 will merge this PR once CI passes on it, as requested by @rly0nheart.

---

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)

[rly0nheart]

@dependabot merge

[dependabot]

Superseded by #49.