Combine catalogd and operator-controller goreleaser configurations

[OchiengEd]

Combine goreleaser files from the catalogd and operator-controller files.

[jsm84]

Linked to internal Jira story EET-4420.

[LalatenduMohanty]

We can use GoReleaser within a monorepo and use tag prefixes to mark "which tags belong to which sub project" [1]

[1] https://goreleaser.com/customization/monorepo/

[LalatenduMohanty]

We can create a .goreleaser.yaml for each subproject

# subroj1/.goreleaser.yaml
project_name: subproj1

monorepo:
  tag_prefix: subproject1/
  dir: subproj1

Then, you can release with (from the project's root directory):

goreleaser release --clean -f ./subproj1/.goreleaser.yaml

[LalatenduMohanty]

After the monorepo prep script is run the go releaser is working fine

go: module github.com/operator-framework/catalogd: not a known dependency
(re)installing /home/lmohanty/go/bin/goreleaser-v1.26.2
/home/lmohanty/go/bin/goreleaser-v1.26.2 --snapshot --clean
  • starting release...
 xxxxxxx
  • release succeeded after 14s
  • thanks for using goreleaser!
 
=======================================================
lmohanty@LenovoP16v:~/code/operator-controller/catalogd$ make release 
sed: can't read go.mod: No such file or directory
/home/lmohanty/go/bin/goreleaser-v1.26.2 --snapshot --clean
  • starting release...
xxxxxx
  • release succeeded after 46s
  • thanks for using goreleaser!

[LalatenduMohanty]

However there are two warnings i.e. for operator-controller go: module github.com/operator-framework/catalogd: not a known dependency and catalogd sed: can't read go.mod: No such file or directory

[LalatenduMohanty]

So current goreleaser files work fine after the monorepo script is run. However the release of operator-controller will get all change long from catalog directory as well, which is not desired.

[LalatenduMohanty]

As discussed in the #olm-dev slack channel. We do not need any changes in the go-releaser files.

[1] https://kubernetes.slack.com/archives/C0181L6JYQ2/p1734649103901029