Repository navigation
Author Harness native pins in the declaration and move shared code to its owners - #833
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.
Each Harness's native component name and version are authored once in
Declaration.Native. Go adapters and the CLI read them;scripts/native-pins.jsonis generated; every other projection (scripts, Dockerfiles, workflow, READMEs) is checked bymake check-harness-catalog, which names stale files. The catalog gains a native version column. Also movesinternal/agentnetworkinto Core, deletesbinpath(each adapter reads its own binary override), and drops theCLAUDE_CODE_GIT_BASH_PATHread from shared setup-script code.Need help on this PR? Tag
@codesmith-botwith what you need.