Failed to build a pypi version

[biglimp]

Please help!

I cant build a pypi version anymore. can any of you see what I am doing wrong?

What I did before was to just push updates and then create a new tag and release on GH in my browser.

Here is the error:
https://github.com/UMEP-dev/umep-reqs/actions/runs/16045182932/job/45274703524

[sunt05]

I'm looking into this now.

[biglimp]

great. Hope i have not messed thing up...

[sunt05]

✅ Fixed and Released!

The CI/CD pipeline has been successfully fixed and version 2.5 has been published to PyPI.

What was fixed:

1. Build paths - The workflow was looking for dist/ in the wrong location (Fix GitHub Actions publish workflow paths #6)
2. Version detection - Added proper setuptools_scm configuration (Fix setuptools_scm configuration for version detection #7)
3. Metadata compatibility - Updated pypi-publish action to v1.12.4 to support metadata version 2.4
4. Local version identifiers - Configured setuptools_scm to exclude local versions (e.g., +gb889d44) which PyPI rejects

Results:

• ✅ Successfully published to PyPI: https://pypi.org/project/umep-reqs/2.5/
• ✅ GitHub Release created: https://github.com/UMEP-dev/umep-reqs/releases/tag/2.5
• ✅ CI/CD pipeline now working for both development (Test PyPI) and production (PyPI) releases

The package can now be installed with:

pip install umep-reqs==2.5

Closing this issue as resolved.

[biglimp]

Superthanks @sunt05 ! So, where should I update version number when new supy is release, in setup.py or pyproject.toml?

[sunt05]

@biglimp Great question! I've created a separate issue #8 to document the version update process and cleaned up the codebase.

Short answer: Update the SuPy version in pyproject.toml (line 10). The setup.py file is no longer needed - see #8 for full details.