-
Notifications
You must be signed in to change notification settings - Fork 0
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
Description
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 createsdistandwheel. - Validate metadata with
twine check.
- Use
-
Publishing
- Configure GitHub Actions to trigger PyPI uploads on tagged releases.
- Use
twine uploadwith GitHub Secrets for credentials (PYPI_API_TOKEN).
Acceptance Criteria
- Running
pip install ecliinstalls the package directly from PyPI. - The published package passes
twine checkvalidation. - 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.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.