Do not remove patch versions from Python Package Index

[marcorighini]

We have github-copilot-sdk python library version pinned to 0.2.2

The version disappeared from the Python Package Index causing the error

ERROR: Ignored the following yanked versions: 0.1.10rc2
ERROR: Could not find a version that satisfies the requirement github-copilot-sdk==0.2.2 (from versions: 0.1.10, 0.1.11, 0.1.12, 0.1.13rc0, 0.1.13, 0.1.14, 0.1.15rc0, 0.1.15, 0.1.16rc0, 0.1.16, 0.1.17, 0.1.18, 0.1.19, 0.1.20, 0.1.21, 0.1.22, 0.1.23rc0, 0.1.23rc1, 0.1.23, 0.1.24rc0, 0.1.24, 0.1.25rc0, 0.1.25, 0.1.26rc0, 0.1.28, 0.1.29, 0.1.30, 0.1.31, 0.1.32, 0.2.0, 0.2.3, 0.3.0rc0, 0.3.0rc1, 0.3.0, 1.0.0b1, 1.0.0b2, 1.0.0b3, 1.0.0b4, 1.0.0b5, 1.0.0b6)
ERROR: No matching distribution found for github-copilot-sdk==0.2.2

[github-actions]

Investigation findings

Label applied: bug

I investigated this issue by checking the GitHub releases and the CHANGELOG.

What I found

• v0.2.2 was a real, published release — the GitHub release exists (published 2026-04-10) with a full changelog entry covering several features (sessionFs cross-SDK, model capabilities override, enableConfigDiscovery, etc.).
• v0.2.1 was also a published release per the CHANGELOG.
• Both v0.2.1 and v0.2.2 are absent from PyPI — the available versions jump from 0.2.0 directly to 0.2.3, confirming both patch versions were removed from the package index after publication.
• The error message (Could not find a version that satisfies the requirement) indicates the packages were hard-deleted from PyPI, not just yanked. Yanked packages can still be installed when pinned explicitly; hard-deleted ones cannot.

Why this is a bug

Deleting published package versions from PyPI breaks any downstream consumer who has pinned to that version. PyPI's own policy discourages deletion precisely because of this. The correct remediation for a bad release is to yank the version (soft-delete), not delete it — yanked versions still satisfy exact-version pins (==0.2.2) while being excluded from unpinned resolution.

Recommended fix

1. Republish github-copilot-sdk==0.2.1 and github-copilot-sdk==0.2.2 to PyPI (if the release artifacts are still available), or document a migration path for users who had these versions pinned.
2. Update the release process to use pip install twine && twine upload --yank / PyPI's yank API instead of deleting versions in the future.

Generated by Bug Handler for issue #1374 · ● 1.9M · ◷

[ruoruyan]

We have github-copilot-sdk python library version pinned to 0.2.1 as well, will we republish this version?