chore: update Craig fork to latest upstream OpenClaw#5
Merged
Conversation
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
Updates the Merit OpenClaw fork to the latest upstream
openclaw/openclawmain commit (e311ffdcb9) and reapplies the Craig-specific runtime patches on top.Changes
9ff335a06) to upstreame311ffdcb9extensions/discordruntime layoutTest Plan
pnpm install --frozen-lockfilepnpm exec vitest run --config test/vitest/vitest.extension-discord.config.ts extensions/discord/src/send.sends-basic-channel-messages.test.tspnpm exec vitest run --config test/vitest/vitest.auto-reply-core.config.ts src/auto-reply/reply/agent-runner-memory.test.tspnpm buildOPENCLAW_CONFIG_PATH=/Users/samragsdale/Documents/Code/merit-systems/CraigClaw/deploy/openclaw.json node dist/index.js config validate --jsonAfter this merges, CraigClaw can bump
deploy/openclaw-pinto the merged fork commit in a separate PR.