| Filename | Latest commit message | Latest commit date |
|---|---|---|
|
Some checks failed
ci/crow/manual/reindex/2 Pipeline failed
ci/crow/manual/reindex/17 Pipeline failed
ci/crow/manual/reindex/13 Pipeline failed
ci/crow/manual/reindex/15 Pipeline failed
ci/crow/manual/reindex/11 Pipeline failed
ci/crow/manual/reindex/9 Pipeline failed
ci/crow/manual/reindex/7 Pipeline failed
ci/crow/manual/reindex/12 Pipeline failed
ci/crow/manual/reindex/10 Pipeline failed
ci/crow/manual/reindex/14 Pipeline failed
ci/crow/manual/reindex/1 Pipeline failed
ci/crow/manual/reindex/5 Pipeline failed
ci/crow/manual/reindex/3 Pipeline failed
ci/crow/manual/reindex/16 Pipeline failed
ci/crow/manual/reindex/18 Pipeline failed
ci/crow/manual/reindex/4 Pipeline failed
ci/crow/manual/reindex/6 Pipeline failed
ci/crow/manual/reindex/8 Pipeline failed
weekly-rebuild-reindex depends on weekly-rebuild-missing and shares its gate, so triggering it manually also starts hours of package rebuilds. That is the wrong tool when only the index needs regenerating: after a bincraft release that changes how the index is written, the objects in the bucket are already correct and only PACKAGES* is stale. This workflow does the index half alone. It installs the latest bincraft release, republishes the generic and per-R-minor indexes for each slot, and purges the edge. No package is built. |
||
| .. | ||
| archive-missed-packages.yaml | ||
| auto-apply-patches.yaml | ||
| build-all-versions-install-deps.yaml | ||
| build-all-versions.yaml | ||
| process-updates.yaml | ||
| reindex.yaml | ||
| repair-built-stamp.yaml | ||
| trial-build-registry.yaml | ||
| weekly-audit-missing.yaml | ||
| weekly-patch-proposals.yaml | ||
| weekly-rebuild-missing.yaml | ||
| weekly-rebuild-reindex.yaml | ||