Repository navigation
feat(keel-repin): repin shared kit and engine layers - #240
Merged
Merged
Conversation
Contributor
There was a problem hiding this comment.
Reviewed the kit/Keel tuple rewrite, engine hook flow, duplicate suppression and exact-head settlement. Shared-layer rewrites now preserve unrelated Keel release tags and comments; the added verified/weekly fixtures cover both engine hooks, lock and pin preservation, and owned failed-build drafts. Tests and ci-ok succeeded on this head. No blocking findings. The merge writer arms this same head through the normal merge path.
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 changed
Extend the existing keel-repin action with
layer: kitandlayer: engine, leaving the default verified Keel tag flow unchanged.Why
Shared kit and engine updates currently need hand-built consumer branches. Keeping them inside the existing repin action preserves the consumer's build and CI gates, while moving the kit's Keel pin together avoids a split Keel dependency graph.
Testing
git diff --check origin/main HEADpassed on the final head.python -m unittest discover -s testsremain for CI. The remote full-suite attempt could not acquire a machine within 120 seconds; the final repin-only attempt could not start because every workspace was in use. Neither attempt ran tests or returned a test failure.