Skip to content

Issue #30: Implement PyPI Publishing Workflow #6

@SSobol77

Description

@SSobol77

Problem Description

Currently, ECLI is distributed only as native system packages (.deb, .rpm). Developers who rely on pip install and Python package registries cannot easily install it.

Proposed Solution

Introduce an automated PyPI publishing workflow to distribute ECLI as a Python package.

  • Build Process

    • Use uv build (PEP 517/518 compliant) to create sdist and wheel.
    • Validate metadata with twine check.
  • Publishing

    • Configure GitHub Actions to trigger PyPI uploads on tagged releases.
    • Use twine upload with GitHub Secrets for credentials (PYPI_API_TOKEN).

Acceptance Criteria

  • Running pip install ecli installs the package directly from PyPI.
  • The published package passes twine check validation.
  • PyPI and system packaging workflows remain independent but consistent.

Metadata

Metadata

Assignees

Labels

build-environmentIssues related to the build environment, Docker, CI/CD, and cross-platform compatibility.enhancementNew feature or requestpackagingIssues related to build scripts, installers, package managers (apt, rpm), Docker, and distribution.

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions