Repository navigation
Require canonical SMALL progress in LoopExec CI - #6
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.
LoopExec's public
.smallhistory fell behind its code releases because CI did not require the canonical ledger to change with development work. This PR makes source/documentation PRs and main pushes fail when they omit.small/progress.small.yml, then validates the tracked SMALL state with the pinned SMALL v1.1.0 binary. Consumers can still use LoopExec without SMALL.The safeguard is recorded as SMALL task 33 in the same commit. Local proof confirms that the historical v0.4.0 code diff fails the new gate, while a code diff with canonical progress and a SMALL-only diff pass.
small check --strictpasses under both local v1.0.7 and pinned v1.1.0; Gitleaks reports no leaks in.small.