Script 'mail_helper' called by obssrc
Hello community,

here is the log from the commit of package python-click-extra for 
openSUSE:Factory checked in at 2026-04-04 19:05:38
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/python-click-extra (Old)
 and      /work/SRC/openSUSE:Factory/.python-click-extra.new.21863 (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "python-click-extra"

Sat Apr  4 19:05:38 2026 rev:18 rq:1344510 version:7.10.0

Changes:
--------
--- /work/SRC/openSUSE:Factory/python-click-extra/python-click-extra.changes    
2026-03-11 20:51:59.649741255 +0100
+++ 
/work/SRC/openSUSE:Factory/.python-click-extra.new.21863/python-click-extra.changes
 2026-04-04 19:07:08.352440668 +0200
@@ -1,0 +2,85 @@
+Fri Apr  3 17:37:40 UTC 2026 - Dirk Müller <[email protected]>
+
+- update to 7.10.0:
+  * Highlight parent group names in subcommand help text, so
+    ancestor command names are colored even when interleaved with
+    options.
+  * Add `range_label`, `required`, and `argument` theme slots to
+    `HelpExtraTheme`. Argument metavars are now styled separately
+    from option metavars.
+  * Add `cross_ref_highlight` flag to `HelpExtraTheme`. Set to
+    `False` to disable free-text highlighting of options,
+    choices, arguments, metavars, and CLI names in descriptions
+    and docstrings. Structural elements (bracket fields,
+    deprecated messages, subcommand lists) are always styled.
+  * Add type-aware flattening, field metadata, and nested
+    dataclass support to `config_schema`. `flatten_config_keys()`
+    and `normalize_config_keys()` accept an `opaque_keys`
+    parameter to preserve data-keyed dicts. Fields support
+    `click_extra.config_path` and `click_extra.normalize_keys`
+    metadata. Nested dataclass fields are recursively
+    instantiated with the same normalize/flatten/opaque logic.
+  * Fix help text highlighting of hyphenated option names (e.g.
+    `--table-format` split at the first hyphen), argument names
+    (e.g. `keys`) colliding with option keywords, and substring
+    matches in compound keywords (e.g. `outline` inside `rounded-
+    outline`).
+  * Fix enum coloring: use `normalize_choice()` to produce the
+    exact strings shown in the metavar instead of raw enum member
+    names.
+
+-------------------------------------------------------------------
+Wed Apr  1 06:34:32 UTC 2026 - Johannes Kastl 
<[email protected]>
+
+- update to 7.9.0:
+  * Add flatten_config_keys() utility to flatten nested config
+    dicts into a single level by joining keys with a separator.
+  * Flatten nested config dicts before dataclass field matching in
+    config_schema, so nested TOML sub-tables (e.g.
+    [tool.myapp.sub-section]) map to flat dataclass fields (e.g.
+    sub_section_key).
+  * Add schema_strict parameter to ConfigOption and
+    ExtraCommand/ExtraGroup: when True, unknown config keys raise
+    ValueError during dataclass schema validation instead of being
+    silently dropped.
+  * Auto-discover pyproject.toml from the current working directory
+    upward to the VCS root before falling back to the app config
+    directory. Matches the discovery behavior of uv, ruff, and
+    mypy. Only active during auto-discovery (not when --config is
+    passed explicitly).
+  * Instantiate config_schema defaults when no config file is
+    found, so get_tool_config() never returns None when a schema is
+    configured.
+  * Forward included_params from ExtraCommand/ExtraGroup to
+    ConfigOption. Allows @group(included_params=()) to disable
+    merge_default_map when config keys are schema-only and would
+    collide with subcommand names.
+  * Move prebake_version(), prebake_dunder(), and
+    discover_package_init_files() from ExtraVersionOption static
+    methods to module-level functions in click_extra.version.
+    Import them directly: from click_extra.version import
+    prebake_version.
+  * Add git_tag template field. Resolved from a __git_tag__ dunder
+    or git describe --tags --exact-match HEAD at runtime. Returns
+    the tag name if HEAD is at a tagged commit.
+  * Add git_tag_sha template field. Resolved from a __git_tag_sha__
+    dunder on the CLI module, with a git subprocess fallback.
+    Replaces the old __tag_sha__ convention.
+  * Git template fields (git_branch, git_long_hash, git_short_hash,
+    git_date) now check for pre-baked __<field>__ dunders on the
+    CLI module before falling back to subprocess calls. Enables
+    compiled binaries (Nuitka/PyInstaller) to embed git metadata at
+    build time.
+  * Add click-extra prebake CLI with three subcommands: prebake all
+    bakes __version__ and all git fields in one pass, prebake
+    version injects Git hashes into __version__, and prebake field
+    replaces any empty dunder variable. Field names auto-wrap with
+    __...__ (e.g. git_tag_sha becomes __git_tag_sha__). All
+    subcommands auto-discover target files from [project.scripts].
+  * Add empty __git_*__ dunder placeholders to
+    click_extra/__init__.py for dogfooding the prebake system.
+  * Pin image URLs in readme.md and docs/tutorial.md to the release
+    tag at bump time, and restore them to main on the next dev
+    bump.
+
+-------------------------------------------------------------------

Old:
----
  click-extra-7.8.0.tar.gz

New:
----
  click-extra-7.10.0.tar.gz

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Other differences:
------------------
++++++ python-click-extra.spec ++++++
--- /var/tmp/diff_new_pack.M1eKTj/_old  2026-04-04 19:07:08.888462645 +0200
+++ /var/tmp/diff_new_pack.M1eKTj/_new  2026-04-04 19:07:08.888462645 +0200
@@ -28,7 +28,7 @@
 
 %{?sle15_python_module_pythons}
 Name:           python-click-extra
-Version:        7.8.0
+Version:        7.10.0
 Release:        0
 Summary:        Drop-in replacement for Click to make user-friendly and 
colorful CLI
 License:        GPL-2.0-or-later

++++++ click-extra-7.8.0.tar.gz -> click-extra-7.10.0.tar.gz ++++++
++++ 9697 lines of diff (skipped)

Reply via email to