-
Notifications
You must be signed in to change notification settings - Fork 0
Issue #30: Implement PyPI Publishing Workflow #6
Copy link
Copy link
Open
Labels
build-environmentIssues related to the build environment, Docker, CI/CD, and cross-platform compatibility.Issues related to the build environment, Docker, CI/CD, and cross-platform compatibility.enhancementNew feature or requestNew feature or requestpackagingIssues related to build scripts, installers, package managers (apt, rpm), Docker, and distribution.Issues related to build scripts, installers, package managers (apt, rpm), Docker, and distribution.
Milestone
Metadata
Metadata
Assignees
Labels
build-environmentIssues related to the build environment, Docker, CI/CD, and cross-platform compatibility.Issues related to the build environment, Docker, CI/CD, and cross-platform compatibility.enhancementNew feature or requestNew feature or requestpackagingIssues related to build scripts, installers, package managers (apt, rpm), Docker, and distribution.Issues related to build scripts, installers, package managers (apt, rpm), Docker, and distribution.
Problem Description
Currently, ECLI is distributed only as native system packages (
.deb,.rpm). Developers who rely onpip installand Python package registries cannot easily install it.Proposed Solution
Introduce an automated PyPI publishing workflow to distribute ECLI as a Python package.
Build Process
uv build(PEP 517/518 compliant) to createsdistandwheel.twine check.Publishing
twine uploadwith GitHub Secrets for credentials (PYPI_API_TOKEN).Acceptance Criteria
pip install ecliinstalls the package directly from PyPI.twine checkvalidation.