Fix source-linked upgrades and MCP array schema#907
Open
ArshyaAI wants to merge 1 commit into
Open
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.
Summary
git pull --ff-onlywith explicit clean-worktree fetch/merge handling for tracked, no-tracking, fast-forward, and clean custom-branch merge casesexecFileSyncarray args and surface the actual auto-upgrade error before manual recovery guidanceitems: { type: 'string' }schema forextract_facts.entity_hintsso OpenAI-compatible function schema validation accepts the MCP tool definitionTests
bun install --frozen-lockfilebun run typecheckbun test test/mcp-tool-defs.test.ts test/upgrade.test.tsHOME=/private/tmp/gbrain-test-home bun run test(repo tests write to~/.gbrain, so HOME is redirected to writable temp space)Need help on this PR? Tag
@codesmithwith what you need.