[WIP] Fix package upload error to PyPI due to bad request

[Copilot]

Summary

Fixed PyPI upload failure by addressing version conflict and workflow configuration issues.

Changes Made:

• Update version from 0.2.0 to 0.2.1 in pyproject.toml
• Update version in init.py to 0.2.1
• Fix CIBW_REPAIR_WHEEL_COMMAND to be Linux-specific (CIBW_REPAIR_WHEEL_COMMAND_LINUX)
• Verify Python version constraints in pyproject.toml (>=3.8,<3.13) - correct
• Verify workflow file has proper configuration with cibuildwheel
• Test build process locally - successful (built fastaccess-0.2.1.tar.gz)
• Run tests - all passed (31 passed, 5 skipped)
• Run code review - no issues found
• Run security scan - no vulnerabilities found

Root Cause:

The v0.2.0 release used an old workflow that built wheels with python -m build on Python 3.14, creating wheels with unsupported linux_x86_64 platform tags. PyPI requires proper manylinux tags and doesn't support Python 3.14 wheels yet.

Solution:

• Version bumped to 0.2.1 to avoid conflicts with existing v0.2.0 on PyPI
• Current workflow already uses cibuildwheel which will create proper manylinux-tagged wheels
• Workflow explicitly skips Python 3.14 builds and removes unsupported wheels before upload
• Fixed CIBW_REPAIR_WHEEL_COMMAND to be Linux-specific for proper auditwheel tagging

Security Summary:

No security vulnerabilities detected by CodeQL scan.

Original prompt

The job failed with an HTTPError 400 Bad Request when attempting to upload the wheel file fastaccess-0.2.0-cp314-cp314-linux_x86_64.whl to PyPI. This indicates the package does not meet PyPI's requirements.

The issue could stem from the following:

1. The package version already exists on PyPI. A new version number is required to resolve this.
2. The file name format might be invalid for the build process or targeting an unsupported Python version (e.g., Python 3.14 may have limited compatibility with PyPI).
3. There could be an issue with the project's metadata (e.g., name, version compatibility, or unallowed symbols).

Solution:

• Update the version to a new one in the setup.py or pyproject.toml (depending on your setup) to ensure it's unique.
• Ensure the build process supports a valid Python version compatible with PyPI rules.
• Validate and correct the metadata for compliance with PyPI standards.

Update the workflow file .github/workflows/python-publish.yml if there are necessary fixes such as setting supported Python versions.

This pull request was created from Copilot chat.

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.