Repository navigation
chore: remove unsupported Go CLI - #2915
Merged
Merged
Conversation
Contributor
✅ Tests passed: 2555/2558Ran 13 of 16 suites (3 not affected by this change).
|
Contributor
|
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
Remove the unsupported Go
browseros-cliapplication and its release pipeline. The repository no longer advertises or builds that client; the existing MCP servers and unrelated developer tools remain available.Remove the CLI package script, Fallow exclusion, env-migration special cases, analytics test examples, README/contributor references, and contributor-guidance links. Keep the shared analytics implementation and server entry points unchanged.
Evidence
Before: the Go app, publishing workflow, build/upload tooling, and runtime tests were present, and the README and contributing guide offered it as a supported path.
After: the requested recursive reference grep returns no matches in this checkout. An additional scan of README, contributor, and docs text confirms remaining CLI mentions refer to other tools.
bun installpassed; the lockfile is unchanged and matches the surviving workspace manifests.bun run checkpassed (lint, workspace typecheck, Fallow; existing non-fatal warnings remain).bun run testpassed: 2,108 passing, 0 failing, 3 skipped.bun test scripts/env/migrate-local.test.tspassed: 6 passing.bun run build:agentpassed.bun scripts/build/server.ts --target=darwin-arm64 --ci --no-uploadpassed.rustfmt --check --edition 2024 packages/browseros-agent/apps/claw-server/src/analytics/events.rsandgit diff --checkpassed.Independent
ft-code-reviewround completed; its one minor documentation finding was accepted and fixed. No unresolved findings.Docs and intentional historical references
The starting checkout already has no Go CLI pages, nav entries, images, or snippets under
docs/; repository docs history contains no such published pages either. No page URLs are removed by this PR, so there are no new redirects to add.docs/docs.jsonparses as JSON and all 34 navigation pages resolve.The uninitialized
.internal-docssubmodule was inspected through its pinned Git objects. Its sole intentional historical mention isarchitecture/rust-port/README.md:71-72, at pinned commitf04863b14e338267a5d7b3f6b2d8e6aed45dda41:apps/cli(Go) is cited as precedent for non-JS apps not needing apackage.json. That design history remains true; the submodule and gitlink are unchanged.Follow-ups for the owner
browseros-clinpm package. This PR does not deprecate or unpublish it. Its existing postinstall wrapper downloads versioned binaries and checksums from GitHub releases such ascli/v0.4.0; preserve those releases/tags/assets until an explicit retirement decision.https://cdn.browseros.com/cli/install.sh,/cli/install.ps1,/cli/latest/version.txt,/cli/latest/manifest.json, and versioned/cli/v0.4.0/*binaries/checksums. Old installs self-update from the latest manifest, and the hosted installers resolve the latest version and fetch those archives. Read-only GET checks confirm both installers and both latest metadata endpoints return HTTP 200, currently advertising 0.4.0 across six platform assets. Removing the release workflow stops future refreshes; this PR changes no hosted objects.Merge Danger
Door: two-way; the source deletion can be reverted in Git.
Blast Radius: building and publishing the unsupported Go client stops. Existing npm, GitHub, and CDN artifacts are unchanged; their eventual retirement is an owner follow-up.