Verify dep installers - #35
Merged
Merged
Conversation
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.
What
Dependency-installer recipe gate — the real-install tier of the installer CI.
.github/workflows/installer-recipes.yml— scheduled (weekly) matrix, one row per installer. For each installer it runs everyregistry/deps.tomlrecipe in a native environment and asserts the dep's declared binaries land on PATH. Opens a tracking issue on failure (labelinstaller-recipes)..github/scripts/verify_installers.py— registry-driven driver: discovers recipes fromdeps.toml(no hardcoding), mirrorsInstaller::command()for rendering, checks PATH + tool-managed bin dirs.Complements the PR gate (
cargo test→catalog.rs, which proves recipes parse): this proves they still work against the live world (renamed package, moved install script, formula rename).Related issues
Merge after #34. This branch is cut from
add-scalus, so until #34 lands its diff still carries the Scalus changes. Rebase ontomainafter #34 merges, then merge — the diff should reduce to just the two files above.Deferred (documented in the workflow header)
dnf/pacman(no recipes yet),winget/powershell(Windows), andcurl(interactive download-and-run scripts) are intentionally excluded so a green run stays meaningful — see #36.