Out of curiosity, were you dealing with microservices defined within a monorepo, or microservices each in their own repo? The steps here:
> Build your binaries with the new version. Go through the build errors if any.
> Run all the unit tests with the new version. Go through the test failures.
are a lot easier in a monorepo.
Separately, I've experienced frequent breaking changes in the golangci-lint configuration file. I can't point to a specific instance of this happening but one thing I'd suggest is pinning your version of golangci-lint in development and in CI rather than using "latest".
Golang's backwards compatibility and simplified toolchain is one of my favorite parts about it. Bumping go.mod and downloading the new version of go is usually all it takes!
> Build your binaries with the new version. Go through the build errors if any.
> Run all the unit tests with the new version. Go through the test failures.
are a lot easier in a monorepo.
Separately, I've experienced frequent breaking changes in the golangci-lint configuration file. I can't point to a specific instance of this happening but one thing I'd suggest is pinning your version of golangci-lint in development and in CI rather than using "latest".
Golang's backwards compatibility and simplified toolchain is one of my favorite parts about it. Bumping go.mod and downloading the new version of go is usually all it takes!