I am fairly certain I found a bug in the go orb when using gorelease with a context that stores the Github token using a variable named GITHUB_TOKEN. I reported the issue here.
Basically, when the context is passed to the job, the goreleaser-release command will overwrite the GITHUB_TOKEN environment variable in the individual step with the literal value GITHUB_TOKEN before attempting to expand it again using the circleci cli. Since the environment variable no longer points to a valid token value, the release will fail.
I have a PR open to fix it by renaming the environment variable passed to the step used for storing the name of the environment variable with the actual Github token value.