Repository navigation
Use the locked Komizo project recipe - #11
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.
Local verification and CI now use the project manifest and exact Komizo v0.2.2 lock. Existing caller-owned assertions are preserved, with the build/test order and supported operations declared in one place. This removes the Make/mise wrappers and retired bootstrap/profile files. Public documentation is a usage README generated from its private canonical source.
Validation: the released binary accepted the manifest/lock; actionlint and the private source, dependency and naming audit passed. Existing fixture/redirect and gate-control tests passed locally where applicable. Hosted checks must pass on this exact head before merge.
Need help on this PR? Tag
@codesmith-botwith what you need.