gh-100538: Create a workflow for verifying bundled libexpat files#100539
gh-100538: Create a workflow for verifying bundled libexpat files#100539illia-v wants to merge 4 commits intopython:mainfrom
Conversation
|
You don't need news for build tools :) |
|
@sobolevn I removed the news entry |
| @@ -1,3 +1,7 @@ | |||
| /* Namespace external symbols to allow multiple libexpat version to | |||
There was a problem hiding this comment.
This one is should not be needed. It's already included below.
|
More generally, I'm not sure we actually need this step. Aren't we already doing this with SBOM checks? |
We aren't verifying that the files in the repository are the same as the ones in the release. |
|
I propose a simpler alternative: #145359 |
|
closing as the alternative PR merged. thanks though, this is a useful thing for us to have! |
Tags of libexpat releases are signed and GitHub runs a verification process on them.
I added a check of the verification status retrieved via GitHub's API. If the check succeeds, the script downloads a release source code and compares content of bundled files to the source.
Since a few lines are added to
Modules/expat/expat_external.h, I moved them to the top of the file and the script skips them.