Update scripts to refer to the new cli staging repo

On-behalf-of: @SAP [email protected]
Signed-off-by: Marko Mudrinić <[email protected]>

Author: xmudrii

.goreleaser.yaml

@@ -18,7 +18,7 @@ builds:
 # plugin builds
 - id: "kubectl-kcp"
   main: ./cmd/kubectl-kcp
-  dir: cli
+  dir: staging/src/github.com/kcp-dev/cli
   binary: bin/kubectl-kcp
   ldflags:
   - "{{ .Env.LDFLAGS }}"
@@ -34,7 +34,7 @@ builds:
 
 - id: "kubectl-ws"
   main: ./cmd/kubectl-ws
-  dir: cli
+  dir: staging/src/github.com/kcp-dev/cli
   binary: bin/kubectl-ws
   ldflags:
   - "{{ .Env.LDFLAGS }}"
@@ -50,7 +50,7 @@ builds:
 
 - id: "kubectl-create-workspace"
   main: ./cmd/kubectl-create-workspace
-  dir: cli
+  dir: staging/src/github.com/kcp-dev/cli
   binary: bin/kubectl-create-workspace
   ldflags:
   - "{{ .Env.LDFLAGS }}"
@@ -66,7 +66,7 @@ builds:
 
 - id: apigen
   main: ./cmd/apigen
-  dir: sdk
+  dir: staging/src/github.com/kcp-dev/sdk
   binary: bin/apigen
   ldflags:
   - "{{ .Env.LDFLAGS }}"

Dockerfile

@@ -28,10 +28,10 @@ ENV GOPROXY=$goproxy
 # Copy the Go Modules manifests
 COPY go.mod go.mod
 COPY go.sum go.sum
-COPY cli/go.mod cli/go.mod
-COPY cli/go.sum cli/go.sum
 COPY staging/src/github.com/kcp-dev/apimachinery/go.mod staging/src/github.com/kcp-dev/apimachinery/go.mod
 COPY staging/src/github.com/kcp-dev/apimachinery/go.sum staging/src/github.com/kcp-dev/apimachinery/go.sum
+COPY staging/src/github.com/kcp-dev/cli/go.mod staging/src/github.com/kcp-dev/cli/go.mod
+COPY staging/src/github.com/kcp-dev/cli/go.sum staging/src/github.com/kcp-dev/cli/go.sum
 COPY staging/src/github.com/kcp-dev/client-go/go.mod staging/src/github.com/kcp-dev/client-go/go.mod
 COPY staging/src/github.com/kcp-dev/client-go/go.sum staging/src/github.com/kcp-dev/client-go/go.sum
 COPY staging/src/github.com/kcp-dev/code-generator/go.mod staging/src/github.com/kcp-dev/code-generator/go.mod

FAQ.md

@@ -67,5 +67,5 @@ Shards in kcp represent a single apiserver and etcd/db instance.  This is how kc
 
 ## Where can I get the kubectl ws plugin?
 
-You're in the right place. Clone this repo and run `make install WHAT=./cli/cmd/kubectl-kcp`.
+You're in the right place. Clone this repo and run `make install WHAT=./staging/src/github.com/kcp-dev/cli/cmd/kubectl-kcp`.
 

Makefile

@@ -106,7 +106,7 @@ ldflags:
 require-%:
 	@if ! command -v $* 1> /dev/null 2>&1; then echo "$* not found in ${PATH}"; exit 1; fi
 
-build: WHAT ?= ./cmd/... ./cli/cmd/... ./staging/src/github.com/kcp-dev/sdk/cmd/...
+build: WHAT ?= ./cmd/... ./staging/src/github.com/kcp-dev/cli/cmd/... ./staging/src/github.com/kcp-dev/sdk/cmd/...
 build: require-jq require-go require-git verify-go-versions ## Build the project
 	set -x; for W in $(WHAT); do \
 		pushd . && cd $${W%..}; \
@@ -119,7 +119,7 @@ build: require-jq require-go require-git verify-go-versions ## Build the project
 build-all:
 	GOOS=$(OS) GOARCH=$(ARCH) $(MAKE) build WHAT='./cmd/...'
 
-install: WHAT ?= ./cmd/... ./cli/cmd/... ./staging/src/github.com/kcp-dev/sdk/cmd/...
+install: WHAT ?= ./cmd/... ./staging/src/github.com/kcp-dev/cli/cmd/... ./staging/src/github.com/kcp-dev/sdk/cmd/...
 install: require-jq require-go require-git verify-go-versions ## Install the project
 	set -x; for W in $(WHAT); do \
 		pushd . && cd $${W%..}; \

docs/content/contributing/guides/publishing-a-new-kcp-release.md

@@ -17,9 +17,12 @@ description: >
 2. <https://docs.github.com/en/authentication/managing-commit-signature-verification/adding-a-gpg-key-to-your-github-account>
 3. <https://docs.github.com/en/authentication/managing-commit-signature-verification/telling-git-about-your-signing-key>
 
-### Create the Tags
+### Create the Tag
 
-kcp has 2 go modules, and a unique tag is needed for each module every time we create a new release.
+!!! note
+    kcp used two have two submodules (`sdk` and `cli`) which were tagged separately in addition to the main kcp module.
+    With the introduction of the monorepo, those two submodules became staging repositories. Their tags are now handled
+    automatically by publishing-bot, so it's only needed to create one tag for the main kcp module.
 
 1. `git fetch` from the main kcp repository (kcp-dev/kcp) to ensure you have the latest commits
 2. Tag the main module
@@ -33,28 +36,12 @@ kcp has 2 go modules, and a unique tag is needed for each module every time we c
     git tag --sign --message "$TAG" "$TAG" "$REF"
     ```
 
- 3. Tag the `sdk` module, following the same logic as above for `REF` and `TAG`
-
-    ```shell
-    REF=upstream/main
-    TAG=v1.2.3
-    git tag --sign --message "sdk/$TAG" "sdk/$TAG" "$REF"
-    ```
-    
-4. Tag the `cli` module, following the same logic as above for `REF` and `TAG`
-
-    ```shell
-    REF=upstream/main
-    TAG=v1.2.3
-    git tag --sign --message "cli/$TAG" "cli/$TAG" "$REF"
-    ```
-
-### Push the Tags
+### Push the Tag
 
 ```shell
 REMOTE=upstream
 TAG=v1.2.3
-git push "$REMOTE" "$TAG" "sdk/$TAG" "cli/$TAG"
+git push "$REMOTE" "$TAG"
 ```
 
 ## If it's a New Minor Version