Create a GitHub Actions workflow for verifying bundled libexpat files #100538
Copy link
Copy link
Closed
Labels
infraCI, GitHub Actions, buildbots, Dependabot, etc.CI, GitHub Actions, buildbots, Dependabot, etc.topic-XMLtype-featureA feature request or enhancementA feature request or enhancement
Description
Activity
- addedtype-featureA feature request or enhancementA feature request or enhancement
on Dec 26, 2022 - addedinfraCI, GitHub Actions, buildbots, Dependabot, etc.CI, GitHub Actions, buildbots, Dependabot, etc.
on Aug 17, 2025 thanks!
- added 3 commits that reference this issue
on Mar 2, 2026
Metadata
Metadata
Assignees
Labels
infraCI, GitHub Actions, buildbots, Dependabot, etc.CI, GitHub Actions, buildbots, Dependabot, etc.topic-XMLtype-featureA feature request or enhancementA feature request or enhancement
Feature or enhancement
A GitHub Actions workflow can be used to verify libexpat files bundled in CPython in
Modules/expat/.Pitch
When a new version of libexpat is released, someone usually creates a pull request to update its files bundled in CPython. Before merging it, a few people verify the change manually like in #98742.
An automatic test can be used for verifying the files during updates to reduce error proneness and speed up integration of new libexpat releases that fix security issues often.
We have a similar workflow for verifying bundled pip and setuptools wheels #91172.
Linked PRs