fix: migrate .goreleaser.yml to GoReleaser v2 config schema Andriy Knysh (@aknysh) (#546)
## what- Migrate
.goreleaser.ymlfrom the GoReleaser v1 schema to v2:- Add
version: 2(required by GoReleaser v2) - Rename
archives.format→archives.formats(list;formatis deprecated in v2) - Rename
changelog.skip→changelog.disable(skipwas removed in v2)
- Add
why
- The
releaseworkflow'sgoreleaser-actiondefaults tolatest, which now resolves to v2.18.0. GoReleaser v2 only accepts configs declaringversion: 2and failed the release with:only version: 2 configuration files are supported, yours is version: 0 - The release job copies this repo's
.goreleaser.ymlinto.configs/repo/and uses it (it only falls back to the sharedcloudposse/.githubconfig when the repo has none), so our local config is what needs to be v2-compliant. - No behavioral change to the produced artifacts — only schema/field renames. Validated with
goreleaser v2.18.0 check→ "1 configuration file(s) validated", no errors or deprecation warnings.
references
- Failed run: https://github.com/cloudposse/terraform-provider-utils/actions/runs/33076515162/job/98536568557
- GoReleaser v2 migration guide: https://goreleaser.com/deprecations/
[!NOTE]
The canonicalcloudposse/.github/.github/goreleaser.ymlhas the same v1-isms and will fail for every repo relying on the shared config now thatlatest= v2.18.0. A separate upstream fix tocloudposse/.githubis warranted; this PR only unblocks this repo (which uses its own config).
Update Atmos to v1.227.0 Andriy Knysh (@aknysh) (#545)
## what- Update the embedded Atmos Go library from
v1.221.1tov1.227.0ingo.mod(andgo.sum). - Add a new row to the Atmos ↔
cloudposse/utilscompatibility matrix indocs/versions.mdand itsREADME.mdmirror: Atmosv1.227.0→ providerv2.7.0.
why
- Atmos
v1.222.0(PR cloudposse/atmos#2608) removed two public functions this provider depends on (pkg/aws.ExecuteAwsEksUpdateKubeconfigandpkg/utils.JSONToMapOfInterfaces), which pinned the provider to Atmosv1.221.1. - Atmos
v1.227.0restores those public API wrappers (PR cloudposse/atmos#2996), so the provider can track current Atmos again. - Keeping the embedded Atmos library version aligned with the Atmos CLI is required for deterministic YAML/JSON deep-merge results; the compatibility matrix documents the pairing so downstream users can pin correctly.
- Validation:
go build ./...passes; allinternal/...unit suites pass (component,convert,describe,merge,provider,spacelift,stack). The only failing test is theutils_spacelift_stack_configexample E2E, which requires a local Terraform dev-override provider build (9999.99.99) — environmental, not a code regression.
references
- Restores API removed in cloudposse/atmos#2608, re-added in cloudposse/atmos#2996
- Atmos release: https://github.com/cloudposse/atmos/releases/tag/v1.227.0
- Compatibility matrix:
docs/versions.md