docs(contributing): update minimum Go version to match go.mod - #370
Open
awdemos wants to merge 19 commits into
Open
docs(contributing): update minimum Go version to match go.mod#370awdemos wants to merge 19 commits into
awdemos wants to merge 19 commits into
Conversation
- remove the nix goreleaser publisher (requires a separate awdemos/nix repo and a PAT; revisit later if nix packaging is wanted) - use the workflow's built-in GITHUB_TOKEN (already has contents:write) instead of a RELEASE_GITHUB_TOKEN PAT secret that was never configured
targets a non-existent awdemos/homebrew-tap repo, needs a PAT the built-in GITHUB_TOKEN can't provide, and uses the deprecated homebrew_casks.binary property. GitHub Releases artifacts only for now.
point users at this repo's releases and issues instead of upstream
This reverts commit 4de3a30.
install.sh hardcoded REPO=dagger/container-use, so the documented install path fetched upstream binaries instead of this repo's releases. Also updates docs/quickstart, agent-integrations, introduction, docs.json and README to reference awdemos/container-use. Note: the 'brew install dagger/tap/container-use' line still points at upstream's tap intentionally - this fork does not publish a homebrew tap (dropped in the release simplification).
) When a client advertises the roots capability, request its roots after initialization (and on roots/list_changed) and include them in the error message when a repository fails to open. Agents frequently pass a wrong environment_source; the client roots give a concrete hint about which repositories are actually available. Ported from the stale minimal-roots-support branch, modernized for mcp-go v0.57: uses the proper MCPServer.RequestRoots request/response API instead of the notification hack. The request runs detached from the triggering message's context (it is canceled when the message finishes processing) with a 30s timeout, in a goroutine so the initialize handshake and stdio read loop never block. Co-authored-by: Sisyphus <clio-agent@sisyphuslabs.ai>
…hooks (#5) Ported from the stale project-git-config branch and rebased onto current main by hand. Two related robustness fixes: 1. The fork repo (~/.config/container-use/repos/...) now includes the user repo's .git/config via include.path, so project-level git configuration (user.name/user.email, etc.) applies to container-use commits and later config changes are picked up dynamically. Existing fork repos get the directive added on next open. commit.gpgsign is explicitly disabled in the fork since container-use commits are automated and often headless. 2. All git operations container-use performs in the user repository (push to the container-use remote, checkout/merge/apply) and in worktrees (commits) now run with -c core.hooksPath=/dev/null, so the user repo's hooks (pre-push test suites, commit linters, ...) never fire on container-use's own operations. Includes the branch's integration tests covering config inheritance, precedence, dynamic updates, existing fork repos, and hook suppression. Co-authored-by: Sisyphus <clio-agent@sisyphuslabs.ai>
Agents had no way to inspect an environment's history or cumulative changes through MCP; the only path was telling the user to run `cu log`/`cu diff`. These two tools wrap the existing repository Log/Diff (already covered by integration tests) via a lightweight openEnvironmentTarget helper that resolves repo + env ID without loading the environment container. Ported from the stale mcp-log-diff branch, minimized: no Log/Diff signature changes (the branch's extra branch-comparison param dropped), adapted to main's createTools/single-tenant structure. Co-authored-by: Sisyphus <clio-agent@sisyphuslabs.ai>
…nBackground and startService
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
2 participants
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.
The contribution guide stated Go 1.21, but go.mod requires Go 1.26.1. Update the documented minimum so new contributors use a compatible toolchain.