Skip to content

feat: Distinguish file-level vs release-level yanking (PEP 592) #13784

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Ashutosh0x wants to merge 9 commits into
base: main
Choose a base branch
from
+305 −8

Shorten news fragment for PEP 592 yanking

68fb326
Select commit
Loading
Failed to load commit list.
Open

feat: Distinguish file-level vs release-level yanking (PEP 592) #13784

Shorten news fragment for PEP 592 yanking
68fb326
Select commit
Loading
Failed to load commit list.
PSF Chronographer / Changelog entry succeeded Feb 1, 2026 in 2s

Chronographer: Good to go

Great! This change has been recorded to the chronicles

You are good at keeping records! Image source: Unsplash ID=bByhWydZLW0

See https://pip.pypa.io/dev/news-entry-failure for details.

Please, refer to the following document for more details on how to
craft a great change note for inclusion with your pull request:
https://pip.pypa.io/dev/news-entry-failure

Details

The following news fragments found: [<PatchedFile: news/13755.feature.rst>]

Pattern: re.compile('news/(?P<issue_number>[^\\./]+)\.(?P<fragment_type>removal|feature|bugfix|vendor|doc|process|trivial)(\.\d+)?(\.[^\\./]+)*\.rst$')

View more details on PSF Chronographer