Repository navigation
chore: bump pitchfork and Node.js, scope pitchfork MCP to the project - #8264
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
disintegrator
marked this pull request as ready for review
October 29, 2026 12:36
disintegrator
added
the
review:bypass
![gram-bot[bot]](https://avatars.githubusercontent.com/in/1956617?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Auto-approved: review:bypass label applied by @disintegrator. Required status checks still gate this merge.
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
disintegrator
changed the title
disintegrator
enabled auto-merge
October 29, 2026 12:48
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
disintegrator
changed the title
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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
pitchforkfrom 2.22.0 to 2.32.4 inmise.toml, with refreshed checksums and release URLs inmise.lockfor every platform.pitchfork mcp --localin every harness config:.mcp.json(Claude Code, and Cursor through the.cursor/mcp.jsonsymlink),.codex/config.toml, andopencode.json.pitchforkskill so it says the MCP tools are scoped to the current project and points to the CLI for other projects.mise.tomland.node-version, and relock every platform. Lockfile checksums match the publishedSHASUMS256.txt.linux-arm64-musllock entry goes back to the prebuilt unofficial-builds tarball instead of building from source. chore: update runtimes and production CA trust stores #7815 locked it before that tarball was published.Motivation
Each worktree runs its own stack under one shared pitchfork supervisor. Without
--local, an agent's MCP server sees and can start, stop, or restart daemons from every worktree on the machine.--local(new in 2.32.x) limits it to the project of the agent's working directory. Requests for daemons in another project return an error, and a start or restart can no longer reach another project through a dependency.The Node patch bump keeps the local toolchain on the current LTS release.
🤖 Generated with Claude Code