docs: clean mentions of go-ipfs-api, go-ipfs-http-api

.github/workflows/build.yml

@@ -94,43 +94,6 @@ jobs:
         working-directory: interop/packages/interop
         env:
           KUBO_BINARY: ${{ github.workspace }}/cmd/ipfs/ipfs
-  go-ipfs-api:
-    needs: [interop-prep]
-    runs-on: ubuntu-latest
-    timeout-minutes: 5
-    env:
-      TEST_DOCKER: 0
-      TEST_FUSE: 0
-      TEST_VERBOSE: 1
-      TRAVIS: 1
-      GIT_PAGER: cat
-      IPFS_CHECK_RCMGR_DEFAULTS: 1
-    defaults:
-      run:
-        shell: bash
-    steps:
-      - uses: actions/setup-go@v4
-        with:
-          go-version: ${{ env.GO_VERSION }}
-      - uses: actions/download-artifact@v3
-        with:
-          name: kubo
-          path: cmd/ipfs
-      - run: chmod +x cmd/ipfs/ipfs
-      - uses: actions/checkout@v4
-        with:
-          repository: ipfs/go-ipfs-api
-          path: go-ipfs-api
-      - run: cmd/ipfs/ipfs daemon --init --enable-namesys-pubsub &
-      - run: |
-          while ! cmd/ipfs/ipfs id --api=/ip4/127.0.0.1/tcp/5001 2>/dev/null; do
-            sleep 1
-          done
-        timeout-minutes: 5
-      - run: go test -count=1 -v ./...
-        working-directory: go-ipfs-api
-      - run: cmd/ipfs/ipfs shutdown
-        if: always()
   ipfs-webui:
     needs: [interop-prep]
     runs-on: ${{ fromJSON(github.repository == 'ipfs/kubo' && '["self-hosted", "linux", "x64", "2xlarge"]' || '"ubuntu-latest"') }}

core/coreapi/coreapi.go

@@ -1,15 +1,12 @@
 /*
+**NOTE: this package is experimental.**
+
 Package coreapi provides direct access to the core commands in IPFS. If you are
 embedding IPFS directly in your Go program, this package is the public
 interface you should use to read and write files or otherwise control IPFS.
 
-If you are running IPFS as a separate process, you should use `go-ipfs-api` to
-work with it via HTTP. As we finalize the interfaces here, `go-ipfs-api` will
-transparently adopt them so you can use the same code with either package.
-
-**NOTE: this package is experimental.** `go-ipfs` has mainly been developed
-as a standalone application and library-style use of this package is still new.
-Interfaces here aren't yet completely stable.
+If you are running IPFS as a separate process, you should use `client/rpc` to
+work with it via HTTP.
 */
 package coreapi
 

docs/http-rpc-clients.md

@@ -2,12 +2,6 @@
 
 Kubo provides official HTTP RPC  (`/api/v0`) clients for selected languages:
 
-- [`js-kubo-rpc-client`](https://github.com/ipfs/js-kubo-rpc-client) - Official JS client for talking to Kubo RPC over HTTP
-- [`go-ipfs-api`](https://github.com/ipfs/go-ipfs-api) - The go interface to ipfs's HTTP RPC - Follow https://github.com/ipfs/kubo/issues/9124 for coming changes.
-- [`httpapi`](./client/rpc) (previously `go-ipfs-http-client`) - [`coreiface.CoreAPI`](https://pkg.go.dev/github.com/ipfs/boxo/coreiface#CoreAPI) implementation using HTTP RPC
-
-## Recommended clients
-
 | Language |     Package Name    | Github Repository                          |
 |:--------:|:-------------------:|--------------------------------------------|
 | JS       | kubo-rpc-client     | https://github.com/ipfs/js-kubo-rpc-client |