shadcn-qt

Appearance

Publishing to PyPI ​

This repository publishes as shadcn-qt, while Python uses import shadcn_qt. The distribution and import names are the only supported public names. The runtime requires Python 3.9 or newer; the CI matrix covers Python 3.9, 3.11, and 3.13.

Version 0.2.6 is published at PyPI. Its initial project registration for version 0.1.0 used an authorized local API token after the complete release checks and an isolated installation test. Version 0.2.0 was likewise published with uv publish and the existing scoped token after the full release workflow validated its tests and artifacts; clean PySide6 and PyQt6 installs were then verified from the production index. Versions 0.2.1 through 0.2.5 follow the same direct, maintainer-approved uv publish fallback. Version 0.2.6 aligns Core and adopted native combo popup rows with the 32px new-york minimum while preserving larger application-defined rows and custom delegate behavior.

GitHub Actions releases use environment-scoped PyPI credentials:

  1. configure protected GitHub environments testpypi and pypi;
  2. set PYPI_USERNAME as an environment variable and PYPI_API_TOKEN as an environment secret in each environment, using credentials for the matching package index;
  3. run the manual TestPyPI workflow;
  4. update the matching versions in packages/python/pyproject.toml and packages/cpp/shadcn_qt/CMakeLists.txt, then tag exactly v<version>;
  5. approve the protected pypi deployment after tests and artifact checks.

An explicitly maintainer-approved direct production release may instead use uv publish with UV_PUBLISH_TOKEN when GitHub Actions is unavailable. Never print the token or pass it as a command-line argument.

The workflow validates GPL/commercial metadata and confirms that all license files are inside both the wheel and sdist. See the repository's docs/PYPI_RELEASE.md for one-time setup, commands, verification, and recovery.

Publisher metadata is configured for Felorx. Keep https://github.com/felorx/shadcn-qt public, configure its protected environments before the next release, and replace the temporary Felorx homepage commercial link when a dedicated sales page is available.