Repository navigation
Conversation
A package's "<pkg> riscv64 support" issue should move to "Available in RISE PyPI" in the Python Wheels project once its wheels are published. Doing it when update_doc.py opens the docs PR is too early: /simple/ is only regenerated by website.yml after that PR is merged. Add a sync-project-status job after website.yml's deploy that runs the new ci_scripts/sync_project_status.py. For every package in packages.txt it takes the oldest open issue and, unless its status is already "Available in RISE PyPI" or "Available Upstream", adds it to the project and sets the status. The issue stays open; only a deprecation closes it. It compares state instead of diffing the push, so runs dropped by the concurrency queue or failed runs are caught up by the next deploy. Move the issue and project helpers into ci_scripts/github_issues.py, shared by sync_project_status.py, check_versions.py and update_doc.py (REPO, normalize_name). check_versions.py's find_upstream_issue() now fetches the issues once per run and picks the oldest open issue whose title matches exactly, instead of the newest fuzzy search hit. The project is matched by node ID, since its title is "Python Wheels - riseproject-dev/python-wheels". Document the job, and drop the closing-keyword advice from the porting steps: the issue must stay open. Signed-off-by: Julien Stephan <jstephan@baylibre.com>
Collaborator
Author
|
Here is the output of the dry-run: Show full logThere are 471 issues to update Todo -> Available in RISE PyPI (updated during the very first run) and 467 packages without issues found (either no issues or malformed issues). The script does not create issues for the missing one. Human check needed |
justeph
requested review from
luhenry and
threexc
and removed request for
luhenry
October 26, 2026 16:00
threexc
approved these changes
Oct 26, 2026
Collaborator
|
LGTM, thanks for adding it. I ran with |
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A package's " riscv64 support" issue should move to "Available in RISE PyPI" in the Python Wheels project once its wheels are published. Doing it when update_doc.py opens the docs PR is too early: /simple/ is only regenerated by website.yml after that PR is merged.
Add a sync-project-status job after website.yml's deploy that runs the new ci_scripts/sync_project_status.py. For every package in packages.txt it takes the oldest open issue and, unless its status is already "Available in RISE PyPI" or "Available Upstream", adds it to the project and sets the status. The issue stays open; only a deprecation closes it. It compares state instead of diffing the push, so runs dropped by the concurrency queue or failed runs are caught up by the next deploy.
Move the issue and project helpers into ci_scripts/github_issues.py, shared by sync_project_status.py, check_versions.py and update_doc.py (REPO, normalize_name). check_versions.py's find_upstream_issue() now fetches the issues once per run and picks the oldest open issue whose title matches exactly, instead of the newest fuzzy search hit. The project is matched by node ID, since its title is "Python Wheels - riseproject-dev/python-wheels".
Document the job, and drop the closing-keyword advice from the porting steps: the issue must stay open.