Small adjustments to the release config and docs (#4487)

Signed-off-by: Juraci Paixão Kröhling <[email protected]>

.github/workflows/builder-release.yaml

@@ -25,7 +25,7 @@ jobs:
         with:
           distribution: goreleaser-pro
           version: latest
-          args: release --rm-dist
+          args: release --rm-dist -f cmd/builder/.goreleaser.yml
         env:
           GORELEASER_KEY: ${{ secrets.GORELEASER_KEY }}
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

cmd/builder/.goreleaser.yml

@@ -22,6 +22,11 @@ builds:
     goarm:
       - 6
       - 7
+    binary: ocb
+release:
+  github:
+    owner: open-telemetry
+    name: opentelemetry-collector
 archives:
   - format: binary
 checksum:

docs/release.md

@@ -31,7 +31,9 @@ We release both core and contrib collectors with the same versions where the con
 
 1. Tag all the modules with the new release version by running the `make add-tag` command (e.g. `make add-tag TAG=v0.4.0`). Push them to origin (not your fork) with `git push --tags origin` (assuming origin refers to upstream open-telemetry project). Wait for the new tag build to pass successfully.
 
-1. The release script for the collector builder should create a new GitHub release. Wait until the workflow "Builder - Release" has completed and change the release's description to include the release notes from the CHANGELOG.md file.
+1. The release script for the collector builder should create a new GitHub release for the builder. This is a separate release from the core, but we might join them in the future if it makes sense.
+
+1. Create a new `v0.40.0` release and use the contents from the CHANGELOG.md as the release's description.
 
 ## Releasing opentelemetry-collector-contrib