refactor(ci): skip bincraft reinstall when image already has it #72
Loading…
Reference in a new issue
No description provided.
Delete branch "pr/guard-bincraft-reinstall"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
bincraft is baked into the build-env images, but every workflow still unconditionally calls
pak::pak("git::.../bincraft.git")(~30–60s per job).Pin bincraft to a specific tag (currently
v4.0.2) and guard the install on a version check.git-tagsdatasource against the bincraft repo).Touches 43
.crowYAMLs +renovate.json.bincraft is baked into the build-env images, but every workflow run unconditionally called pak::pak("git::.../bincraft.git") to defend against bakes where the install silently failed. That cost ~30-60s per job (pak resolves Remotes, may recompile), which adds up across all process-updates, update-package-index, weekly-rebuild and archive-missed-packages workflows. Guard the call with requireNamespace(): healthy images skip the install entirely; broken images still self-heal.63b4a51b31to7d873eb07b7d873eb07bto7323ac1713