ci: read the registry state from docs/packages/<pkg>.yaml - #1939
Merged
Merged
Conversation
Contributor
|
The nightly check resolved our registry version with `pip index versions`,
which cannot see a package whose only wheels are prereleases or newer
Pythons than the one it queries, so every run since 2026-09-13 failed:
[X] ERRORS (5 packages):
fast-walk Could not get registry version
nodejs-wheel-binaries Could not get registry version
pyyaml-ft Could not get registry version
tinyobjloader Could not get registry version
vtk Could not get registry version
The YAML is the source of truth for what is released, so read it instead.
While there, `--declare` applies the outcome to the working tree (new
versions, `yanked: true`, deprecation) and the workflow commits it into
one rolling draft PR; `--since` declares every release in a time window;
versions upstream already ships riscv64 wheels for are skipped, and a
package is only deprecated once every gap before that point is built.
Signed-off-by: Ludovic Henry <git@ludovic.dev>
luhenry
force-pushed
the
yaml-driven-versions
branch
from
September 16, 2026 11:21
b769b08 to
04e34b5
Compare
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
1 participant
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.
The nightly check resolved our registry version with
pip index versions, which cannot see a package whose only wheels are prereleases or newer Pythons than the one it queries, so every run since 2026-09-13 failed:The YAML is the source of truth for what is released, so read it instead. While there,
--declareapplies the outcome to the working tree (new versions,yanked: true, deprecation) and the workflow commits it into one rolling draft PR;--sincedeclares every release in a time window; versions upstream already ships riscv64 wheels for are skipped, and a package is only deprecated once every gap before that point is built.