Repository navigation
Harden dependency and build workflows - #15
Merged
Merged
Conversation
This was referenced Aug 25, 2026
Sunday111
force-pushed
the
harden-dependency-and-build-workflows
branch
2 times, most recently
from
August 26, 2026 16:22
ada4120 to
0e449c6
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.
Makes binary dependency installation atomic and confined, centralizes staged-content ownership, and rejects invalid module/build configuration before generation. Also aligns generated CMake, CUDA toolchains, repository discovery, and documented runtime requirements.\n\nDepends on Sunday111/yae-support#11 because generated builds invoke the updated staging script.