GoReleaser "is a GoReleaser Pro feature" (GORELEASER_KEY) in CI

Some GoReleaser config keys are only available in GoReleaser Pro. Running the open-source build with a Pro-only field, or Pro without a valid GORELEASER_KEY, fails with a Pro feature error.

What this error means

GoReleaser fails to load config or run with "X is a GoReleaser Pro feature" or "invalid GORELEASER_KEY", pointing at a Pro-only field.

⨯ release failed after 0s
  error=partial: only available in GoReleaser Pro, get it at
  https://goreleaser.com/pro

Common causes

A Pro-only field on the open-source build

Fields like partial, nightly, or templated includes are Pro-only; the OSS binary rejects them.

Pro is used without a valid key

The Pro distribution needs GORELEASER_KEY set to a valid license, or it will not run Pro features.

How to fix it

Use the Pro distribution with a key

1. Set distribution: goreleaser-pro in the action.
2. Provide GORELEASER_KEY from a secret in the step env.
3. Re-run so the Pro features are recognized.

- uses: goreleaser/goreleaser-action@v6
  with:
    distribution: goreleaser-pro
    args: release --clean
  env:
    GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
    GORELEASER_KEY: ${{ secrets.GORELEASER_KEY }}

Remove the Pro-only field if you use OSS

If you are not on Pro, delete the Pro-only key from the config so the open-source binary can run.

goreleaser check

How to prevent it

• Know which config fields are Pro-only before adding them.
• Set distribution: goreleaser-pro and GORELEASER_KEY when using Pro.
• Run goreleaser check to catch Pro-only fields early.

Related guides