update make target + corresponding doc

Author: cahillsf

Makefile

@@ -1097,13 +1097,9 @@ release-alias-tag: ## Add the release alias tag to the last build tag
 	gcloud container images add-tag $(CAPIM_CONTROLLER_IMG):$(TAG) $(CAPIM_CONTROLLER_IMG):$(RELEASE_ALIAS_TAG)
 	gcloud container images add-tag $(TEST_EXTENSION_IMG):$(TAG) $(TEST_EXTENSION_IMG):$(RELEASE_ALIAS_TAG)
 
-.PHONY: release-notes
-release-notes: $(RELEASE_NOTES_DIR) $(RELEASE_NOTES)
-	if [ -n "${PRE_RELEASE}" ]; then \
-	echo ":rotating_light: This is a RELEASE CANDIDATE. Use it only for testing purposes. If you find any bugs, file an [issue](https://github.com/kubernetes-sigs/cluster-api/issues/new)." > $(RELEASE_NOTES_DIR)/$(RELEASE_TAG).md; \
-	else \
-	go run ./hack/tools/release/notes.go --from=$(PREVIOUS_TAG) > $(RELEASE_NOTES_DIR)/$(RELEASE_TAG).md; \
-	fi
+.PHONY: release-notes-tool
+release-notes-tool:
+	go build -o bin/notes hack/tools/release/notes.go
 
 .PHONY: promote-images
 promote-images: $(KPROMO)

docs/release/release-tasks.md

@@ -321,7 +321,7 @@ The goal of this task to make the book for the current release available under e
 1. Checkout the `main` branch.
 1. Build the release note tools binary.
    ```bash
-   go build -o bin/notes hack/tools/release/notes.go
+   make release-notes-tool
    ```
 1. Checkout the latest commit on the release branch, e.g. `release-1.4`, or the main branch if the release branch doesn't yet exist (e.g. beta release).
 1. Generate release notes with: